2V0-15.25 · Question #12
An administrator creates a tag for a virtual machine (VM) in VMware Cloud Foundation (VCF) Operations. When assigning the tag to the virtual machine In vCenter, the tag was not found. What is the…
The correct answer is C. The tag was not pushed to the vCenter instance. In VMware Cloud Foundation 9.0 Operations, tags created inside VCF Operations do not automatically appear in vCenter. Tags must be explicitly synchronized ("pushed") to the selected vCenter instance before they become usable for VM tagging within vCenter. This is because VCF…
Question
An administrator creates a tag for a virtual machine (VM) in VMware Cloud Foundation (VCF) Operations. When assigning the tag to the virtual machine In vCenter, the tag was not found. What is the cause of this error?
Options
- AThe tag was not pushed to Custom Groups.
- BThe vCenter version is incorrect.
- CThe tag was not pushed to the vCenter instance.
- DVM Tools is not installed.
How the community answered
(16 responses)- A6% (1)
- B13% (2)
- C81% (13)
Explanation
In VMware Cloud Foundation 9.0 Operations, tags created inside VCF Operations do not automatically appear in vCenter. Tags must be explicitly synchronized ("pushed") to the selected vCenter instance before they become usable for VM tagging within vCenter. This is because VCF Operations maintains its own metadata store for tags, super metrics, groups, and policies. The correct workflow is: Create the tag in VCF Operations. Push (synchronize) the tag to the appropriate vCenter instance. The tag then appears in vCenter's Tags & Custom Attributes section. Administrators can then assign the tag to VMs. If the push step is skipped, the tag exists only inside VCF Operations and cannot be referenced by vCenter, which is exactly the symptom described: tag not found when attempting to assign it to
Topics
Community Discussion
No community discussion yet for this question.