While creating a vCloud Director endpoint, how must an administrator configure vRealize Automation to manage all vCloud Director organizations with a single endpoint?

Question

Options

• ASpecify the organization in the Organization field and use the system administrator credentials.
• BLeave the Organization field blank and use the system administrator credentials.
• CSpecify the organization in the Organization field and use the organization administrator
• DLeave the Organization field blank and use the organization administrator credentials.

• A
  4% (1)
• B
  92% (22)
• C
  4% (1)

Explanation

Leaving the Organization field blank tells vRealize Automation to connect at the system level in vCloud Director, rather than scoping the endpoint to a single organization - combined with system administrator credentials, this grants visibility and management access across all vCloud Director organizations through one endpoint. Option A is wrong because specifying an organization restricts the endpoint to that one org, defeating the goal of managing all organizations. Option C fails for the same scoping reason, and organization administrator credentials are only valid within their assigned organization. Option D uses org admin credentials, which lack system-level authority even if the Organization field is left blank.

Memory tip: Think "blank = broad" - a blank Organization field + System Admin = system-wide scope. Filling in an org narrows the endpoint, and org credentials can never reach beyond their own org's boundary.

No community discussion yet for this question.