Match each service to the kind of problem it most directly helps solve.
Drag a concept onto its matching description — or click a concept then click the description.
Hostname works incorrectly or cannot be resolved into IP information
Clients need automatic IP configuration
Device timestamps do not line up consistently
Administrators need centralized event and log collection
⚠ Common exam trap
A common trap is confusing the roles of RADIUS and TACACS+, or thinking that services like DNS or DHCP have overlapping functions. Remember that DNS resolves names, DHCP assigns IPs, FTP transfers files, SSH secures remote access, RADIUS handles network access, and TACACS+ handles device administration.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
DNS - remembering IP addresses; DHCP - manual IP configuration; FTP - file transfers; SSH - encrypted remote access; RADIUS - network access; TACACS+ - device administration
DNS solves the problem of remembering IP addresses. DHCP eliminates manual IP configuration. FTP enables file transfers. SSH provides encrypted remote access. RADIUS and TACACS+ are AAA protocols, with RADIUS commonly used for network access and TACACS+ for device administration.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
DNS - remembering IP addresses; DHCP - manual IP configuration; FTP - file transfers; SSH - encrypted remote access; RADIUS - network access; TACACS+ - device administration
Why this is correct
This option is correct because each pairing directly addresses the core problem each protocol solves. DNS translates human-friendly hostnames into IP addresses, DHCP eliminates manual IP configuration by dynamically assigning addresses, FTP is the standard protocol for transferring files over a network, SSH provides encrypted remote access to network devices, RADIUS authenticates users seeking network access, and TACACS+ authorizes commands for device administration.
DNS - file transfers; DHCP - encrypted remote access; FTP - remembering IP addresses; SSH - manual IP configuration; RADIUS - device administration; TACACS+ - network access
Why it's wrong here
It misassigns each service's primary function. DNS does not handle file transfers, DHCP does not provide encryption, FTP does not resolve hostnames, SSH does not assign IPs, RADIUS is not for device administration, and TACACS+ is not for network access.
When this WOULD be correct
This would be correct in a question asking to match services to problems in a deliberately scrambled, non-standard scenario where each service is misassigned to a different problem type, such as a trick question testing attention to detail rather than actual knowledge.
DNS - encrypted remote access; DHCP - file transfers; FTP - manual IP configuration; SSH - remembering IP addresses; RADIUS - device administration; TACACS+ - network access
Why it's wrong here
This option is incorrect because it reverses and scrambles the primary purposes of the services. DNS does not provide encrypted remote access—that is SSH's role—and DHCP does not transfer files, which is FTP's function; FTP does not handle manual IP configuration (DHCP does), and SSH does not remember IP addresses (DNS does). Additionally, RADIUS is designed for network access authentication, not device administration, while TACACS+ is used for device administration, not for controlling network access.
When this WOULD be correct
If the question asked to match services to problems they solve in a reversed or scrambled order where the pairs are intentionally misaligned but each service is paired with a problem it actually solves (e.g., DNS - name resolution, DHCP - IP assignment, etc.), then this option would be correct if the pairings were correct. However, here the pairings are incorrect.
DNS - manual IP configuration; DHCP - remembering IP addresses; FTP - encrypted remote access; SSH - file transfers; RADIUS - network access; TACACS+ - device administration
Why it's wrong here
It misattributes the core problems. DNS does not assign IPs, DHCP does not resolve names, FTP does not encrypt sessions, SSH does not transfer files, and while RADIUS and TACACS+ are correctly paired, the other mismatches make this option wrong.
When this WOULD be correct
This option would be correct if the question asked to match services to problems they solve in a reversed or misaligned manner, such as 'Match each service to a problem it does NOT solve' or 'Match each service to a common misconception.'
Option-by-option analysis
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The 200-301 exam frequently reuses these exact scenarios with slightly different constraints.
Why this is correct
This option is correct because each pairing directly addresses the core problem each protocol solves. DNS translates human-friendly hostnames into IP addresses, DHCP eliminates manual IP configuration by dynamically assigning addresses, FTP is the standard protocol for transferring files over a network, SSH provides encrypted remote access to network devices, RADIUS authenticates users seeking network access, and TACACS+ authorizes commands for device administration.
Why this is wrong here
This option mismatches services to problems: DNS resolves names, not file transfers; DHCP automates IP config, not encryption; FTP transfers files, not name resolution; SSH provides encrypted remote access, not manual IP config; RADIUS handles network access, not device admin; TACACS+ manages device admin, not network access.
★ When this WOULD be the correct answer
This would be correct in a question asking to match services to problems in a deliberately scrambled, non-standard scenario where each service is misassigned to a different problem type, such as a trick question testing attention to detail rather than actual knowledge.
Why candidates choose this
Candidates may confuse the functions of similar protocols (e.g., RADIUS vs TACACS+) or misremember which service solves which problem, especially under time pressure or when relying on superficial similarities like 'access' or 'remote'.
Why this is wrong here
DNS does not provide encrypted remote access; that is SSH's role. DHCP does not handle file transfers; FTP does. FTP does not handle manual IP configuration; DHCP automates that. SSH does not remember IP addresses; DNS does.
★ When this WOULD be the correct answer
If the question asked to match services to problems they solve in a reversed or scrambled order where the pairs are intentionally misaligned but each service is paired with a problem it actually solves (e.g., DNS - name resolution, DHCP - IP assignment, etc.), then this option would be correct if the pairings were correct. However, here the pairings are incorrect.
Why candidates choose this
Candidates may confuse the functions of services (e.g., thinking DNS provides encryption due to DNSSEC, or mixing up DHCP and FTP roles) or misread the matching pairs, leading to a plausible but incorrect assignment.
Why this is wrong here
This option incorrectly maps DNS to manual IP configuration (DNS resolves names to IPs, not configures IPs), DHCP to remembering IP addresses (DHCP automates IP assignment, not memorization), FTP to encrypted remote access (FTP is not encrypted), SSH to file transfers (SSH is for secure remote access, not file transfers), and TACACS+ to device administration (TACACS+ is for network access, while RADIUS is for device administration).
★ When this WOULD be the correct answer
This option would be correct if the question asked to match services to problems they solve in a reversed or misaligned manner, such as 'Match each service to a problem it does NOT solve' or 'Match each service to a common misconception.'
Why candidates choose this
Candidates may confuse the functions of similar services (e.g., RADIUS vs. TACACS+) or misremember which service handles encryption, file transfers, or IP configuration, leading to swapped mappings.
Analysis generated from the official 200-301blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Visual reference
Quick reference
| 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
Learn chapter
Configuring AAA with TACACS+ and RADIUS on IOS XE
Key term
AAA
AAA (Authentication, Authorization, and Accounting) is a security framework that controls who can access a network, what they are allowed to do, and tracks what they did.
Key term
FTP
FTP, or File Transfer Protocol, is a standard network protocol used to transfer files between a client and a server over a TCP/IP network.
About these practice questions
One of 1,389 original 200-301 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 200-301 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 200-301 exam.