CyberCertPrepMobile Security FundamentalsApp Distribution (Play Store / App Store)EASYFree question
An Android app developer wants Google Play to automatically handle multiple APKs for different CPU architectures (arm64-v8a, armeabi-v7a, x86_64). What is the recommended build artifact format that enables this without requiring the developer to manually create and manage multiple APKs?
- A.B. Android App Bundle (AAB), which includes all ABI splits and lets Play generate device-specific APKs
- B.A. Universal APK with all ABI libraries bundled
- C.C. APK Expansion Files (OBB) containing ABI-specific libraries
- D.D. Multi-APK publishing with separate version codes per ABI
Why A is correct
The Android App Bundle (AAB) format includes all ABI, screen density, and language resources in a single upload artifact. Google Play's dynamic delivery infrastructure then generates and serves device-specific split APKs. A universal APK includes all resources and is larger; it does not provide per-device optimization. OBB files are for large asset packs, not ABI splits. Multi-APK with separate version codes works but requires manual management and is the legacy approach replaced by AAB.
Know someone studying for Mobile Security Fundamentals? Send them this one.