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?
If the app targets a higher API level than the device's OS, it will crash on launch due to missing system features.
Why this answer
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.
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.
How to eliminate wrong answers
Option A is wrong because a corrupt MDM profile would typically cause deployment failures (e.g., app not installing or configuration not applying), not a crash upon launch of an already-installed app. Option C is wrong because insufficient storage space would prevent installation or cause a different error (e.g., 'insufficient storage' message), not an immediate crash after the app is already installed and launched. Option D is wrong because an incorrect enterprise certificate would prevent the app from installing at all (due to signature verification failure), not cause a crash after successful installation and launch.