While attempting to create a nested blueprint, a software architect is unable to locate the child blueprint under
Blueprints in the Design Canvas.
What would be a possible reason for this?
A.
The child blueprint is NOT entitled.
B.
The child blueprint is created as a private blueprint.
C.
The child blueprint is unpublished.
D.
The child blueprint is NOT marked as a component.
C
2
1
C
Definitely not A
https://docs.vmware.com/en/vRealize-Automation/7.3/com.vmware.vra.prepare.use.doc/GUID-977883EC-4C38-40A3-81F6-5DCA9C7866A4.html
1
0
Answer is C. Anyone who has used vRealize Automation has experienced how frustrating it is to forget to publish something. When you don’t publish a blue print, it will not appear in the list of blueprints on the design canvas. It happens to me all the time and you can easily replicate it, but you shouldn’t need to replicate it because if you are taking this test? You should already know!
Answer A – you don’t have to entitle it until you are ready to put it in a catalog. You aren’t putting it in a catalog (not yet), you are putting it inside another blueprint. This is easy to replicate too. Just try it.
2
0