An administrator powers on a vRealize Automation Multi-Machine Service that includes Machine A and Machine B. The application on Machine A does not start correctly and displays the following error message:
Machine B not ready
What step should be taken to resolve this issue?
A. Change the startup order of the Multi-Machine Service.
B. Create a startup dependency in the Multi-Machine Service.
C. Define a startup delay in the Multi-Machine Service.
D. Adjust the startup approvals for the Multi-Machine Service.
Thank You Fred
The answer is B. What is a startup dependency? “Creating a dependency link from one item such as a service or application component to another service or application component guarantees that the task of creating the first item finishes successfully before a second task begins.” According to https://docs.vmware.com/en/vRealize-Automation/7.3/com.vmware.vra.prepare.use.doc/GUID-66C261D4-648E-4E66-8D20-CC87AFE44AA7.html
“To map a dependency on your design canvas, you draw a line from the dependent component to the component you are depending on. ”
The answer is not A because the topic of start up order concerns the start up order of the vRealize Automation elements, not of comonents in a blueprint.
The answer is not C because the startup delay is a setting within VMTools and with the Virtual Client’s VM properties, not something within blue prints
The answer is not D because approvals isn’t used that way. You improve the entire request, not components within.