220-802 · Question #844
A small library has an integrated switch and router that is not wireless. All of the public PCs in the library are connected to the device. Which of the following is the FIRST thing the library…
The correct answer is C. Change the default user name and password. The first and most critical step to securing any network device is changing the factory-set default credentials, which are publicly known and exploitable by anyone.
Question
A small library has an integrated switch and router that is not wireless. All of the public PCs in the library are connected to the device. Which of the following is the FIRST thing the library should do to deter curious patrons from interfering with the device?
Options
- AConfigure DNS to resolve externally rather than internally
- BEnable MAC filtering to permit public PCs
- CChange the default user name and password
- DSet up the DHCP server to use a different gateway option
How the community answered
(21 responses)- A5% (1)
- B5% (1)
- C90% (19)
Why each option
The first and most critical step to securing any network device is changing the factory-set default credentials, which are publicly known and exploitable by anyone.
Configuring DNS for external resolution affects name resolution behavior but does nothing to prevent access to the device's management interface.
MAC filtering controls which client devices can connect to the network, not who can log into the router/switch administration console.
Network devices ship with well-known default usernames and passwords that attackers and curious users can easily look up online. Changing the default credentials is the foundational first step in securing a device, as it prevents unauthorized access to the administrative interface before any other hardening measures are applied. All other security configurations are irrelevant if the admin interface remains accessible via defaults.
Changing the DHCP gateway option affects client network routing but does not restrict access to the device itself.
Concept tested: Default credential hardening for network devices
Source: https://www.cisco.com/c/en/us/support/docs/ip/access-lists/13608-21.html
Topics
Community Discussion
No community discussion yet for this question.