An administrator has successfully deployed and configured the Application Monitoring Telegraf Agent to 30 virtual machines through VMware Cloud Foundation (VCF) Operations.
After 24 hours, the administrator is alerted to the fact that no additional data has been collected since the agents were deployed on the virtual machines.
What could be the possible cause of the issue?

• A.There is a time synchronization issue between the Telegraf Agent and the Cloud Proxy.
• B.The Service Discovery Management Pack has not been configured.
• C.Application monitoring has been configured to use a single Cloud Proxy rather than a Collector Group.
• D.There is a compatibility issue between the version of Virtual Machine Hardware and VMware Tools.

Comment: *

Name: *

Email: *

Verification: *

An administrator is asked to create a second provider gateway (provider gateway 02) in VMware Cloud Foundation (VCF) Automation Region-A.
After launching the Create Provider Gateway workflow in the VCF Automation Provider Management Portal, no Tier-0 Gateway is available for assignment.
How would you resolve this issue?

• A.Create a new Region.
• B.Log into the NSX Manager, create a new Tier-1 Gateway.
• C.Log into the NSX Manager, create a new TO Gateway.
• D.Retry the Create Provider Gateway workflow.

Comment: *

Name: *

Email: *

Verification: *

An administrator has created an alarm for an object in VMware Cloud Foundation (VCF) Operations. The alert does not show up In the alert pane despite being configured on the object.
Parameters:
* Symptom definition: Read Latency (ms) is higher than 1 ms.
* Alert definition: Alert is triggered as soon as the latency is higher than the 1 ms defined in the symptom definition.
* Object type: Virtual Machine.
What is the reason the alert does not show up in the alert view?

• A.The administrator is missing the privileges to view alerts for this object.
• B.The metric used in the symptom definition does not apply to this object type.
• C.The alert is not enabled in the policy.
• D.This type of alert must be forwarded from VMware Cloud Foundation Operations for Logs.

Comment: *

Name: *

Email: *

Verification: *

An administrator is troubleshooting network connectivity issues on a VMware ESX host configured with a dedicated VMware vSAN vSphere Distributed Switch (vDS) port group. The VMware vSAN vDS port group has two physical adapters and two uplinks assigned. After a failure of the active physical adapter, the vSAN vDS connection over the vSAN network was lost.
What is the cause of the issue?

• A.The vSAN storage policies are misconfigured.
• B.VLAN tagging is not correctly configured on the vDS.
• C.A physical adapter is set to "Not Used" in the vDS configuration.
• D.The vDS failover policy does not allow fallback.

Comment: *

Name: *

Email: *

Verification: *

An administrator is attempting to activate a new vSphere Supervisor for use with VMware Cloud Foundation (VCF) Automation on a newly deployed cluster. In the VMware vSphere client, when going through the vSphere Supervisor activation having selected VCF Networking with VPC, the Virtual Private Cloud (VPC) Connectivity Profile dropdown is empty on the workload network page. The administrator verified that a Virtual Private Cloud (VPC) Connectivity Profile exists in NSX.
What is the cause of the issue?

• A.The TO gateway is in active/active mode.
• B.The vSphere Supervisor control plane is set to high-availability.
• C.The selected NSX Project is the Default Project.
• D.The default VPC has not been created.

Comment: *

Name: *

Email: *

Verification: *