This is because according to VMware documentation3, developers can only access Kubernetes storage classes that are mapped from VM Storage Policies. They cannot modify or delete them.

This is because according to VMware documentation, this is what an administrator must register as an external component to complete this task of configuring scheduled backups for the SDDC Manager. SFTP server is one of the supported backup targets for SDDC Manager backups. The administrator can register an SFTP server by navigating to the SDDC Manager UI > Administration > Backup > Site Settings and clicking Register External.

According to Networking Requirements for vSAN1, the maximum network latency between the two main sites for stretched clusters is 5 ms RTT (round-trip time). This means that the latency between any two nodes in different availability zones should not exceed 5 ms.

According to the VMware Cloud Foundation documentation on network requirements, vSAN requires only the vMotion and NFS networks to be configured in the network pool. This is because vSAN traffic can be carried over the vMotion network, and the NFS network is needed to support the use of NFS datastores [1].

NFS is a file-based storage protocol that can be accessed over IP networks. It does not require any special hardware or software, and can be accessed by any device that supports the NFS protocol [2]. As such, it only requires the NFS network to be configured in the network pool.

Therefore, the correct answers are B. NFS and E. vSAN.

This is because according to VMware documentation1, these are two of the limits that an administrator can configure on a vSphere Namespace for a VMware Cloud Foundation Developer-Ready Workload Domain. Secrets are used to store sensitive information such as passwords or tokens for Kubernetes workloads2. Persistent Volumes are used to provide persistent storage for Kubernetes workloads3.

The NSX Manager is a standalone appliance that hosts the API services, the management plane, control plane, and policy management. As a result of this combined format, you no longer need to install the manager and controllers as separate VMs. The NSX Manager has three built-in roles: policy, manager, and controller 1.

B. Policy: NSX Manager is responsible for the creation and management of NSX-T policies, which are used to define networking and security configurations and rules.

C. Controller: NSX Manager also serves as a central management point for NSX-T controllers, which are responsible for implementing and enforcing networking and security policies across the NSX-T environment.

References:

• VMware Cloud Foundation Specialist (v2) Exam Guide, section 2.2
• NSX-T Data Center Administration Guide, section "NSX Manager and NSX-T Controllers"

This is because according to VMware documentation1, the VMware Imaging Appliance (VIA) is a tool that automates ESXi host imaging and configuration for VCF deployments. It supports custom ESXi images that include additional drivers or VIBs that are not part of the base ESXi image2. You can download ESXi software and VIBs from VMware or third-party sources and upload them to VIA for creating custom images3.