A city separates 911 inference compute from research training compute. How should UCS domain profiles be used?

When a city separates 911 inference compute from research training compute, UCS domain profiles should be separate for the 911 inference domain and the research training domain. Different security, ops, firmware, and connectivity intents must not bleed across zones that have different criticality. Domain 3.2.a expects domain-profile separation when municipal workloads are intentionally isolated. Using separate domain profiles for the 911 inference servers and research training servers misapplies the construct, since domain profiles configure the FI domains, while servers require server profiles. Using separate domain profiles to set boot order and firmware for 911 and research domains misstates their purpose, since boot order and server firmware are handled in server profiles, not in the FI domain settings that must stay separate per zone. Using separate domain profiles for the 911 inference chassis pair and research training pair misapplies the construct, since chassis pairs are managed with chassis profiles, while domain profiles must align separately to each FI domain. Exam caveat: separate domain profiles do not by themselves replace network segmentation, but on the exam they are the UCS construct that keeps domain-level settings aligned to each civic zone. Operational check: maintain distinct Intersight domain profiles for 911 inference and research training, assign each FI domain accordingly, review policy diffs for security/ops settings, and verify a profile change in research cannot apply to 911 inventory.