Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

VMware 2V0-15.25 Exam - Topic 2 Question 8 Discussion

Actual exam question for VMware's 2V0-15.25 exam
Question #: 8
Topic #: 2
[All 2V0-15.25 Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: C

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 a VM.

Option A is incorrect because Custom Groups do not affect vCenter tag visibility. Option B is incorrect because tag synchronization is not tied to a specific vCenter version as long as the vCenter is officially supported by VCF 9.x. Option D is irrelevant---VMware Tools has nothing to do with tag visibility.


Contribute your Thoughts:

0/2000 characters

Currently there are no comments in this discussion, be the first to comment!


Save Cancel