hardMultiple Choice
220-1202 Practice Question: A company deploys a custom app via MDM to Android…
A company deploys a custom app via MDM to Android devices. Users report that the app crashes immediately upon launch. The app works fine on the developer's test device. What is the most likely cause?
⚠ Common exam trap
The CompTIA A+ exam often tests the distinction between installation-time failures (certificate, storage) and runtime failures (API level, missing libraries). The trap here is that candidates may incorrectly attribute a crash to MDM profile corruption or certificate issues, when the actual root cause is an API level mismatch that only manifests at launch.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The app requires a specific Android API level that is not present on the deployed devices.
The most likely cause is that the app requires a specific Android API level (e.g., a minimum SDK version) that is not present on the deployed devices. Since the app works on the developer's test device (which likely has a newer or matching API level), but crashes on the target devices, this indicates a compatibility mismatch. MDM deployment does not alter the device's API level, so the app's manifest-defined requirements are not met, leading to an immediate crash on launch.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The MDM profile is corrupt and needs to be re-pushed.
Why it's wrong here
A corrupt MDM profile would disrupt enrolment, policy delivery or app installation, but the app installs and then crashes at runtime. Re-pushing profiles is correct when devices lose management state or configuration, not when a launched app fails on every device identically.
- ✓
The app requires a specific Android API level that is not present on the deployed devices.
Why this is correct
Android apps declare a minimum SDK version in their manifest. If deployed devices run an older API level than that minimum, the app cannot load its required runtime components and crashes at launch, whereas the developer's newer test device meets the threshold.
- ✗
The devices have insufficient storage space.
Why it's wrong here
Insufficient storage typically prevents installation or causes gradual failure, not an immediate crash at launch on every device. Storage checks are the right diagnostic when installs fail or apps misbehave intermittently, but a consistent instant crash points to signing or compatibility instead.
- ✗
The app is not signed with the correct enterprise certificate.
Why it's wrong here
An incorrectly signed app fails installation or is rejected by the package installer; Android does not launch it and then crash. Signing certificates are the correct focus when deployment itself is blocked, whereas a successful install followed by an instant crash indicates an API or runtime incompatibility.
About these practice questions
Courseiva writes every 220-1202 question from scratch — 687 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 220-1202 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 220-1202 exam.