A public-health GPU chassis must inherit a known-good UCS baseline through Intersight. Which construct should the city team apply?

A public-health GPU chassis that must inherit a known-good UCS baseline through Intersight should receive a UCS domain profile so the chassis inherits that reusable baseline. Domain profiles encode FI/domain-level settings as a managed, repeatable construct rather than one-off drift. Domain 3.2.a positions Intersight domain profiles as the vehicle for consistent civic UCS domains. A UCS server profile template via Intersight to define blade identity and boot policy only configures individual blades; it does not make the chassis inherit the reusable domain baseline or prevent domain-wide drift. A Cisco UCS Manager service profile configured on the fabric interconnect pair is managed locally through UCS Manager rather than Intersight, so it does not deliver the Intersight-inherited known-good domain baseline to the chassis. An Intersight firmware and NTP policy bundle attached to the server profiles for the GPU blades addresses component-level settings, not the domain-level chassis baseline that the requirement calls for. Exam caveat: domain profiles and server profile templates address different layers—the domain profile covers the UCS domain/FI fabric context the chassis inherits; a server profile template only sets per-blade identity and boot policy and won't apply that chassis-level baseline. Operational check: define or select the known-good UCS domain profile in Intersight, assign it to the public-health domain/chassis, verify compliance shows the baseline applied, and confirm subsequent chassis additions inherit the same profile without manual CLI drift.