Read a sample: 1. A Method for Reading Configurations
A configuration question is a small reading problem disguised as a networking problem. You may recognize every command in a snippet and still choose the wrong answer if you overlook where a command applies, reverse a direction, or assume that a configured setting is working.
The goal of this book is to make your reading more deliberate. Rather than looking at a few familiar words and jumping to a conclusion, you will build an answer from evidence. First identify what the snippet contains. Then determine what the relevant commands are intended to do. Finally, compare that conclusion with the answer choices, rejecting statements that go beyond what the configuration establishes.
Consider the difference between these two claims:
- “The interface is configured with an IPv4 address.”
- “Hosts on the connected network can reach the internet.”
The first may be directly supported by an ip address command. The second depends on much more: interface state, addressing, routing, filtering, and conditions elsewhere in the network. A configuration can express an intention without proving that the intended service is operating.
That distinction will serve you throughout this book. Interfaces, access lists, and management settings all have their own command syntax, but the reading method stays remarkably consistent.
Start by finding the task. Are you being asked to identify an address, interpret an access-list entry, determine where filtering is applied, or decide what is required for a login?
The wording matters. “What is configured?” calls for a different level of evidence than “What will a packet do?” A packet-treatment question may require an interface, direction, complete rule order, and a traffic description. A question about a configured address may require only the relevant interface block.
Read the stem and the configuration first. If the format allows it, delay evaluating the answer choices until you have made a short prediction in your own words. This reduces the chance that an attractive distractor will become your starting assumption.
A useful prediction need not be polished. It might be:
> The address is configured on GigabitEthernet0/0, and the interface is administratively enabled. Its operational state is not shown.
You can then look for the choice that says essentially that, rather than trying to make the snippet fit a choice that sounds familiar.
Use the following process for each configuration. With practice, the steps become quick mental checks rather than a lengthy procedure.
Notice what the question tells you about the device. Is it a router, a switch, or simply a device running Cisco IOS-style commands? Is a topology provided? Are you seeing a complete configuration or an excerpt?
Do not fill gaps with a favorite lab topology. An interface description may suggest what a cable is meant to connect to, but it does not independently verify the neighbor. A snippet that contains no routing configuration does not necessarily prove that no routes exist elsewhere in the device’s full configuration.
Treat the displayed material as evidence with boundaries. You can interpret the lines shown and any facts explicitly supplied in the question. When something important is absent, decide whether the question presents the snippet as complete for that purpose or merely leaves the fact unknown.
A command’s meaning depends partly on where it appears. An interface command applies to the interface block that contains it. A line-configuration command applies to the specified console or virtual terminal lines. An access-list entry defines matching and action rules within an ACL; a separate application command identifies where that ACL is used.
Read the headings as carefully as the commands underneath them:
text
interface GigabitEthernet0/0
ip address 192.0.2.1 255.255.255.0
no shutdown
!
interface GigabitEthernet0/1
shutdown
The address and no shutdown belong to GigabitEthernet0/0. The shutdown belongs to GigabitEthernet0/1. The exclamation mark is commonly used as a visual separator in displayed configurations; it is not a command that transfers the previous settings to the next interface.
A rushed reader may remember seeing both no shutdown and shutdown and assign the wrong state to an interface. Keeping track of context prevents that error.
Work line by line, using plain language. Translate only as much as the question requires, but do not skip a word that changes the result.
For an interface question, the important lines may be the interface identifier, address, mask, and administrative state. For an ACL question, they may include the action, protocol, address criteria, ports, sequence, and application direction. For a management question, distinguish the lines that define credentials from those that tell a console or virtual terminal line how to authenticate.
Pay attention to small words. In an ACL application, in and out are different. In a line configuration, login local is not the same kind of instruction as a command that merely creates a local user. In an interface block, shutdown and no shutdown have opposite administrative effects.
Separate three ideas:
- Configured: The command is present and specifies a setting.
- Intended effect: The setting is meant to influence device behavior in a particular way.
- Observed result: A fact demonstrated by operational output, a test, or other supplied evidence.
For example, no shutdown removes the administrative shutdown condition from an interface. It does not by itself prove that the physical link is up or that traffic is passing. An ACL applied inbound is intended to filter traffic entering that interface, but its actual effect on a particular packet depends on the packet and the ACL’s ordered…