800-150 · Question #74
Drag and Drop Question Drag and drop the TFTP statements from the left onto the corresponding categories on the right. Answer:
The correct answer is component to configure; interface type; slot; port. TFTP Interface Configuration - Drag-and-Drop Explanation This question tests knowledge of the Cisco IOS interface naming/configuration syntax, which follows a strict hierarchical order. The correct arrangement reflects the command structure used when configuring a network…
Question
Drag and Drop Question Drag and drop the TFTP statements from the left onto the corresponding categories on the right. Answer:
Exhibit
Answer Area
Drag items
Correct arrangement
- component to configure
- interface type
- slot
- port
Explanation
TFTP Interface Configuration - Drag-and-Drop Explanation
This question tests knowledge of the Cisco IOS interface naming/configuration syntax, which follows a strict hierarchical order. The correct arrangement reflects the command structure used when configuring a network interface (often necessary when setting up TFTP server reachability).
The Correct Order and Why
The command structure being modeled:
interface GigabitEthernet 0 / 1
[1] [2] [3] [4]
1. Component to configure - interface
This is the IOS command keyword that opens the configuration context. You must declare what you are configuring before anything else. Without this, the remaining parameters have no context.
2. Interface type - e.g., GigabitEthernet, FastEthernet, Serial
After declaring the component, you specify which kind of interface. The type must come before the physical location because the slot/port numbering can differ by type.
3. Slot - e.g., 0
The physical slot (or module) number on the chassis. Slot comes before port because it represents the higher-level physical location - you identify the card/module first, then the specific port on it.
4. Port - e.g., 1
The specific port within the slot. This is always last because it is the most granular identifier in the hierarchy.
Common Mistakes
| Mistake | Why It's Wrong |
|---|---|
| Placing port before slot | IOS notation is always slot/port, never reversed |
| Placing interface type first | The interface keyword (component) must precede the type |
| Confusing slot with port on single-module devices | On simple devices (e.g., Fa0/1), "0" is slot, "1" is port - they still follow the same order |
The hierarchy is always: what → what kind → where (coarse) → where (fine).
Topics
Community Discussion
No community discussion yet for this question.
