An administrator wants to prevent users from enrolling into an organization group (OG) that is used only as a logical container. Which OG configuration can be blanked out in order prevent users from…

Question

Options

• ALocale
• BGroupID
• CType
• DName

• A
  3% (1)
• B
  93% (37)
• D
  5% (2)

Explanation

Blanking out the GroupID prevents enrollment because the GroupID is the unique identifier users must enter (or that is auto-populated) during device enrollment to target a specific Organization Group. With no GroupID configured, the enrollment process has no way to route users into that OG, making it effectively invisible to enrolling devices - perfect for OGs serving only as structural/logical containers in the hierarchy.

Why the distractors are wrong:

• A. Locale - Controls regional/language settings for the OG; has no bearing on whether users can enroll into it.
• C. Type - Defines the OG's role in the hierarchy (e.g., Customer, Container, Global), but changing or blanking this does not block enrollment.
• D. Name - The display name is for administrative identification only; enrollment routing does not depend on it.

Memory tip: Think "GroupID = the enrollment door handle." If you remove the handle (blank the GroupID), users can see the door (the OG exists) but have no way to open it and get in.

No community discussion yet for this question.