County assessor InfiniBand HA subnet managers must cooperate during provisioning. Which prerequisite should documentation include?
Select an answer to reveal the explanation.
Short Explanation
HA subnet managers need a secure handshake, not anonymous file drops. Document trusted SSH between the county assessor’s HA SM nodes during InfiniBand provisioning.
Full Explanation
County assessor InfiniBand HA subnet managers must cooperate during provisioning, and documentation should include trusted SSH between HA subnet manager nodes as part of InfiniBand HA provisioning. Trusted SSH provides authenticated, auditable communication between SM nodes so HA coordination does not rely on open, unauthenticated channels that would be unacceptable on a county fabric.
Anonymous FTP between SM nodes with shared write access to fabric databases fails by concept: anonymous FTP is unauthenticated and unsafe for fabric-critical state. Disabling authentication so either SM can overwrite the other freely fails: it invites split-brain and unauthorized changes. Replacing both SMs with a weekly cron job that reboots all IB switches fails: reboots are not subnet management HA and cause recurring civic AI disruption.
Exam caveat: InfiniBand HA SM provisioning expects secure trust (e.g., trusted SSH) between SM nodes—not anonymous FTP, disabled auth, or reboot cron jobs as an HA strategy.
Operational check: configure mutual trusted SSH between county assessor HA SM nodes per security policy, verify non-interactive administrative connectivity works, complete IB HA provisioning steps that depend on that trust, and record the SSH trust setup in the civic IB runbook.