The VCF 9.0 Automation Guide details the use of Property Groups to standardize blueprint inputs and constants across projects. Property Groups allow administrators to define sets of inputs (like size, os, location) and constants (like salt master id) centrally, ensuring consistency across deployments.
The correct actions are:
Create a new Property Group for input properties (C) to capture the standard inputs (size, os, location).
Create a new Property Group for constant properties (E) to include items like the salt master id.
Update all existing blueprints in the production project with the new Property Groups (F) to enforce standardization across new and existing workloads.
Options A and B are incorrect because changes are not required in the appdev project or across the entire organization-only the production project. Option D is redundant since inputs and constants should be separated into distinct groups.

The Network Operations feature within VMware Cloud Foundation is powered by VCF Operations for Networks (formerly Aria Operations for Networks).
The VCF 9.0 documentation explains:
"VCF Operations for Networks provides application dependency mapping, network flow visibility, micro-segmentation validation, and network troubleshooting capabilities." Without this component, advanced network analytics and topology visualization are not available.
vDefend firewall (B) provides security enforcement but does not deliver analytics and visibility features.
NSX networking (C) provides networking services but does not itself deliver network operations insights and analytics.
VCF Operations collector (D) collects data but does not provide the network operations feature set.
Thus, to enable full Network Operations capability, the administrator must install and configure VCF Operations for Networks.

The VCF 9.0 Kubernetes Service documentation confirms that Antrea is the default CNI used for VMware Kubernetes Service (VKS) workload clusters.
"When deploying a new VKS workload cluster, the Antrea Container Networking Interface is automatically enabled by default to provide pod-to-pod and pod-to-service networking. Antrea is fully integrated with NSX-T for advanced policy control." Flannel, Calico, and Cilium are widely used CNIs in upstream Kubernetes but are not the default in VCF. Administrators can optionally integrate with third-party CNIs, but the supported default choice is Antrea.

In VMware vSphere with Supervisor (used within VCF), a vSphere Namespace allows administrators to define resource quotas for Kubernetes workloads.
The vSphere documentation specifies that administrators can configure limits on:
CPU resources
Memory resources
Storage capacity
These quotas control the maximum resources that workloads deployed within the namespace can consume.
Incorrect options:
The number of containers (A) is managed at the Kubernetes level, not directly as a namespace resource quota in vSphere.
The number of services (D) is a Kubernetes object count limit, not a vSphere namespace resource limit.
Thus, the three configurable resource limitations are CPU, Memory, and Storage.

To deploy Kubernetes workloads through VCF Automation (Organization for All Applications), the following prerequisites are required:
vSphere Supervisor must be activated within the workload domain (B) to enable Kubernetes functionality.
A Region must be configured (A) to provide compute and storage capacity to the Organization.
NSX Federation (C) is optional and not required.
VKS activation in the Management domain (D, E) is not required for workload domain Kubernetes deployments.