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.Multi-APK publishing with a separate version code for every architecture, because Play always serves the highest code a device accepts (the console tracks each variant and its rollout)
• B.Expansion files carrying the architecture-specific libraries, because the store always delivers the base package first (the payload downloads afterward), and the loader picks the matching library
• C.A universal package with every library bundled inside, because the installer always selects the right one at runtime (the linker resolves the architecture), and the download size is the only cost
• D.Android App Bundle (AAB), which includes all ABI splits and lets Play generate device-specific APKs