Which ISE Portal Registers BYOD Devices Without Native Supplicants?

Implement BYOD device lifecycle operations Describe Cisco BYOD functionality

Answer Correct answer: C — Configure the Cisco ISE My Devices portal so employees can register personal devices that do not support native supplicant provisioning.

An engineer is designing a BYOD environment utilizing Cisco ISE for devices that do not support native supplicants. Which portal must the security engineer configure to accomplish this task?

BYOD
Client Provisioning
My Devices Correct Answer
MDM

Community Insight

The question tests which ISE BYOD portal serves devices lacking native supplicant support; the trap is choosing Client Provisioning because the word 'provisioning' sounds like the operation needed for devices that require software.

Cisco ISE's My Devices portal is the portal that lets employees register personal endpoints which cannot run a native supplicant. This page confirms answer C using the ISE admin guide wording, contrasts it with the BYOD and Client Provisioning portals, and summarizes community voting.

Picking B (Client Provisioning). Candidates see 'devices that do not support native supplicants' and assume the engineer must deliver a supplicant, posture agent, or compliance module, but Client Provisioning pushes software to endpoints that can run it — it does not register non-supplicant devices, which is what the question asks for.

Community Discussion (17 comments)

evdw 👍 1 Selected: C

You can provide a My Devices portal to enable employees to add and register their personal devices that do not support native supplicants and cannot be added using the Bring Your Own Device (BYOD) portal.

AsaHung 👍 1 Selected: C

i chosen C , My Devices Portal the B. Client Provisioning Portal is forces employees to download a posture agent on their devices that checks for compliance , and posture is not what this question is asking. Here is reference URL : and see Personal Device Portals tpoics https://www.cisco.com/c/en/us/td/docs/security/ise/3-2/admin_guide/b_ise_admin_3_2/b_ISE_admin_32_byod.html

817042b 👍 1 Selected: C

C. My Devices is a correct answer when the requirement is to register devices without native supplicant support. If this was a multiple‑choice exam question, sometimes they intend a specific nuance (like provisioning vs just registering), so one answer might be preferred. But strictly speaking, My Devices Portal is designed for that exact purpose as per the Cisco docs.

Cachaman 👍 1 Selected: C

C Some network devices that need network access are not supported by native supplicant provisioning and cannot be registered using the BYOD portal. However, employees can add and register personal devices, whose operating systems are not supported or do not have web browsers (such as printers, internet radios, and other devices), using the My Devices portal. https://www.cisco.com/c/en/us/td/docs/security/ise/3-0/admin_guide/b_ISE_admin_3_0/b_ISE_admin_30_byod.html

luismg 👍 2 Selected: C

https://www.cisco.com/c/en/us/td/docs/security/ise/3-0/admin_guide/b_ISE_admin_3_0/b_ISE_admin_30_byod.html

KnightHeart 👍 1 Selected: B

AI doubao said is B

SilentStock8 👍 1

AI will steer you wrong in a lot of questions.

XBfoundX 👍 1

Same link provided by the IlPerdan0

XBfoundX 👍 3

I will go for B too. the question is about design and put in production a solution for let authenticate devices that do not have native supplicant. The need to log in into the My device portal for add the device is not the right answer for me. In this guide is clear how to configure BYOD without the need of a native supplicant policy configured https://community.cisco.com/t5/security-blogs/ise-byod-registration-only-without-native-supplicant-or/ba-p/3099290 We can also define how many devices that does not support the native supplicant. After that we need to configure the specific authorization policies for these devices. https://www.google.com/search?sca_esv=584485115&sxsrf=AM9HkKl4Nf8vU-mivr0QzBoio-yaTCjJwQ:1700626451946&q=my+devices+portal+cisco+ise&tbm=vid&source=lnms&sa=X&ved=2ahUKEwik_8Cc39aCAxWIhv0HHV3eDxAQ0pQJegQICBAB&cshid=1700626456264194&biw=2400&bih=1138&dpr=0.8

XBfoundX 👍 1

SORRY LOOK THIS LINK HERE: https://community.cisco.com/t5/security-blogs/ise-byod-registration-only-without-native-supplicant-or/ba-p/3099290

denverfly 👍 3 Selected: B

The correct answer is - Client Provisioning. Client Provisioning is a portal in Cisco ISE that allows administrators to customize the settings for devices that connect to the network. This includes settings such as the device's username and password, the location of the compliance module, and the type of authentication that is required. For devices that do not support native supplicants, administrators can use the Client Provisioning portal to configure the device to use PEAP or TTLS authentication. PEAP and TTLS are both tunneling protocols that allow devices to authenticate to Cisco ISE even if they do not support native supplicants. The other options are not correct. The BYOD portal is used to manage the settings for a user's endpoint device. The My Devices portal is used by users to manage the settings for their own endpoint devices. MDM is a mobile device management platform that can be used to manage devices that connect to the network.

Cnoteone 👍 2 Selected: C

Thanks YmerG! As per : https://www.cisco.com/c/en/us/td/docs/security/ise/2-6/admin_guide/b_ISE_26_admin_guide/b_ISE_admin_26_byod.html#task_323AFE02F568400B93FFB3448D0CA3F3 My Devices Portals: Enables employees to add and register personal devices, including those that do not support native supplicant provisioning, and then manage them.

Han2022 👍 3

The key point of question is "Which portal must the security engineer configure to accomplish this task?" So security engineer should configure for that not a user. Answer is B Client Provisioning Reference: Official Guide - Page 562

YmerG 👍 3 Selected: C

Correct. look here: https://www.cisco.com/c/en/us/td/docs/security/ise/2-6/admin_guide/b_ISE_26_admin_guide/b_ISE_admin_26_byod.html#task_323AFE02F568400B93FFB3448D0CA3F3

kornalt 👍 2

Provided answer is correct (C) My Devices Portals: Enables employees to add and register personal devices, including those that do not support native supplicant provisioning, and then manage them. https://www.cisco.com/c/en/us/td/docs/security/ise/2-4/admin_guide/b_ISE_admin_guide_24/m_ise_devices_byod.html

YmerG 👍 1

Very helpful link. I agree with the answer

IlPerdan0 👍 1 Selected: B

We can configure that on CP portal. https://community.cisco.com/t5/security-blogs/ise-byod-registration-only-without-native-supplicant-or/ba-p/3099290

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Expert Analysis

Why the Answer Is Correct

Cisco's ISE administrator guide describes the My Devices portal as the employee-facing page that "Enables employees to add and register personal devices, including those that do not support native supplicant provisioning, and then manage them." The question asks which portal the security engineer must configure for exactly that population, so the documented match is My Devices (C). The workflow is: an administrative or sponsor-enabled portal is configured on ISE, the user authenticates, and the MAC address or device identity is registered into an endpoint identity group that policy can then authorize. Because the source answer key was recorded as unknown, the verdict here rests on the vendor documentation quoted repeatedly in the discussion, where kornalt, Cnoteone and YmerG all cite the same sentence from the BYOD admin guide. Nothing in the scenario mentions certificate enrollment, SCEP, or posture, which are the features that would point to a different portal.

Why the Other Options Are Wrong

The BYOD portal (A) is the self-service onboarding flow for devices that do carry a native supplicant — it chains guest/BYOD SSIDs, certificate provisioning and supplicant configuration, which is precisely the capability the described endpoints lack. Client Provisioning (B) is the ISE service that delivers supplicant, AnyConnect NAM, posture agent and compliance-module files to endpoints that can install them, so it assumes a supplicant-capable device and is a delivery mechanism rather than the registration portal the question asks about. MDM (D) configures integration with an external mobile device management server to pull compliance and device attributes, not a portal for registering personal devices. denverfly and Han2022 argued for Client Provisioning, but their reasoning describes provisioning settings rather than the registration portal task in the stem.

Community Comment Notes

Seven of the ten comments land on C, several quoting the admin guide line about devices that "do not support native supplicant provisioning"; evdw adds that such devices "cannot be added using the Bring Your Own Device (BYOD) portal." AsaHung notes that Client Provisioning "forces employees to download a posture agent" and that posture is not what the question is asking, which matches the scenario's silence on compliance. XBfoundX prefers B and argues that designing and producing a solution for authenticating non-supplicant devices is the real intent, while 817042b concedes a nuance about "provisioning vs just registering" but still concludes My Devices is "designed for that exact purpose." Han2022 and kornalt both stress that the question asks what the engineer configures, which favors the portal documented for non-supplicant registration.

Official Reference

Exam Strategy

Watch who performs the action in the stem: 'which portal must the security engineer configure' points to a portal whose documented purpose is registering devices without native supplicants, not to the provisioning service that installs software. Eliminate any option whose job is delivering a supplicant, posture agent or MDM integration, since the scenario gives those endpoints no supplicant at all. Do not let the comment vote split push you toward Client Provisioning — the correct choice follows the admin guide sentence, not the poll.

Frequently Asked Questions

Why is the Client Provisioning portal wrong for non-supplicant devices?

Client Provisioning delivers supplicant, posture and compliance software to endpoints that can run it; it does not register devices that have no native supplicant and cannot install one.

When should the BYOD portal be used instead of My Devices in ISE?

The BYOD portal drives self-service onboarding with supplicant and certificate provisioning for capable devices; My Devices covers registering endpoints that lack that supplicant support.

More 300-715 FAQ →

Related Analysis

← Back to 300-715 Study Guide