An administrator powers on a vCloud Automation Center 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.
A
0
1
http://pubs.vmware.com/vra-62/index.jsp#com.vmware.vra.tenant.administration.doc/GUID-7D135E80-C3C6-4ADB-8C02-A24EAB85B713.html
0
1
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 components 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 are not used that way. You approve the entire request, not components within.
0
0
One more point, before vRealize Automation 7’s converged blueprint, there was a concept of multi-machine blueprints. You were able to combine blueprints and specify startup orders. That was replaced by the converged blue print. Back in the ver 5 and 6 days, option A was probably correct. But not in the Ver 7 days.
0
0