Which answer accurately captures the Play In-App Updates API (immediate vs. flexible) and how does it help maintain security patch adoption?

• A.The update API is available from Android 12 onward, and an older handset falls back to a store deep link the app opens (the core library returns an unsupported result below that release); the security consequence is a patch adoption curve that lags on legacy devices, and a team relying on the API alone leaves them behind. A manual prompt covers the gap for those devices.
• B.The update API delivers a push notification to the handset, and the install proceeds in the background once the user taps it (the store client handles the download without opening the app); the security consequence is that a patch reaches users who rarely launch the app, and the immediate mode is a delivery priority rather than a blocking screen. Adoption improves for dormant installs.
• C.The Play In-App Updates API allows apps to prompt users to update without leaving the app; "immediate" mode forces a full-screen blocking update flow (suitable for critical security patches), while "flexible" mode downloads in the background and prompts the user at a convenient time. This reduces the window of exposure for vulnerabilities in older app versions.