Question 2: An administrator is responsible for managing a VMware Cloud Foundation (VCF) fleet and the admi… | Advanced VMware Cloud Foundation 9.0 Automation Practice Question

An administrator is responsible for managing a VMware Cloud Foundation (VCF) fleet and the administrator has been tasked with the following: • Create DNS records before each virtual machine (VM) is deployed using VCF Automation. The administrator has already completed the following tasks: • Created two VCF Operations Orchestrator Workflows with corresponding Event Subscriptions: Create DNS Record Delete DNS Record • Created a new blueprint to deploy a VM: Added two string inputs, hostname and domainName Added hostname: '${input.hostname}' as a custom property of the Virtual Machine resource. Added domainName: '${input.domainName}' as a custom property of the Virtual Machine resource. What should the administrator configure within the Event subscription to ensure that the DNS record is only created when the hostname is provided?

Answer

A. Add the Delete DNS Record workflow as the Recovery Workflow of the Create DNS Record subscription.
B. Add the event.data.customproperties['domainName'] != null condition to the Create DNS Record and Delete DNS Record subscriptions.
C. Add the event.data.customproperties['hostname'] != null condition to the Create DNS Record and Delete DNS Record subscriptions. Correct
D. Enable the Block execution of events in topic option in the Create DNS Record and Delete DNS Record subscriptions.

Explanation

VCF Automation 9.0 utilizes an Event Broker Service (EBS) to trigger extensibility workflows during the lifecycle of a deployment. For a DNS integration to function correctly and reliably, the event subscription must be "scoped" to prevent it from firing when essential metadata is missing. In this scenario, the administrator has mapped the user input hostname to a custom property of the virtual machine. By adding the condition event.data.customproperties['hostname'] != null to the subscription, the platform evaluates the payload before invoking the Operations Orchestrator workflow. If the consumer leaves the hostname field empty (assuming it is not marked as mandatory in the blueprint), the condition will evaluate to false, and the DNS creation workflow will not be triggered, preventing "empty" or invalid records from being sent to the DNS provider. This logic must be applied to both the creation and deletion subscriptions to maintain parity throughout the VM's lifecycle. Using the customproperties array within the event.data payload is the standard method for referencing blueprint-specific inputs within the VCF 9.0 extensibility framework.