A customer will use the vRealize Automation platform for production and development deployments to the same vSphere cluster. One of their vSphere templates will only be licensed for use in development and must not be used for production.
The customer has defined a tag category called `environment` with three possible values `development`, `test` and `production` to differentiate the environments.
Which two design decisions will ensure that the requirements are met? (Choose two.)
To ensure that the vSphere template licensed for development is not used in production, the correct design decisions are to define a tag of 'environment:development' on the licensed image mapping and to define a tag of 'environment:development' in all development Cloud Templates. The tag on the image mapping ensures that the image can only be used in the development environment, while the tag on the Cloud Templates enforces the constraint that only development images can be utilized for development deployments.
Since production and development VMs are in the same cluster, the cloud zone cannot be used as a point of separation - so A and E are out. The question only mentions that the license is for development, not production. So it doesn't make sense to put a production tag on the image mapping. B is out. In addition, the question doesn't say *which* kind of tag, so it is legit to answer C & D. The image gets the capability tag of 'dev' and the cloud template gets the constraint tag of 'dev'.
A and C. The Image Mapping has a constraint tag, not capability tag.
wrong ! You can create capability tags on compute resources, cloud zones, images and image maps, and networks and network profiles. https://docs.vmware.com/en/vRealize-Automation/8.10/Using-and-Managing-Cloud-Assembly/GUID-8E630DEA-4732-45FC-9655-6933D55818C1.html
I would set the tag environment:development on the Image Mapping and use it as a constraint in the corresponding cloud template. (C and D)
C and D
I think AE
C , D are corrected
B and E