Given a Scenario, Troubleshoot Issues When Scaling a VCF Fleet by Adding / Removing VCF Instances VCP-VCF-SUPPORT Practice Questions (Page 1)

Questions 1–5

1. 1foundation · easy

   Which log file would you examine to troubleshoot a failed VCF Fleet scaling operation?

   • ASDDC Manager logs
   • BNSX Manager logs
   • CvSphere ESXi host logs
   • DvSAN health logs
   Reveal Solution Discussion Select an answer first
2. 2foundation · easy

   Which pre-scaling check is performed to ensure that the target VCF Instance has enough capacity to accommodate the scaling operation?

   • AResource availability validation
   • BDNS resolution test
   • CNetwork latency measurement
   • DCertificate expiry verification
   Reveal Solution Discussion Select an answer first
4. 3foundation · easy

   During the addition of a new VCF Instance to a fleet, the operation fails at the validation stage. What is the most likely cause of this failure?

   • AThe instance's storage is running low
   • BThe instance has too many virtual machines
   • CThe instance's vCenter Server credentials are incorrect
   • DThe instance is using a different hypervisor
   Reveal Solution Discussion Select an answer first
5. 4expert · hard

   An administrator is removing a VCF Instance from a fleet. The removal operation fails during the cleanup phase, and the logs indicate that the instance's NSX-T Manager is still registered as a management plane in the management domain's NSX-T Manager. The administrator has already confirmed that no transport nodes are associated with the instance. What is the most appropriate next step to resolve this issue?

   • ARe-run the removal operation with the 'force' flag to bypass the dependency check.
   • BRestart the removal operation after waiting for the NSX-T Manager to synchronize with the management domain.
   • CDelete the instance's NSX-T Manager virtual machine directly from the management domain's vCenter Server.
   • DManually remove the instance's NSX-T Manager from the management domain's NSX-T Manager using the NSX-T API or UI.
   Reveal Solution Discussion Select an answer first
6. 5expert · hard

   An administrator is removing a VCF Instance from a fleet. The removal operation fails, and the error log indicates that the instance's vCenter Server is still registered as a solution user in the management domain's vCenter Server SSO. The administrator has already confirmed that no workload domains reference the instance. What is the most appropriate next step to resolve this issue?

   • ADelete the instance's vCenter Server virtual machine directly from the management domain's vCenter Server.
   • BRe-run the removal operation with the 'force' flag to bypass the dependency check.
   • CManually remove the solution user from the management domain's SSO using the vSphere Web Client, then retry the removal.
   • DRestart the removal operation after waiting for the SSO replication to complete.
   Reveal Solution Discussion Select an answer first