A housing-authority InfiniBand expansion may go live only after fabric health looks clean. What acceptance check should operators require?
Select an answer to reveal the explanation.
Short Explanation
Don’t cut the ribbon until the fabric dashboard smiles. Require UFM link-status green checks as InfiniBand acceptance criteria for the housing-authority expansion.
Full Explanation
A housing-authority InfiniBand expansion may go live only after fabric health looks clean, so operators should require UFM link-status green checks as InfiniBand acceptance criteria. Acceptance tied to UFM ensures new switches, cables, and HCAs are fabric-visible and healthy before production municipal traffic is admitted, unlike congestion-control tuning results which only reflect configuration changes rather than actual link health. That measured go-live gate protects civic workloads from silent IB faults introduced during expansion.
Acceptance based on UFM congestion-control tuning results fails by concept because tuning output reflects traffic-management configuration, not the physical and logical link health required before cutover. Relying on Subnet Manager priority settings fails because priority values influence master election and routing, not whether every expanded link is green and fault-free before go-live. Using HCA firmware inventory lists as acceptance fails because an inventory list documents adapter versions, not the real-time link status or fabric health UFM must verify before cutover.
Exam caveat: physical install evidence is necessary but not sufficient—UFM green link status is the fabric acceptance signal the exam expects before cutover. Operational check: block housing-authority go-live until UFM shows clean link status across the expanded IB segment, remediate any red or degraded links first, optionally add a short bandwidth sanity check, and attach UFM screenshots or exports to the acceptance record.