The city adopted a tagging convention so later groups can collect permit, finance, and clinic workloads. Where should the operator apply those NSX tags?
Select an answer to reveal the explanation.
Short Explanation
City tags are stickers on the NSX objects themselves. Put them in Inventory Tags, or on the VM and segment tag fields, so groups can match them. vSAN, Horizon DEM, and the TOR switch are the wrong sticker pads.
Full Explanation
NSX tags are applied in Inventory under Tags, or on the tag fields of objects such as VMs and segments, so Groups can match them later for permit, finance, and clinic workloads. City tags are stickers on the NSX objects themselves. vSAN storage policies do not feed NSX tag membership. Horizon Dynamic Environment Manager profiles are EUC settings, not NSX tags. Physical top-of-rack switch labels are not stored as NSX tags on objects. Exam caveat: tagging conventions only help if operators apply tags consistently before building groups; untagged workloads will miss dynamic membership. Operational check: apply the adopted tags in Inventory Tags or on VM/segment tag fields, build a sample group that matches, confirm membership, and verify vSAN policies, Horizon DEM, and TOR labels were not used as the tag store. Document the civic rationale in the change record so the next operator can restate why the correct control matches the agency outcome, why each distractor fails by concept, and which NSX Manager view confirms the result after publish. Document the civic rationale in the change record so the next operator can restate why the correct control matches the agency outcome, why each distractor fails by concept, and which NSX Manager view confirms the result after publish.