What happens to an unsupervised iOS device when the "Meraki management" profile is removed?

Question

Options

• AThe "Meraki management" profile is removed. All configuration profiles that Systems Manager
• BThe "Meraki management" profile is removed. All configuration profiles that Systems Manager
• CThe "Meraki management" profile is removed and then pushed automatically by Systems
• DThe "Meraki management" profile cannot be removed.

• A
  5% (2)
• B
  70% (30)
• C
  19% (8)
• D
  7% (3)

Explanation

On an unsupervised iOS device, the user has full control over the management profile, so it can be removed - and when it is, Meraki Systems Manager loses its management anchor, causing all configuration profiles it had deployed to be automatically removed along with it. Option B correctly captures this cascade: the Meraki profile goes, and every configuration profile Systems Manager pushed goes with it.

Why the distractors are wrong:

• Option A appears nearly identical to B but likely differs in a key detail (such as stating managed apps are also removed, which isn't guaranteed on unsupervised devices since app removal requires additional conditions).
• Option C is wrong because automatic re-enrollment after profile removal describes supervised DEP-enrolled devices, not unsupervised ones - unsupervised devices don't phone home to re-enroll.
• Option D is the most common trap: profile removal is blocked on supervised devices, but the question specifies unsupervised, where the user retains that ability.

Memory tip: Think "U = User controls it" - Unsupervised means the User can pull the profile, and when they do, the configs follow. Supervised = Stuck (the org controls it, so the profile can't be removed).

No community discussion yet for this question.