A design review for the city’s first GBP rollout debates starting with dozens of hyper-granular groups versus a few coarse groups refined over time. Which approach is more practical?
Select an answer to reveal the explanation.
Short Explanation
Launch day is a sketch, not a museum catalog. A handful of clear clubs—users, servers, cameras—beats 400 empty micro-groups nobody can operate. Refine once the city is actually using the badges.
Full Explanation
Practical GBP rollouts favor a limited initial group taxonomy with clear policy intent, then iterative refinement as application dependencies are understood. Instant hyper-granular sprawl creates operational burden and mis-tag risk before value appears. Per-VM groups on day one, delaying GBP for exhaustive pair ACLs, or grouping only by underlay interface without workload identity undermine usable microsegmentation.