How Are Certificates and Supplicants Deployed to Mobile Devices?
Which method is used to deploy certificates and configure the supplicant on mobile devices to gain access to network resources?
Community Insight
The question tests whether you know the full ISE onboarding method (registration + client provisioning + certificate enrollment), and the trap is picking a single sub-component such as SCEP or client provisioning.
Cisco ISE BYOD onboarding is the workflow that registers a mobile device, pushes a native supplicant profile, and enrolls a client certificate so the device can authenticate with 802.1X. This page confirms why BYOD onboarding, not SCEP or MAC authentication bypass, is the correct answer for certificate-plus-supplicant deployment.
Many learners choose SCEP (D) because certificates are mentioned, but SCEP is only an enrollment protocol and configures no supplicant, no SSID, and no device registration.
Community Discussion (55 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
BYOD onboarding is the end-to-end Cisco ISE workflow that takes an unknown personal smartphone or tablet, registers it through the self-service portal, applies a client provisioning policy that pushes the native supplicant profile (SSID, EAP method, trusted CA chain), and then issues the device a client certificate for EAP-TLS. Because the certificate and the supplicant settings are both delivered inside this single onboarding flow, it is the only option that satisfies both halves of the question. As andrewj511 puts it, "At the heart of the BYOD solution is the network supplicant provisioning process." The onboarding method is also what enforces posture and authorization conditions afterwards, which is why the devices can be trusted to reach protected network resources.
Why the Other Options Are Wrong
MAC authentication bypass (B) identifies a device by its MAC address and requires no supplicant and no certificate, so it cannot deploy either. Client provisioning (C) is a real ISE policy, but it is a step inside onboarding that supplies the supplicant profile and CA information rather than the complete method that also registers the device and issues the identity certificate. SCEP (D) is only an enrollment protocol for transporting a certificate request to a CA; on its own it never touches the supplicant profile or the SSID configuration. ffsilveira10 argued the question never says the device is personally owned, but ISE's onboarding terminology is the vendor's named answer for exactly this provisioning scenario, and the certificate cannot be installed for 802.1X without the supplicant being configured alongside it.
Community Comment Notes
Most learners land on the same option: karmaomar states flatly that the answer is BYOD onboarding, and itisfakemaillol, Raajaa and 4pelos agree, with 4pelos pointing to ISE's tools for letting employees securely use personal devices on the corporate network. Tuxzinator's write-up for client provisioning is a useful description of the sub-process — "Client provisioning is a process of deploying network settings, certificates" — but it describes a component of onboarding rather than the overall method the question asks for. mecacig953 captures the fastest elimination rule: "Supplicant in the question disqualifies D", since SCEP is certificate-only. A minority backs SCEP on the theory that certificate deployment equals enrollment, but the supplicant requirement in the stem defeats that reading.
Official Reference
Exam Strategy
When a question pairs two deliverables (certificate + supplicant, or profile + posture), reject answers that cover only one of them and look for the umbrella workflow name. In Cisco ISE questions, the umbrella is usually the onboarding or provisioning policy, while protocols such as SCEP, RADIUS or EAP are just mechanisms used inside it.
Frequently Asked Questions
Why isn't SCEP (D) the answer if certificates are involved?
SCEP only carries the certificate request to a CA; it does not register the device or configure the native supplicant, SSID, and EAP settings that onboarding delivers.
What does ISE client provisioning push to an iOS or Android device?
It delivers the native supplicant profile (SSID, EAP-TLS/PEAP settings) and trusted CA chain, which is why it is a step within BYOD onboarding rather than the whole method.