What happens if multiple resources in a provisioning request meet conflicting hard constraints?
What happens if multiple resources in a provisioning request meet conflicting hard constraints?
When multiple resources meet conflicting hard constraints in a provisioning request, soft constraints are used as a tiebreaker to select the actual resource used. This serves to refine the selection process and ensure the most suitable resource is chosen when hard constraints alone cannot determine a clear winner.
Answer is "D" Exp.: - If tags on the project conflict with the tags in the cloud template, the tags from the project take precedence. - Similar to priority matches, if multiple resources meet a hard constraint, soft constraints are used as a tiebreaker to select the actual resource used in the deployment.
i think its C) If you have a series of hard and soft constraints on a specific resource type, the soft constraints can also serve as tie breakers. That is, if multiple resources meet a hard constraint, the soft constraints are used to select the actual resource used in the deployment. Link: https://docs.vmware.com/en/vRealize-Automation/8.1/Using-and-Managing-Cloud-Assembly/GUID-C8C335F4-9623-401C-825E-6F5B2B3C6507.html
Answer is C. Soft contraints are the tie breaker. This article spells it out exactly! https://docs.vmware.com/en/VMware-Aria-Automation/SaaS/Using-Automation-Assembler/GUID-C8C335F4-9623-401C-825E-6F5B2B3C6507.html
The correct answer is C. From the lab, it is also well explained. "If multiple resources meet a hard constraint soft constraints are used as a tiebreaker to select the actual resource used in the deployment"
Answer is D Reference: https://docs.vmware.com/en/vRealize-Automation/8.1/Using-and-Managing-Cloud-Assembly/GUID-C8C335F4-9623-401C-825E-6F5B2B3C6507.html Note: In projects and blueprints, the failOnConstraintMergeConflict flag modifies the behavior of constraints. When this flag is set to true, if there is a conflict between project constraints and blueprint constraints, the request will fail. If the flag is not present or set to false, the project constraints take precedence over the blueprint constraints.