Skip to content
Practice tests · 44 items

Mobile Application Security practice test

The Android and iOS security models, secure storage with the Keystore, Keychain and Secure Enclave, exported components, deep links and WebViews, certificate pinning and its rotation, root detection and attestation, reverse engineering of apps, and the on-device AI features that bring prompt injection to the phone. The pool for this topic holds 13 easy, 20 medium and 11 hard items. Each answer comes with its reasoning and a link to the question or concept page it was drawn from.

Configure a test
Topic
Difficulty
Questions
13 in this pool · about 7 min
Reveal answers
Sign in to startFree account required · retakes favour new items

Sample items with answers

easy · sample
What does the Android application sandbox primarily rely on to keep one app's files away from another app?
Encrypting every app's files with a key derived from the user's PIN
✓A separate Linux user ID for each app, plus SELinux policy
Google Play reviewing apps for code that reads other apps' data
The Java virtual machine refusing file access outside the app's package

Each app gets its own UID, so ordinary kernel file permissions keep its private directory away from other apps, and SELinux confines app domains further. Play review and the runtime are not the isolation mechanism.

easy · sample
Why can an API key embedded in a mobile app not be kept secret?
✓Every user receives the app, so the key can be extracted from the package or observed at runtime
App stores publish the decompiled source of every app they distribute, including all embedded configuration values
Mobile operating systems log all string constants used by apps
Keys are only secret if they are longer than 256 bits

Anything shipped in the binary is available to whoever installs it: static analysis finds constants, and instrumentation reads values when they are used. Authenticate users instead and keep third-party keys on the backend.

After the test

Choosing from options is easier than reasoning it out in front of a panel. These pages make you reason it out: