The requirement is provider-side pricing for VMs consumed through VCF Automation Organizations , with charging based on assigned vCPU count and different rates by VM size. In VCF Operations, this maps to Provider Pricing , not vCenter pricing or tag-based additional charges. The official workflow states that Provider Pricing is configured from Infrastructure Operations > Configurations > Policy Definition > Edit Policy > Provider Pricing , where the administrator activates the pricing engine and configures Region Quota settings . For CPU charging, the Compute Rate section provides the option CPU GHz Based / vCPU Count Based , and the administrator must select vCPU Count Based because the business rule is based on assigned vCPUs, not GHz consumption . The same section supports Base Rate Slabs , which allow different base rates depending on the number of CPUs used; each slab uses a “greater than or equal” threshold and a base rate . Therefore, slabs should be created for Small, Medium, and Large VM ranges. Tags and recurring tag charges are unnecessary because VM size is determined directly from vCPU count. Reference topic: Objective 4.4 – Cost Management in VCF Operations / Provider Pricing / Rate Cards / Chargeback .

The failure is caused by removal of the Linux socket statistics utility, ss , and visibility is restored by reinstalling or restoring that utility. VCF Operations Service Discovery relies on in-guest commands to identify running services and network relationships. For UNIX/Linux operating systems, the documented Service Discovery command and utility requirements are ps , ss , and top . If a hardened Linux image removes ss under least-functionality controls, VMware Tools and the Service Discovery plug-in can still be present, but the collector cannot perform the required service enumeration. This explains why legacy Linux systems still work while newly hardened systems do not. The correction is to restore the ss utility and ensure the discovery user can execute it. The documentation also shows that for non-root Linux users, sudoers may need NOPASSWD entries that include the ss path so collection scripts do not block on password prompts . tcpdump is not listed as a Service Discovery prerequisite, and netstat is a Windows Service Discovery utility in this context, not the required Linux dependency. Reference topic: Objective 4.7 – Service Discovery / Linux prerequisites / Supported commands and utilities .

The administrator should assign the developer an appropriate VCF Operations content-management role, represented here by ContentAdmin . In VCF Operations 9.0, Management Pack Builder is already integrated into the product; it is not deployed as a separate appliance and does not require installation from Marketplace. The official documentation states that Management Pack Builder enables creation of custom management packs for VCF Operations and that there is no separate installation required , replacing the older standalone OVA-based model . It is accessed directly in the VCF Operations console under Developer Center > Management Pack Builder , where users can create, import, export, edit, and delete custom designs . Therefore, the environment preparation step is access enablement, not software deployment. The ContentAdmin role is the best listed fit because Broadcom documents it as a role for users who manage content such as views, reports, dashboards, and custom groups in VCF Operations . Feature flags, OVA deployment, and Marketplace installation are not required. Reference topic: Objective 4.8 – Management Pack Builder / custom management packs / access and content administration .

In Disconnected Reporting Mode , VCF Operations cannot automatically submit license usage or retrieve updated license entitlement information. The administrator must manually exchange files between the isolated VCF Operations instance and the VCF Business Services Console . The official workflow states that in disconnected mode, the administrator must manually report license usage and upload license files in VCF Operations . The required sequence is: generate a usage file from License Management > Registration in VCF Operations, upload that usage file to the VCF Business Services Console, download the generated license file, and then import that license file back into VCF Operations . This process must be completed at least once every 180 days ; otherwise, licenses are treated as expired, hosts are disconnected from vCenter, and workload operations cannot start . Adding a legacy license key, enabling SSH, or downloading a license key from the Broadcom Support Portal are not part of the VCF 9 disconnected reporting process. Reference topic: Objective 4.15 – Manage VCF licensing with VCF Operations / Disconnected Reporting Mode / Usage File and License File Exchange .

The administrator should use Edit for Specific Datacenter mode and edit the Facilities cost driver. VCF Operations cost drivers calculate private cloud cost from inventory details such as ESX hosts, datastores, VMs, configuration, and utilization, and administrators can modify data-center expenses when the default reference values do not reflect actual costs . Because the only stated variation across DC1–DC4 is power and cooling , the relevant cost category is Facilities , which covers real estate, data center buildings, power, cooling, racks, and facility management labor . The Facilities workflow specifically allows the administrator to modify power and cooling cost per kilowatt-hour or total monthly facilities cost . Since the four datacenters do not share identical power and cooling values, the administrator must select Edit for Specific Datacenter , which allows different cost-driver values for different datacenters instead of applying a single value globally . Server Hardware: Hyper-Converged is relevant for vSAN/vxRail hardware costing, but the scenario states that all monthly costs are the same except power and cooling. Reference topic: Objective 4.4 – Cost Management / Cost Drivers / Facilities Cost Driver / Specific Datacenter Edit Mode .

The OUT_OF_SYNC state indicates that the configuration template state in VCF Operations no longer matches the corresponding state expected from Source Control. VCF Operations supports GitHub-based source control so configuration templates can be synchronized to and from a repository, and the documented sync workflow explicitly changes template status back to IN_SYNC after the administrator uses the Sync option in VCF Operations . A template can become out of sync when it is modified outside the VCF Operations workflow, such as being edited directly in the GitHub repository. It can also become out of sync if the corresponding template file is deleted from the repository, because VCF Operations can no longer reconcile the local template object with its source-controlled copy. If the source-control configuration itself is deleted, VCF Operations loses the configured repository association required to validate and synchronize templates. Removing a template from a policy or removing a vCenter instance from a drift-detection job affects drift evaluation scope, not Git template synchronization. Reference topic: Objective 4.16 – Configuration Drift / Source Control Integration / Syncing Configuration Templates with GitHub .

The administrator should use a List View. In VCF Operations, views present collected information for objects depending on the selected view type, and the View widget can be added to custom dashboards to display operational data that is relevant to dashboard users . A List View is specifically designed to provide tabular data about selected objects in the monitored environment, where each object appears as a row and the selected metrics or properties appear as columns . This directly satisfies the requirement to monitor CPU, memory, and disk usage across all VMs in a workload domain because the administrator can select Virtual Machine as the subject and add the required usage metrics as columns. The documentation also states that the View widget supports Export as CSV, and that views can be exported in CSV format . Scoreboard is best for current metric tiles, Object Relationship is for topology, and Trend View is for historical trends and forecasts, not detailed tabular extraction. Reference topic: Objective 4.10 – Creating Custom Dashboards, Views and Reports / Create a View / List View / View Widget Export as CSV.

The correct recovery method is to log in to the VCF Operations primary/master node console as root and reset the local administrator password using the CLI reset utility. Broadcom documents a dedicated procedure titled Reset the VCF Operations Administrator Password from CLI , and the guidance applies when the admin account password is lost. ( TechDocs ) The VMware Aria Operations administrator password reset workflow also identifies the vcopsSetAdminPassword.py --reset command as the reset mechanism when performed from the appliance command line as root. ( TechDocs ) This is different from a normal password rotation workflow. Fleet Management password management is used for managed component credentials, but it does not replace the break-glass local admin reset procedure when the administrator password is unknown. AD administrator access also does not reset the built-in local VCF Operations admin account unless that account is already accessible through supported administration workflows. Reference topic: Objective 4.14 – Fleet Management / Password Management / Reset VCF Operations Administrator Password from CLI .