An administrator completes a proof-of-concept with vRealize Automation using a standard deployment to test out its key provisioning use cases. vRealize Suite Lifecycle Manager (vRSLCM) is going to…

Question

Options

• ADelete the existing standard deployment.
• BChoose "Add Component" from the vRealize Automation environment card.
• CReview VMware Knowledge Base articles for steps to validate the PostgreSQL cluster health
• DCreate or import a product certificate in the locker with all of the existing and new product

• A
  3% (2)
• B
  7% (5)
• C
  10% (7)
• D
  79% (54)

Explanation

Before scaling out a vRealize Automation deployment using vRSLCM, a valid product certificate covering all nodes (existing and new) must be present in vRSLCM's Locker. The Scale-Out process replaces the existing single-node certificate with one that covers every node in the expanded topology, so vRSLCM requires that certificate to be in place before it can proceed.

Why the distractors are wrong:

• A is wrong because you do not delete the existing deployment - vRSLCM scales out the live environment in place, preserving your configuration.
• B is wrong because "Add Component" is used to add new vRealize products to an environment, not to scale out an existing product's nodes.
• C is wrong because reviewing KB articles for PostgreSQL health may be good practice, but it is not a required prerequisite step enforced by vRSLCM before initiating Scale-Out.

Memory tip: Think of the Locker as a security checkpoint - vRSLCM won't let your deployment "grow" until it has the keys (certificate) that cover the entire future footprint. New nodes need new names on the cert - load it in the Locker first.

No community discussion yet for this question.