A 311 model-farm InfiniBand fabric needs recurring civic ops visibility. What should operators schedule?
Select an answer to reveal the explanation.
Short Explanation
Governance likes a weekly report card, not a surprise outage. Schedule UFM health reports so the 311 model farm’s InfiniBand fabric shows up in civic ops review on a cadence.
Full Explanation
A 311 model-farm InfiniBand fabric that needs recurring civic ops visibility should schedule weekly UFM health reports for InfiniBand municipal governance review. Recurring reports turn UFM from break-fix tooling into governance evidence: link health trends, bandwidth hot spots, and open defects reach managers on a cadence instead of only during outages. That schedule operationalizes IB monitoring for civic oversight and capacity planning.
Monthly UFM fabric performance exports for engineering tuning analysis fail because they serve engineering tuning rather than municipal governance review, and they do not provide the recurring civic ops visibility the fabric requires. Quarterly UFM inventory audits for asset lifecycle tracking fail because asset tracking does not show link health, bandwidth hot spots, or fabric trends needed for civic governance oversight. Daily UFM event log forwarding to data center operations console fails because raw event forwarding to operations is not scheduled governance reporting and does not retain the longitudinal health evidence municipal review requires.
Exam caveat: governance cadence can be weekly or a similar recurring interval—what matters is UFM health content with retained history, not asset-lifecycle inventory audits or event-log forwarding to the operations console. Operational check: automate weekly UFM health summaries to the 311 model-farm ops review, retain history for week-over-week comparison, escalate links that stay degraded across reporting periods, and treat the report as an acceptance input for further fabric changes.