Which enrollment method must be used when containerization is required on BYOD Android devices managed by Systems Manager?

Question

Options

• AAndroid Enterprise utilizing a Work Profile
• BSystems Manager network ID
• CAndroid Business utilizing a BYOD Profile
• DSystems Manager container ID

• A
  81% (29)
• B
  3% (1)
• C
  6% (2)
• D
  11% (4)

Explanation

Android Enterprise with a Work Profile is the correct answer because it is the industry-standard enrollment method specifically designed to containerize corporate data on BYOD Android devices - it creates a separate, encrypted work container on the device while leaving the personal partition untouched, satisfying both security and privacy requirements in Cisco Meraki Systems Manager.

Why the distractors are wrong:

• B (Systems Manager network ID) - "Network ID" is not an enrollment method in Systems Manager; it's fabricated terminology that does not correspond to any real MDM feature.
• C (Android Business utilizing a BYOD Profile) - "Android Business" is not a real platform or enrollment mode; the correct branding is Android Enterprise, and "BYOD Profile" is not a defined enrollment type.
• D (Systems Manager container ID) - Again, a made-up identifier; Meraki Systems Manager does not use a "container ID" as an enrollment method.

Memory tip: Think "Enterprise = Encryption boundary." Android Enterprise Work Profile creates a hard container (work/personal split), which is exactly what BYOD containerization demands - if you see "BYOD + Android + container" on an exam, anchor to Android Enterprise Work Profile every time.

No community discussion yet for this question.