What happens if multiple resources in a provisioning request meet conflicting hand constraints?

Question

Options

• ARound robin is used to select only one of the conflicting tags.
• BSoft constraints are used as a tiebreaker.
• CTags from the cloud template take precedence.
• DTags from the project take precedence.

• A
  6% (1)
• B
  6% (1)
• C
  13% (2)
• D
  75% (12)

Explanation

https://docs.vmware.com/en/vRealize-Automation/8.0/Using-and-Managing-Cloud- Assembly/GUID-C8C335F4-9623-401C-825E-6F5B2B3C6507.html How constraint tags work on projects When configuring Cloud Assembly resources, cloud administrators can apply constraint tags on projects. In this way, administrators can apply governance constraints directly at the project level. All constraints added at this level are applied to every cloud template requested for the applicable project, and these constraint tags take precedence over other tags. If constraint tags on the project conflict with constraint tags on the cloud template, the project tags take precedence, thus allowing the cloud administrator to enforce governance rules. For example, if the cloud administrators creates a location:london tag on the project, but a developer places a location:boston tag on the cloud template, the former will take precedence and the resource is deployed to infrastructure containing the location:london tag.

No community discussion yet for this question.