Which of the following identifies the security risk of using a public USB charging station ("juice jacking") and what controls mitigate it on both Android and iOS?

• A.The exposure is limited to malware pushed over ADB, and iOS is immune to the whole class (Apple never shipped an equivalent debug bridge, with the Lightning port carrying no developer protocol); the Android mitigation is to leave USB debugging switched off, and a charge-only cable adds nothing on a handset that already refuses the connection: every modern build ships with the developer options hidden. on a supported release.
• B.Modern USB-C requires mutual authentication before data flows, and the specification mandates a certificate exchange between the port and the peripheral (the USB-IF authentication protocol was added in the 3.1 revision, with a signed certificate on every compliant charger); juice jacking is obsolete on current hardware, and a data blocker is a legacy accessory: the handset always refuses an unauthenticated data path.
• C.Juice jacking reaches devices with an unlocked bootloader alone, and a production handset refuses the enumeration a malicious station attempts (the boot chain verifies each USB driver signature at load time, with an unsigned peripheral rejected outright); the mitigation on both platforms is to leave the bootloader locked, and a data blocker addresses a threat that never materializes on retail hardware: every stock device already declines the pairing request the station sends.