300-715 · Question #284
An administrator needs to add a new third party network device to be used with Cisco ISE for Guest and BYOD authorizations. Which two features must be configured under Network Device Profile to…
The correct answer is C. CoA Type E. URL Redirect. When integrating a third-party network device with Cisco ISE for Guest and BYOD authorizations, the Network Device Profile must have the Change of Authorization (CoA) Type and URL Redirect features configured.
Question
An administrator needs to add a new third party network device to be used with Cisco ISE for Guest and BYOD authorizations. Which two features must be configured under Network Device Profile to achieve this? (Choose two.)
Options
- ATACACS
- BSNMP community
- CCoA Type
- DdACL
- EURL Redirect
How the community answered
(25 responses)- A12% (3)
- B4% (1)
- C80% (20)
- D4% (1)
Why each option
When integrating a third-party network device with Cisco ISE for Guest and BYOD authorizations, the Network Device Profile must have the Change of Authorization (CoA) Type and URL Redirect features configured.
TACACS is used for device administration (managing the NAD itself), not for user/device authentication or authorization in Guest/BYOD scenarios, which primarily use RADIUS.
SNMP community is for network monitoring and management of the NAD, not directly for the authentication, authorization, or interactive workflows of Guest/BYOD.
Change of Authorization (CoA) is critical for Guest and BYOD workflows, as ISE uses it to re-authenticate or re-authorize endpoints on the Network Access Device (NAD) after successful registration or onboarding, moving them to the appropriate network segment.
dACLs (downloadable ACLs) are policies applied to endpoints through an authorization profile, not a feature configured within the Network Device Profile itself for generic third-party device capabilities.
URL Redirect is fundamental for Guest and BYOD; it directs endpoints initially placed in a guest VLAN or with restricted access to the ISE guest or BYOD onboarding portal for registration or credential input.
Concept tested: Cisco ISE Network Device Profile for third-party devices
Source: https://www.cisco.com/c/en/us/td/docs/security/ise/3-0/admin_guide/b_ISE_admin_3_0/b_ISE_admin_3_0_chapter_010.html
Topics
Community Discussion
No community discussion yet for this question.