An organization is migrating to vRealize Automation from vCloud Automation Center. Which two steps are necessary to support this requirement? (Choose two.)

Ingrid P.Apr 19, 2026

B and D are your correct answers here. When migrating from vCloud Automation Center to vRealize Automation, both the Distribution Execution Worker names and the agent names in the new deployment must exactly match what was configured in the old environment, because vRA uses those names as identifiers to map existing endpoint configurations and workflow references during the migration process. If either set of names differs, the system cannot reconcile the old state with the new infrastructure and your migration breaks. A and C are distractors worth knowing: Active Directory is not a mandatory identity store requirement for this migration scenario, and group administrator access to the default tenant is a general permission concern, not a migration-specific prerequisite. Card this one with the cue "vCAC to vRA migration naming requirements" and make sure the answer side lists both DEW names and agent names, because exams love to make you pick two and one of the wrong options will always sound plausible enough to trip you up if you only half-remembered it.

Jelena G.Apr 7, 2026

I almost locked in A and D, figuring the Identity Appliance with an Active Directory store was mandatory since vRA leans on SSO and tenant auth so heavily, but the question is specifically about what the migration itself requires, not what a healthy vRA deployment requires in general. What pushed me to B and D together was remembering that vRA ties blueprint execution to specific named DEMs and agents, so if you bring up a fresh vRA instance and the Distribution Execution Worker names or the agent names differ even slightly from what vCAC was running, your existing workflows and provisioning blueprints will fail to hand off work correctly because those names are baked into the references. The migration docs make it clear that name continuity is the load-bearing constraint here, not identity store type, since you can reconfigure SSO after the fact but you cannot silently rename the execution fabric and expect in-flight or stored blueprints to resolve correctly. C is just a general RBAC best practice, not a migration step, so that one drops out fast once you frame the problem around execution continuity rather than feature completeness.

Dervla O.Apr 12, 2026

B and D are right, naming continuity is the migration linchpin, not identity config.

Prof. SaraApr 1, 2026

A is a trap, exact name matching locks migration continuity, so B and D.