After school-district lab PCs are added to a new Carbon Black Cloud sensor group, they keep the old policy. What should the administrator inspect first?
Select an answer to reveal the explanation.
Short Explanation
If the lab PCs still wear the old badge, look at who stands first in the group line. Criteria rank and assignment order beat a reinstall every time.
Full Explanation
After school-district lab PCs are added to a new Carbon Black Cloud sensor group, they keep the old policy when group criteria rank and assignment order still favor an earlier match. Inspect criteria rank and assignment order first—not a sensor reinstall. If lab PCs still wear the old badge, look at who stands first in the group line. Checking whether vCenter tags were copied onto each lab VM fails by concept as a first step because CBC sensor-group assignment is driven by CBC criteria, not vCenter tags by default. Inspecting NSX-T T1 locale-service status on the lab overlay fails because T1 locale-service is unrelated to CBC policy assignment. Fully uninstalling and reinstalling every lab sensor before reviewing groups fails because reinstall does not fix rank order and wastes change windows. Exam caveat: first matching sensor group by rank wins; troubleshoot criteria and order before reinstall or SDDC distractions. Operational check: review group rank, adjust lab criteria or order so the new group matches first, confirm lab PCs show the new policy after re-evaluation, and avoid mass reinstall. Document group rank in the district CBC design so future lab OU changes do not silently rematch an older group.