A Cloud Architect is tasked with publishing a vRealize Automation catalog item that enables Human Resources (HR) personnel to provision Active Directory user accounts. HR will continue to use…

Question

Options

• ACustom Resource
• BCustom Property
• CResource Mapping
• DResource Action

• A
  75% (18)
• B
  8% (2)
• C
  17% (4)

Explanation

Custom Resource (A) is required because Active Directory user accounts are external objects not natively tracked by vRealize Automation. A Custom Resource defines the AD user account as a manageable object type within vRA, giving the platform a schema to represent, track, and interact with it. Resource Action (D) is equally essential because HR needs to perform day-2 operations - modifying accounts after creation - and Resource Actions are exactly the mechanism that exposes post-provisioning management operations as catalog items.

Custom Property (B) is a distractor: while custom properties pass configuration data into blueprints, they don't model external resource types or enable post-creation management workflows on their own. Resource Mapping (C) is used to associate discovered resources with existing resource types, which is a different concern (reconciling existing inventory) rather than defining a new manageable external object type and its lifecycle actions.

Memory tip: Think "Model → Manage." The Custom Resource models the external AD account so vRA knows it exists, and the Resource Action lets HR manage it afterward. Both words contain "Resource" because they're both about treating the AD account as a first-class vRA resource throughout its lifecycle.

No community discussion yet for this question.