An administrator wants to use constraint tags to deploy cloud templates to a particular storage with a capability tag assigned; however, not all projects have access to this storage.
Which two tag formats can be defined at the cloud template level in order to ensure that cloud templates are deployed on this particular storage, whenever possible, and fail if not available? (Choose two.)
In order to ensure cloud templates are deployed on the specified storage whenever possible and fail if not available, constraint tags must be used with a 'hard' requirement. The hard requirement can be represented in two ways: with the 'hard' modifier explicitly (key:value:hard) or simply as key:value which is treated as a hard requirement by default. Hence, both key:value:hard and key:value satisfy this condition.
Answer is D & E
C cannot be the answer as this is the opposite of what is required. It can only be D and E despite both tags doing the same thing: https://docs.vmware.com/en/vRealize-Automation/services/Using-and-Managing-Cloud-Assembly/GUID-C8C335F4-9623-401C-825E-6F5B2B3C6507.html
key:value is a hard tag too.
D and E are the same thing (hard tag)
Let's go through the answers: A. value:key - No, this is not how key:value pairs work B. key:value:soft - No, this means it can be overridden C. !key:value - No, this is the inverse of the constraint D. key:value:hard - Yes (although key:values are hard by default) E. key:value - Yes (although this is the same as D)
From ICM 7-10 Multiple tag modifiers are available: • key:value • key:value:hard • key:value:soft • !key:value The hard modifier indicates that the constraint tag is a requirement. If the constraint cannot be satisfied, then deployment fails. key:value is synonymous with key:value:hard. The soft modifier indicates that the constraint tag is a preference. If vRealize Automation can find a resource that satisfies the constraint tag, then vRealize Automation uses that resource. If vRealize Automation cannot find a resource that satisfies the constraint tag, then the deployment can proceed using another resource even though it does not satisfy the constraint tag. The ! modifier negates the constraint tag. Then D&E are correct
Answer is correct CD , hard is required , actually it's by default so
Correct answer is D , E
Answer is D and E
Answer is D and E The following modifiers can be added to the <key:value> tags: • <key:value>:hard • <key:value>:soft • !<key:value> The hard modifier indicates that the constraint tag is a requirement. If the constraint cannot be satisfied, then deployment fails. The key:value tag is synonymous with the key:value:hard tag. Taken from Aria Automation ICM 8.10 Lesson Book -> Hard, Soft, and Not Modifiers section