mediummulti selectObjective-mapped

Which two statements accurately describe why source restriction and logging are often used together for administrative access?

Question 1mediummulti select
Full question →

Which two statements accurately describe why source restriction and logging are often used together for administrative access?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

Source restriction narrows the allowed origin space for administrative sessions.

This is correct because source filtering reduces where management traffic is permitted from.

B

Best answer

Logging improves visibility and accountability for what happened during administrative access.

This is correct because logs support review and investigation after the fact.

C

Distractor review

Logging removes the need for authentication.

This is wrong because visibility does not replace identity verification.

D

Distractor review

Source restriction works only when Syslog is disabled.

This is wrong because these controls do not conflict in that way.

E

Distractor review

Both controls exist only for guest wireless networks.

This is wrong because they are broad management-plane security measures.

Common exam trap

Common exam trap: answer the scenario, not the keyword

A frequent exam trap is to believe that logging can replace source restriction or that source restriction only works if logging is disabled. Candidates may incorrectly think that visibility through logs is enough to secure administrative access, ignoring the importance of limiting where management sessions can originate. Another mistake is to assume these controls are only relevant for guest wireless networks, which is false because they apply broadly to all management-plane security. Understanding that source restriction and logging serve distinct but complementary roles is critical to avoid this trap.

Technical deep dive

How to think about this question

Source restriction and logging are fundamental components of securing administrative access to Cisco network devices. Source restriction works by limiting the IP addresses or subnets from which management protocols like SSH, Telnet, or HTTP(S) can initiate sessions. This is typically enforced using access control lists (ACLs) applied to the management plane or interface level. By narrowing the allowed origin space, source restriction reduces the attack surface and prevents unauthorized hosts from even attempting to connect to the device's administrative services. Logging complements source restriction by capturing detailed records of administrative access attempts and activities. Cisco devices use Syslog or local logging buffers to record events such as successful or failed login attempts, command executions, and session terminations. This logging provides visibility and accountability, enabling network administrators to audit access, detect suspicious behavior, and perform forensic investigations after security incidents. Together, these controls form a layered defense that both prevents unauthorized access and supports incident response. A common exam trap is to assume that logging alone is sufficient for administrative security or that source restriction conflicts with logging. In reality, logging does not replace authentication or access filtering, and source restriction does not depend on logging being disabled. Both controls operate independently but synergistically. Practically, source restriction blocks unauthorized sources upfront, while logging ensures that all access attempts, whether allowed or denied, are recorded for review. This layered approach aligns with Cisco best practices for management-plane security in the CCNA context.

KKey Concepts to Remember

  • Source restriction limits administrative access by permitting management sessions only from predefined IP address ranges or subnets, reducing exposure to unauthorized hosts.
  • Logging records detailed information about administrative access attempts, including source IP, time, and commands executed, which supports auditing and forensic analysis.
  • Combining source restriction with logging enhances security by both preventing unauthorized access and providing accountability for permitted sessions.
  • Source restriction is implemented using access control lists (ACLs) or management plane protection features on Cisco devices to filter incoming administrative traffic.
  • Logging mechanisms such as Syslog or local buffer logs capture events related to administrative access, enabling network administrators to monitor and investigate incidents.
  • Source restriction does not replace authentication; it only narrows the origin of access, while authentication verifies user identity.
  • Logging does not eliminate the need for source restriction because visibility alone cannot prevent unauthorized access attempts.
  • Effective administrative access security requires layered controls, where source restriction reduces attack surface and logging provides post-event visibility.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Related practice questions

Related 200-301 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this 200-301 question test?

Source restriction limits administrative access by permitting management sessions only from predefined IP address ranges or subnets, reducing exposure to unauthorized hosts.

What is the correct answer to this question?

The correct answer is: Source restriction narrows the allowed origin space for administrative sessions. — Source restriction and logging are often used together because they help answer two different security questions. In practical terms, source restriction limits where administrative sessions may originate, while logging helps show what happened once access was attempted or granted. This combination improves both exposure reduction and post-event visibility. This is a strong layered-security reasoning item because it focuses on complementary controls rather than one-control thinking.

What should I do if I get this 200-301 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.