350-701 Practice Question: Secure Network Access, Visibility and Enforcement
Exhibit
ISE Radius Live Log: Timestamp: 2025-03-10 10:00:00 User: CN=John Doe, OU=Users, DC=company, DC=com Endpoint MAC: 00:11:22:33:44:55 Auth Protocol: PEAP (MSCHAPv2) Result: Authentication succeeded Authorization Policy: Corporate_Access Authorization Profile: Standard_Access Session Attributes: Cisco-av-pair = "device-traffic-class=voice"
Refer to the exhibit. A network administrator reviews the ISE live log for a successful 802.1X authentication. After authentication, the user is unable to make VoIP calls. What is the most likely cause?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The authorization profile does not include a voice VLAN.
The authorization profile applied to the user does not include a voice VLAN assignment, which is required for VoIP traffic. Even though the RADIUS attribute 'device-traffic-class=voice' is present, this only marks the traffic for QoS and does not assign a VLAN. Without a voice VLAN configured in the authorization profile, the phone cannot obtain the necessary VLAN for voice services. Option A is incorrect because whether the phone is configured for 802.1X is irrelevant; the issue is about VLAN assignment. Option B is incorrect because the RADIUS attribute 'device-traffic-class=voice' is correctly formatted for QoS marking, not for VLAN assignment. Option C is incorrect because multi-domain mode is used for scenarios with a phone behind a PC, but here the user's phone is authenticating directly and the problem is the lack of voice VLAN in the authorization profile.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The user's phone is not configured for 802.1X.
Why it's wrong here
The log shows the user's PC authenticated; the phone may not be the authenticated device.
- ✗
The RADIUS attribute 'device-traffic-class=voice' is incorrect.
Why it's wrong here
This attribute is used for QoS and is correctly formatted.
- ✗
The switch port is not configured with 'authentication host-mode multi-domain'.
Why it's wrong here
Multi-domain mode is needed if a phone and PC share the same port, but not the cause of unable to make calls.
- ✓
The authorization profile does not include a voice VLAN.
Why this is correct
VoIP requires a dedicated voice VLAN; without it, the phone cannot communicate with the call manager.
Visual reference
Quick reference
AAA Protocol Comparison
| Protocol | Port(s) | Encryption | Transport | Primary Use |
|---|---|---|---|---|
| RADIUS | 1812 / 1813 | Password only | UDP | Network access control |
| TACACS+ | 49 | Full packet | TCP | Device administration |
| Diameter | 3868 | Full session | TCP / SCTP | Carrier / mobile networks |
| 802.1X | — | EAP-based | Layer 2 | Port-based access control |
TACACS+ encrypts the entire packet; RADIUS only encrypts the password field — a key exam distinction.
Go deeper
Related to this question
About these practice questions
This 350-701 question is part of Courseiva's 978-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 350-701 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 350-701 exam.