A healthcare company has mandated that all IP and DNS entries be allocated from an existing third-party IPAM solution. Also, for auditing purposes, all systems must handle user authentication via…

Question

Options

• AThe IPAM system is an upstream dependency and the LDAP system is a downstream
• BBoth the IPAM and LDAP systems are external, upstream dependencies of vRealize Automation.
• CBoth the IPAM and LDAP systems are external, downstream dependencies of vRealize
• DThe LDAP system is an upstream dependency and the IPAM system is a downstream

• A
  6% (1)
• B
  6% (1)
• C
  71% (12)
• D
  18% (3)

Explanation

Option C is correct because in this logical design, vRealize Automation (vRA) is the orchestrating platform that initiates requests outward - it sends IP allocation requests to IPAM and authentication requests to LDAP. In data flow terms, vRA sits upstream as the initiator, and IPAM/LDAP sit downstream as external receivers of those requests; they respond to vRA, not the other way around.

Why the distractors are wrong:

• A reverses only one relationship, calling IPAM upstream and LDAP downstream, but both systems occupy the same position relative to vRA - they're both recipients of outbound vRA requests, so the split treatment is incorrect.
• B confuses "upstream" with "prerequisite." While IPAM and LDAP must pre-exist for vRA to function, "upstream" in this data-flow context means the source of requests, which is vRA - not the external systems it calls.
• D is the mirror of A, reversing the labels but making the same structural error of splitting two identically-positioned systems into opposite roles.

Memory tip: Picture vRA as a river source. Everything vRA pushes requests toward flows downstream. IPAM and LDAP sit at the riverbank receiving those requests - they're downstream. If something fed into vRA (like a user triggering a blueprint), that would be upstream.

No community discussion yet for this question.