An administrator has been tasked with investigating reports of degraded VM performance using the VCF Operations Troubleshooting Workbench .
Drag and drop the three correct actions from the Actions list on the left and place them into the Troubleshooting Workbench Actions list on the right in any order. (Choose three.)

Explanation:
Identify the primary symptom
Examine related events/changes
Review top anomalous metrics
The correct Troubleshooting Workbench actions are to identify the primary symptom , examine related events or changes , and review top anomalous metrics . VCF Operations Observability/Troubleshooting Workbench is designed to investigate known or unknown issues by focusing on a selected object, alert, or metric within a defined scope and time range. The documentation states that the workbench searches for potential evidence around the problem and displays evidence as cards based on Events , Property Changes , and Anomalous Metrics . Events show metric-behavior changes and major events in the selected scope and time. Property Changes show important configuration changes that occurred in that same scope. Anomalous Metrics show metrics with drastic changes and rank them by the degree of change, giving the most relevant anomalies the highest weight . Therefore, reviewing anomalies and related changes is central to the workbench workflow. Identifying the primary symptom is the starting point for narrowing the investigation.
BIOS power settings, NSX Edge logs, and historical Compliance Drift reports may support broader troubleshooting, but they are not core Troubleshooting Workbench actions. Reference topic: Objective 4.9 - Troubleshooting Workbench / Potential Evidence / Events, Property Changes, and Anomalous Metrics .

An administrator wants to graphically represent which ESX hosts have the highest memory ballooning activity. Which custom view in VCF Operations would satisfy this requirement?

• A. List view with Host Systems and memory ballooning usage metrics
• B. Trend view with Host System objects and memory ballooning usage metrics
• C. Summary view with cluster-level memory ballooning average metrics
• D. Distribution view with Host Systems and memory ballooning usage metrics

說明：（僅 KaoGuTi 成員可見）

A VM named acme001 is listed in the Rightsize oversized list with a default recommendation of a 2 vCPU reduction and also in the undersized list with a default recommendation of a 2 GB memory increase. The administrator schedules the oversized vCPU reduction, then excludes the VM from the undersized list, then schedules scale-up for the remaining undersized VMs. What are the two results for acme001? (Choose two.)

• A. The acme001 VM is reduced by 2 vCPU and memory is increased by 2 GB
• B. The acme001 VM vCPU is not changed
• C. The acme001 VM is reduced by 2 vCPU
• D. The acme001 VM memory is increased by 2 GB
• E. The acme001 VM memory is not changed

說明：（僅 KaoGuTi 成員可見）

An administrator has been tasked with customizing the "Live! Heavy Hitters" Dashboard to include the metric
"Cost | VM Cost Trend." What action should the administrator take to complete this task?

• A. Within the Dashboards Overview panel, click the "Live! Heavy Hitters" Dashboard, click the Edit action and add the relevant metric
• B. Within the Manage Dashboards panel, Clone the dashboard and add the relevant metric
• C. Within the Manage Dashboards panel, click the checkbox for the dashboard, click Edit and add the relevant metric
• D. Within the Manage Dashboards panel, click "Change Ownership" to assign edit permission and add the relevant metric
• E. Within the Manage Dashboards panel, Export the dashboard and add the relevant metric

說明：（僅 KaoGuTi 成員可見）

Given the scenario provided, which three statements should the administrator use to describe the way that the Capacity Models are configured within the VCF workload domain? (Choose three.)

• A. The Allocation model has not been enabled on CL-02
• B. The most constrained resource in CL-01 is CPU Allocation
• C. The most constrained resource in CL-02 is Memory Allocation
• D. The Allocation model for CPU in CL-01 has been configured with a 5:1 vCPU:Core ratio
• E. The Allocation model for CPU in CL-01 has been configured with a 4:1 vCPU:Core ratio
• F. The Allocation model has not been enabled on CL-01

說明：（僅 KaoGuTi 成員可見）