An organization has decided to leverage the Security Configuration Management Automation (SCMA) framework to continuously inspect services for deviations from established security policies. How does Nutanix keep these scans from impacting cluster performance?

The Security Configuration Management Automation (SCMA) framework is designed to run as a low-priority background process. This ensures that the security scans and checks consume system resources (CPU, I/O) only when they are not being used by higher-priority services, such as user virtual machines and core cluster operations. This "nice" scheduling approach effectively prevents the security hardening process from impacting the performance of production workloads running on the Nutanix cluster.

A. SCMA checks are bypassed by STIG: This is incorrect. SCMA is a framework used to apply and audit security baselines like STIGs, not bypass them.
B. SCMA is fully managed by Prism Central: While management is done via Prism Central, this describes the management interface, not the mechanism for preventing performance impact.
C. SCMA inconsistencies aren't reverted: This is a configurable option for remediation. The scan itself still runs regardless of the remediation setting.

1. Nutanix Security Guide (Version 6.5), "Security Configuration Management Automation (SCMA)," Page 11. The guide states, "The SCMA framework runs checks at a low priority to minimize any performance impact on the cluster."