A cloud architect is tasked with designing a vRealize Automation blueprint solution for a three-tier Web application deployment for a vSphere-based private cloud. The application performance team…

Question

Options

• ADefine vRealize Automation pre-defined custom properties and add them with correct values to
• BPre-create anti-affinity rules per VMware Validated Design.
• CAt the appropriate Event Broker state, execute a vRealize Orchestrator workflow to create DRS
• DDisplay pre-defined deployment custom properties for anti-affinity rules so that users can enter

• A
  11% (3)
• B
  25% (7)
• C
  57% (16)
• D
  7% (2)

Explanation

Option C is correct because vRealize Automation blueprints cannot natively create vSphere DRS anti-affinity rules on their own - this requires vCenter API interaction. The Event Broker integration point lets you trigger a vRealize Orchestrator (vRO) workflow at the right provisioning lifecycle state (e.g., after VMs are created), and vRO has the native capability to call the vCenter API to dynamically create anti-affinity rules scoped to that specific deployment's VMs.

Why the distractors are wrong:

• A - Custom properties alone can pass metadata into a blueprint, but they cannot instruct vCenter to create DRS rules. No built-in custom property exists that maps to anti-affinity rule creation.
• B - Pre-creating static DRS rules in vCenter is useless here because each blueprint deployment produces VMs with new, dynamically generated names. Static rules defined before provisioning cannot reference VMs that don't yet exist.
• D - Having users manually input anti-affinity values is error-prone and still doesn't create the DRS rule in vCenter. User input alone has no mechanism to configure vSphere.

Memory tip: Use the phrase "Event triggers Orchestrator to touch vSphere" - whenever a vRA blueprint needs to configure something inside vSphere that the blueprint engine can't do directly (DRS rules, port groups, tags), the correct pattern is always: Event Broker → vRO workflow → vCenter API call.

No community discussion yet for this question.