What are two requirements for deploying a small deployment of vRealize Automation? (Choose two.)

Question

Options

• ACertificate Authority (CA)-signed certificate for all the components of deployment
• BUpgrading the existing vRealize Suite Lifecycle Manager
• CValid, fully-qualified domain name that can be resolved with both forward and reverse lookup
• DConfigured load balancers
• ESingle, static IPv4 and network address

• A
  3% (1)
• B
  3% (1)
• C
  88% (35)
• D
  8% (3)

Explanation

For a small (minimal) deployment of vRealize Automation, two foundational infrastructure requirements must be met:

Why C and E are correct: A valid FQDN with both forward (name → IP) and reverse (IP → name) DNS resolution (C) is required because vRA components communicate by hostname, and broken DNS causes service failures during and after deployment. A single static IPv4 address (E) is mandatory for a small deployment - vRA needs a stable, unchanging IP tied to that FQDN; DHCP-assigned addresses would break cluster communication.

Why the distractors are wrong:

• (A) CA-signed certificates are a best practice for production but not a hard requirement for small deployments - self-signed certificates are acceptable.
• (B) Upgrading vRealize Suite Lifecycle Manager is relevant only if you already have an existing vRSLCM environment; it is not a prerequisite for a fresh small deployment.
• (D) Load balancers are required for large/enterprise (clustered) deployments with multiple nodes, not for small single-node deployments.

Memory tip: Think of a small deployment as the "bare minimum to boot" - you just need to find the machine (DNS/FQDN = C) and reliably reach it at the same address every time (static IP = E). Load balancers and CA certs are "enterprise upgrades," not small-deployment basics.

No community discussion yet for this question.