County assessor InfiniBand auditors ask how agencies map to partitions. What should operators maintain?
Select an answer to reveal the explanation.
Short Explanation
You can't hand the county assessor Subnet Manager backups and call it an agency-to-PKey map. Keep InfiniBand PKey-to-agency mappings documented for the county assessor’s governance trail.
Full Explanation
When county assessor InfiniBand auditors ask how agencies map to partitions, operators must maintain InfiniBand PKey-to-agency tenancy documentation for municipal governance. Written mappings show which PKey IDs belong to which agencies, which GUIDs are members, and who approved changes—evidence auditors and civic governance require beyond switch ASICs. Relying on Subnet Manager partition configuration backups for fabric recovery operations fails because backups preserve fabric state, not the agency-to-PKey ownership narrative or change history auditors require. Keeping only an InfiniBand LID-to-port topology inventory for fabric troubleshooting workflows fails because LID and port maps locate hardware, not agency tenancy policy. Maintaining HCA GUID-to-server asset records for municipal hardware lifecycle tracking fails because asset records track server hardware, not which agencies belong to which InfiniBand partitions. Exam caveat: governance questions expect explicit PKey-to-agency documentation, not subnet-manager backups, LID topology inventories, or hardware asset logs. Operational check: produce the current PKey-to-agency map with GUID memberships, reconcile it to live IB partition config, fix drift, and store the document where assessor auditors and fabric operators both can retrieve it.