VCF Automation event subscriptions support Boolean conditions that determine whether the associated workflow runs. VCF 9.0 states that filters can be applied to subscriptions so that “the event and workflow only triggers if the Boolean expression is ‘true’.” Conditions can access event payload values through event.data, and the != operator is explicitly supported.

Because the stated requirement is specifically to create DNS records only when domainName has been provided, the subscription must test the corresponding custom property:

event.data.customProperties[ ' domainName ' ] != null

Option C checks hostname, which does not satisfy the stated condition. Option B addresses execution ordering: blocking subscriptions prevent another matching subscription from receiving the event until the current runnable item finishes. Option A is relevant to cleanup if the primary workflow fails because VCF supports recovery runnable items for blocking subscriptions, but it does not determine whether the DNS workflow should run based on the presence of the domain name.

The VCF 9.0 Convergence and Migration Guide outlines prerequisites and unsupported configurations when moving from a standalone vSphere deployment into VCF-managed workload domains.

Enhanced Linked Mode (ELM) must be removed:VCF does not support multiple vCenters joined in Enhanced Linked Mode. Each workload domain has its own dedicated vCenter instance, managed by SDDC Manager. The documentation states:“Before convergence, Enhanced Linked Mode must be deactivated. VCF requires independent vCenters for each workload domain.”

Lifecycle Manager must use Images only:VCF lifecycle operations are exclusively image-based. Baselines are not supported.“All clusters managed by VCF must be converted to vSphere Lifecycle Manager image-based lifecycle management prior to convergence.”

Other options are not required:

25 Gbps uplinks (A) are recommended for high throughput but not mandatory; 10 Gbps uplinks are supported.

An additional vMotion VMkernel (C) is not required by default, as standard vMotion networking is included in convergence designs.

vSphere Standard Switches (D) are not supported; VCF requires Distributed Switches, and existing vDS configurations can be adapted.

Therefore, the two configurations that must change are: Deactivate Enhanced Linked Mode (B) and switch Lifecycle Manager to Images only (E).

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.

The vSphere 9.0 Resource Management documentation, included within VMware Cloud Foundation 9.0, specifies that Resource Pools are the mechanism to delegate compute resources within a cluster. A resource pool acts as a container of compute resources (CPU and memory) that can be subdivided and assigned to VMs or groups of VMs.

The documentation states:

“Resource pools provide resource isolation, control, and delegation. You can configure reservations, limits, and shares to ensure that mission-critical workloads (such as production VMs) receive guaranteed resources, while development or test workloads consume only available resources.”

This aligns directly with the requirements:

Power on only if resources are available → Achieved via reservations and limits.

Production VMs require guaranteed levels of resources → Enforced using reservations.

Three-tier apps with varying demand → Controlled using shares and limits across multiple resource pools.

Other options are incorrect:

vSphere Availability (A) provides failover, not resource governance.

VCF Operations (B) monitors resource usage but does not allocate or enforce it.

Dynamic Resource Scheduling (D) balances workloads but does not provide delegated, guaranteed allocations per department or application tier.

Thus, the correct feature is vSphere Resource Pools.

Istio Service Mesh provides built-in capabilities for managing service-to-service communication within Kubernetes environments.

The Istio documentation highlights default capabilities including:

Service discovery (C): Automatic detection and routing between services.

Mutual TLS (mTLS) encryption (E): Secure communication between services by default.

Istio does not provide:

Multi-cluster backup/restore (A) — handled by tools such as Velero.

Cluster conformance validation (B).

Advanced container runtime (D) — container runtime is handled by container engines such as containerd.

Thus, the correct answers are Service discovery and Connection encryption.

The VCF Automation Provider Networking Guide states:

“Before you can configure Provider Networking, an active Tier-0 (T0) Gateway must be created in NSX Manager and associated with the Provider region.”

This gateway provides external routing and forms the foundation for VPC and tenant networking. Creating a T0 at the Organization level (A) is not correct—organizations consume Provider networking but do not create T0s. vDS in Provider Management (C) or vCenter (D) is unrelated to NSX-based provider networking.

Thus, the required prerequisite is: Create a T0 Gateway in NSX Manager.

The VCF Health feature “provides a central location for monitoring the health of your environment,” including the ability to track “vCenter Server instances,” “ESXi hosts,” and “NSX deployments.” Health monitoring includes connectivity, configuration, and critical services status, surfacing alerts for remediation. The documentation’s scope statements make clear that VCF Health targets the infrastructure components—vCenter, ESXi, and NSX—rather than the VCF Operations applications themselves (for example, Fleet Management or Logs). Therefore, the correct monitored components are ESX hosts, vCenter Server, and NSX.

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.

Memory tiering in modern vSphere environments allows hosts to utilize different memory technologies (e.g., DRAM and persistent memory tiers) to optimize cost and performance.

The vSphere documentation explains:

“Memory tiering enables efficient placement of memory pages across different memory types, optimizing performance and capacity for memory-intensive workloads.”

The primary use case is for:

Large in-memory databases

Analytics workloads

Memory-intensive applications

Incorrect options:

It does not primarily reduce swap for small VMs (A).

It does not directly boost CPU throughput (B).

It does not address host availability during hardware failure (C).

Thus, memory tiering is best suited for optimizing memory usage for large, memory-intensive workloads.

A VM Class predefines hardware for Supervisor-managed VMs: “The VM class… defines such parameters as the number of virtual CPUs, memory capacity, and reservation settings.”

Administration steps show these are configurable: “You can configure hardware resources such as CPU, memory, and different devices” when editing a VM class.

Additionally, the DCLI/API specification underscores CPU and Memory fields: “--cpu-count … Required.” and “--memory-mb … Required.” for a VM class.

While network adapters, PCI devices, and instance storage can also be added via advanced config, the question asks for two; CPU and Memory are canonical, always-present VM Class resources per the core definition above.

===========