正解：

Explanation:
Invoke the process using a VCF Operations API call.
Schedule a job using VCF Operations Automation Central.
The two valid activation methods are to invoke Drift Detection through a VCF Operations API call and to schedule a job using VCF Operations Automation Central . VCF Operations Configuration Drift uses desired-state templates assigned through policy to compare vCenter and vSphere cluster configuration values against approved standards. The VCF 9.0 documentation states that unified configuration management supports scheduled drift detection for vCenter and cluster objects and allows administrators to schedule drift detection through VCF Automation or the VCF Operations orchestrator . The scheduling workflow is performed from Fleet Management > Configuration Drifts > Schedule Drift Detection , where the administrator defines the scope, criteria, and schedule; after creation, VCF Operations creates a new job in Automation Central . API invocation is also valid because VCF Operations exposes fleet and cloud proxy functionality through APIs for automation-driven operations . The GitLab or source-control sync options are not correct because source control synchronizes configuration templates, not the drift detection process itself.
Pull requests govern template change review, not drift execution. Reference topic: Objective 4.16 - Monitor Security, Compliance and Configuration / Configuration Drift / Scheduled Drift Detection / Automation Central / API-driven operations

正解：B  🗳️

解説: (PassTest メンバーにのみ表示されます)

正解：

Explanation:
Payment Card Industry Data Security Standard, PCI DSS, Compliance Standards Defense Information Systems Agency, DISA, Security Standards Center for Internet Security, CIS, Security Standards The supported benchmarks from the provided list are PCI DSS , DISA , and CIS . VCF Operations compliance monitoring is accessed from Security > Compliance , where compliance scorecards are based on alert definitions with the Compliance subtype. The official VCF 9.0 documentation states that Regulatory Benchmarks display benchmarks for industry-standard regulatory compliance requirements and explicitly lists Defense Information Systems Agency (DISA) Security Standards , Payment Card Industry Data Security Standard (PCI DSS) Compliance Standards , and CIS Security Standards as supported regulatory benchmark options. DISA is available as a native pack, PCI DSS is listed as a regulatory compliance standard, and CIS is supported through a compliance pack from VMware Marketplace .
FedRAMP and GDPR are not listed in the VCF Operations regulatory benchmark set shown in the guide.
NIST is supported only as specific NIST SP 800-171 and NIST SP 800-53 R5 packs, not as the generic
"NIST CyberSecurity Framework Security Baseline Standards" option shown in the question . Reference topic: Objective 4.16 - Monitor Security, Compliance and Configuration / Compliance Benchmarks / Regulatory Benchmarks .

正解：

Explanation:
Business Intent in VCF Operations is used to define placement constraints that represent organizational, licensing, operational, or regulatory requirements. In Workload Optimization, Business Intent works with Operational Intent. Operational Intent determines how aggressively VCF Operations balances or consolidates workloads, while Business Intent defines where workloads are allowed or expected to run based on tag-driven placement rules. The Workload Optimization documentation states that the Business Intent card lets administrators define infrastructure zones within cluster boundaries and select criteria for VM placement; optimization then reports whether workloads are optimized and whether tag violations exist . Therefore, meeting compliance goals , grouping common operating systems and applications together , and license enforcement are valid Business Intent use cases because they are placement-policy objectives. Maximize capacity utilization is not Business Intent; it belongs to capacity optimization and Operational Intent, where VCF Operations balances, consolidates, or optimizes resource usage . Keeping infrastructure cost per VM as low as possible is a FinOps/cost-management goal, not a workload-placement constraint. Reference topic:
Objective 4.6 - Workload Optimization / Business Intent vs Operational Intent / Placement Tags and Tag Violations .