All practice questions

203 questions

Question 81Question

A network administrator must configure a Cisco IOS extended IPv4 Access Control List (ACL) numbered 105 to enforce the following security policy for outbound traffic from an internal subnet:

1. Permit HTTPS traffic originating from subnet 192.168.10.0/24 destined to the database server at 10.0.0.50.
2. Deny all other TCP traffic originating from subnet 192.168.10.0/24 destined to the database server at 10.0.0.50.
3. Permit all remaining IP traffic originating from subnet 192.168.10.0/24 to any destination.

Arrange the ACL statements in the correct top-down sequential order required to successfully enforce this security policy.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequential order of statements from top to bottom is: 1) access-list 105 permit tcp 192.168.10.0 0.0.0.255 host 10.0.0.50 eq 443, 2) access-list 105 deny tcp 192.168.10.0 0.0.0.255 host 10.0.0.50, 3) access-list 105 permit ip 192.168.10.0 0.0.0.255 any, 4) (Implicit deny ip any any).
Cisco IPv4 access control lists execute line-by-line starting from the top entry (lowest sequence number) and stop evaluating as soon as a match occurs. Therefore, rules must strictly proceed from most specific (permitting HTTPS port 443 to the single host 10.0.0.50) to moderately specific (denying all other TCP to host 10.0.0.50), followed by broader subnet access (permitting all IP from 192.168.10.0/24), and finally concluding with the built-in implicit deny rule.

Step-by-Step Solution

1
Identify the most specific requirement
HTTPS traffic (TCP port 443) from 192.168.10.0/24 to host 10.0.0.50 is the most narrow requirement.
Cisco ACLs process sequentially top-down; specific permit rules must precede broader deny rules to prevent legitimate traffic from being matched early and dropped.
2
Place the specific host/port restriction next
Denying general TCP traffic from 192.168.10.0/24 to host 10.0.0.50 follows the HTTPS permit rule.
This blocks all other TCP application ports destined for 10.0.0.50 without affecting HTTPS traffic matched in step 1.
3
Place the general subnet permit rule
Permitting all IP traffic from 192.168.10.0/24 to any destination is placed after host-specific TCP rules.
This guarantees other destinations and protocols (such as ICMP or traffic to other servers) from subnet 192.168.10.0/24 are permitted.
4
Account for implicit ACL behavior
The implicit deny ip any any statement automatically resides at the end of the access list.
Cisco IOS automatically appends an invisible implicit deny to the end of every ACL, dropping any traffic that fails to match any explicit permit entries above.

Key Concept

Top-Down Sequential Processing and Specific-to-General Rule Ordering in Cisco IPv4 Extended ACLs
Question 82Question

A network administrator has configured HSRPv2 between two routers, R1 and R2. Router R1 is currently the Active router with a configured priority of 120, preemption enabled, and tracking on its primary WAN interface configured to decrement priority by 30 upon link failure. Router R2 is currently the Standby router with a configured priority of 105 and preemption enabled. When R1's tracked WAN interface fails, a precise sequence of operational events occurs across the routers and local LAN switches to complete the failover. What is the correct chronological sequence of these events from first to last?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of events is: (1) R1's tracked WAN interface fails and internal priority decrements to 90, (2) R1 advertises priority 90 in an HSRP Hello packet, (3) R2 observes R1's lower priority and transmits an HSRP Coup message due to preemption, (4) R2 assumes Active status and transmits a Gratuitous ARP (GARP) frame to update switch CAM tables, and (5) R1 processes R2's higher-priority election and transitions to Standby status.
The failover process begins when R1's tracked interface fails, immediately decreasing its local priority from 120 to 90. R1 advertises this new priority of 90 in its subsequent HSRP Hello multicast packet. R2 reads R1's Hello packet, notices its own priority of 105 is higher than R1's 90, and generates an HSRP Coup message because preemption is enabled. R2 then transitions to Active status and broadcasts a Gratuitous ARP (GARP) frame so adjacent switches update their MAC address tables for the virtual MAC address. Finally, R1 receives R2's Active message and transitions to Standby status.

Step-by-Step Solution

1
Identify the initial interface failure and local priority recalculation.
R1's priority is decremented by 30 (120 - 30 = 90).
HSRP interface tracking continuously monitors the specified interface status and modifies the router priority locally upon state change.
2
Determine how priority changes are communicated across the subnet.
R1 sends an HSRP Hello packet advertising priority 90.
HSRP state updates and priority shifts must be transmitted via multicast Hello messages to peer routers.
3
Evaluate peer router reaction and preemption mechanism.
R2 compares priorities (105 vs 90) and sends a Coup message.
Because preemption is enabled on R2, R2 immediately attempts to claim the Active role when it sees an Active router with lower priority.
4
Analyze Layer 2 forwarding convergence.
R2 shifts to Active state and sends a Gratuitous ARP (GARP).
Layer 2 switches must learn that the virtual MAC address is now reachable via R2's switch port, which is accomplished via GARP frame broadcast.
5
Verify final state transition of the original Active router.
R1 transitions to Standby state.
R1 recognizes R2 as a valid Active router with higher priority (105 > 90) and completes demotion.

Key Concept

HSRP Interface Tracking, Preemption Coup Mechanics, and GARP Convergence
Question 83Question

An engineer is analyzing legacy IEEE 802.1D Spanning Tree Protocol (STP) behavior on a Cisco switch interface that is configured without PortFast. Place the following STP port states in chronological order, starting from link initialization and ending when the interface reaches active user data transmission.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological order of classic IEEE 802.1D STP port states during port initialization is Blocking, Listening, Learning, and Forwarding.
Standard IEEE 802.1D STP port state convergence transitions sequentially through Blocking (loop prevention / BPDU listening) -> Listening (BPDU transmission/reception, topology role determination) -> Learning (MAC address table population without frame forwarding) -> Forwarding (full data frame forwarding and continuous learning).

Step-by-Step Solution

1
Identify the initial state assigned to prevent immediate switching loops upon link UP.
The interface starts in the Blocking state where data frames are dropped and MAC addresses are not learned, but incoming BPDUs are evaluated.
802.1D STP defaults to a loop-prevention state to listen for existing network bridge topology.
2
Determine the state where active STP participation and BPDU transmission begin.
The port transitions to the Listening state for 15 seconds (Forward Delay), sending and receiving BPDUs to elect the root bridge and establish port roles.
In Listening, the switch establishes topology structure without yet accepting host MAC entries.
3
Identify the state designed to populate layer 2 tables prior to passing payload traffic.
The port moves to the Learning state for an additional 15 seconds (Forward Delay), reading source MAC addresses from frame headers without forwarding frames.
Pre-building the MAC address table minimizes unicast flooding once frame forwarding is enabled.
4
Identify the ultimate operational state achieved upon timer completion.
The port enters the Forwarding state, enabling full bidirectional user traffic forwarding alongside ongoing BPDU processing and MAC learning.
The port has passed all convergence checks over the 30-second convergence window.

Key Concept

Classic IEEE 802.1D STP Port State Transition Sequence
Question 84Question

A switch port running standard IEEE 802.1D Spanning Tree Protocol (STP) detects an active connection to an end device. Arrange the STP port states in the correct sequential order from initial physical link detection to fully active data frame forwarding.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequential progression of 802.1D STP port states is: Blocking State, Listening State, Learning State, and Forwarding State.
Under standard IEEE 802.1D, a newly connected port progresses through four distinct states to ensure network loops do not form: Blocking (drops data, listens for BPDUs), Listening (discards data, sends/receives BPDUs, no MAC learning), Learning (discards data, learns MAC addresses), and finally Forwarding (forwards data frames normally).

Step-by-Step Solution

1
Identify the initial state upon link up.
The port starts in the Blocking state to avoid creating temporary switching loops while BPDU information is evaluated.
802.1D requires all non-designated/non-root ports or newly activated ports to block user traffic initially.
2
Determine the transition following BPDU analysis.
The port transitions to the Listening state for the duration of the Forward Delay timer (15 seconds).
During Listening, the port sends and receives BPDUs to elect root bridges and assign port roles without forwarding traffic or learning MAC addresses.
3
Determine the step after topology role determination.
The port enters the Learning state for a second Forward Delay timer interval (15 seconds).
Learning allows the switch to build its MAC address table from source MACs in incoming frames to minimize flooding when forwarding begins.
4
Identify the final operational state.
The port reaches the Forwarding state.
Once the learning phase expires without topology conflicts, the interface fully forwards user data frames and processes BPDUs.

Key Concept

802.1D Spanning Tree Protocol Port State Transitions
Estimated Time:45s
Question 85Question

A network administrator needs to configure a floating static default route on a Cisco IOS router to serve as a backup to an existing OSPF-learned default route (Administrative Distance of 110). Place the operational steps in the correct sequential order to configure, validate normal operation, and verify failover behavior of this backup route.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence begins by analyzing the primary protocol AD (110), navigating to global configuration mode, defining the floating static default route with a higher AD value (120), verifying that the route remains inactive in the routing table during normal operations, and finally testing link failover to confirm RIB insertion.
The workflow follows standard Cisco IOS network administration practices: planning parameters (AD selection), configuration entry, syntax application, baseline verification (confirming inactivity while primary is up), and failover validation (confirming activation when primary drops).

Step-by-Step Solution

1
Determine the primary route's Administrative Distance.
Identified OSPF AD as 110, requiring a floating static route AD > 110 (e.g., 120).
Floating static routes rely on a higher AD than the active routing source so they remain inactive until the primary route fails.
2
Access configuration mode.
Router prompt changes to `Router(config)#`.
Cisco IOS static route creation requires global configuration access.
3
Apply the static route configuration.
Configured `ip route 0.0.0.0 0.0.0.0 203.0.113.2 120`.
Defines a default route (`0.0.0.0 0.0.0.0`) pointing to next-hop `203.0.113.2` with an AD argument of `120`.
4
Verify initial routing table state.
Confirmed OSPF route is active in RIB and static route is absent.
Ensures the floating route does not preempt the primary dynamic path while the primary path is healthy.
5
Test path failover under fault conditions.
Static route `S* 0.0.0.0/0 [120/0] via 203.0.113.2` appears in `show ip route` output upon primary interface shutdown.
Validates proper failover functionality when the primary route is removed from the routing table.

Key Concept

Floating Static Route Lifecycle and Failover Validation
Estimated Time:2m 0s
Question 86Question

A network engineer connects two Cisco Catalyst switches. SwitchA interface GigabitEthernet0/1 is configured with 'switchport mode dynamic desirable', and SwitchB interface GigabitEthernet0/1 is configured with 'switchport mode dynamic auto'. Both switches use default native VLAN 1 configurations. Place the following operational events in the correct sequential order from the initiation of link negotiation to the transmission of native VLAN traffic.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with SwitchA sending active DTP frames, followed by SwitchB acknowledging the proposal from dynamic auto mode, both interfaces transitioning to operational 802.1Q trunking, SwitchA receiving ingress VLAN 1 traffic, and SwitchA forwarding that native VLAN traffic untagged across the trunk.
Dynamic desirable ports actively initiate DTP negotiation, causing dynamic auto ports to respond and agree. Once operational, data traffic matching the default native VLAN (VLAN 1) is forwarded across the 802.1Q trunk untagged.

Step-by-Step Solution

1
Initiate DTP Proposal
SwitchA sends DTP frames via Gi0/1.
'switchport mode dynamic desirable' actively initiates negotiation with the neighbor.
2
Respond to Negotiation
SwitchB receives DTP and responds positively.
'switchport mode dynamic auto' will not originate DTP proposals but willingly converts to a trunk if requested by a neighbor.
3
Establish Operational Trunk
Both Gi0/1 interfaces enter the trunking operational state using 802.1Q encapsulation.
A desirable-to-auto dynamic DTP pairing successfully negotiates a trunk.
4
Process Ingress Frame
SwitchA accepts an ingress frame belonging to VLAN 1 (native VLAN).
Data plane forwarding occurs after control plane negotiation is established.
5
Forward Across Trunk
SwitchA sends the frame across Gi0/1 untagged.
By default under 802.1Q, native VLAN traffic is transmitted without adding a 4-byte VLAN tag.

Key Concept

802.1Q Trunking DTP Negotiation Sequence and Native VLAN Tagging Mechanics
Question 87Question

A Cisco Catalyst switch with an initially empty MAC address table receives an Ethernet frame on ingress port FastEthernet0/1. The frame originates from Host A (MAC address 00A1.1111.AAAA) and is addressed to Host B (MAC address 00B2.2222.BBBB) on VLAN 10. In what chronological sequence does the Layer 2 switch execute internal processing steps from frame ingress to frame egress?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological sequence is: 1) Parse ingress frame for MAC addresses, 2) Learn source MAC and map to ingress port, 3) Lookup destination MAC in table, 4) Identify destination as unknown unicast, 5) Flood frame out all VLAN ports except ingress port.
When a Layer 2 switch receives an Ethernet frame on an ingress interface, it processes the frame in a specific order: first, it parses the L2 header; second, it reads the source MAC address and updates/populates its MAC address table (CAM table); third, it looks up the destination MAC address; fourth, if the destination is missing from the CAM table, it classifies it as an unknown unicast; fifth, it floods the frame out all active ports assigned to that VLAN except the receiving port.

Step-by-Step Solution

1
Receive and ingress-parse frame
Identified Source MAC: 00A1.1111.AAAA, Destination MAC: 00B2.2222.BBBB, Ingress Port: Fa0/1, VLAN: 10.
The switch ASIC must inspect the Layer 2 Ethernet header preamble and fields first.
2
Source MAC Learning
MAC table entry updated with [VLAN 10 | 00A1.1111.AAAA | Dynamic | Fa0/1].
Layer 2 switches always learn source MAC addresses before determining egress forwarding.
3
Destination MAC Lookup
Query for 00B2.2222.BBBB yields no matching entry in VLAN 10 CAM table.
Switch determines whether to perform known unicast forwarding or unknown unicast flooding.
4
Classification of Traffic
Traffic categorized as unknown unicast.
A table miss forces the switch to default to broadcast-like flooding behavior within Layer 2 bounds.
5
Egress Frame Flooding
Frame replicated to all operational VLAN 10 ports, suppressing Fa0/1.
Split-horizon rule prevents sending a frame back out the interface from which it was received.

Key Concept

Layer 2 MAC Address Table Operation and Ingress/Egress Forwarding Pipeline
Question 88Question

Place the operational and negotiation events in the exact chronological sequence required for two Cisco Catalyst switches to establish a functional IEEE 802.1Q trunk link using Dynamic Trunking Protocol (DTP) following CLI configuration.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with the CLI mode configuration on both switches, followed by Switch-A actively sending DTP request frames, Switch-B processing and agreeing to the trunking request, the operational transition of both interfaces to an active 802.1Q trunk, and finally the active forwarding and 4-byte tagging of frame traffic.
The correct order follows the standard Cisco IOS control and data plane progression: Configuration commands activate DTP on the interface -> The dynamic desirable interface actively sends DTP negotiation frames -> The dynamic auto interface receives the frame and agrees to form a trunk -> Both ports transition operationally to trunking status -> IEEE 802.1Q 4-byte frame tagging is applied to active traffic.

Step-by-Step Solution

1
Identify administrative configuration stage
Switch-A is set to dynamic desirable and Switch-B is set to dynamic auto.
Administrative commands must be applied to the interfaces before any control-plane negotiation protocols can generate messages.
2
Determine active protocol packet generation
Switch-A sends DTP frames actively across the link.
Dynamic desirable ports actively initiate negotiation by sending DTP frames, whereas dynamic auto ports only listen until prompted.
3
Analyze protocol response and parameter matching
Switch-B receives the DTP request and responds affirmatively.
Dynamic auto mode transitions to a trunk state upon receiving an active negotiation request from a desirable or trunking neighbor.
4
Establish operational port state
Both ports transition to operational status trunking with 802.1Q encapsulation.
Once parameters are agreed upon, hardware state registers update the port state from access to trunking.
5
Apply data-plane framing rules
Ethernet frames traversing the link receive a 4-byte 802.1Q VLAN header, except for frames belonging to the native VLAN.
Data forwarding and 802.1Q frame encapsulation occur only after trunk negotiation and port state activation are fully finalized.

Key Concept

802.1Q Trunking & DTP Negotiation Sequence
Question 89Question

A network administrator needs to create a new VLAN named 'VOICE' with ID 20 on a fresh Cisco Catalyst switch and manually assign interface FastEthernet 0/1 as an active access port belonging to this VLAN. Place the Cisco IOS CLI commands in the exact correct sequence required to perform this complete configuration from privileged EXEC mode.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational order begins by entering global configuration mode (configure terminal), creating the VLAN (vlan 20), naming the VLAN (name VOICE), entering interface mode (interface fastethernet 0/1), explicitly setting the link to access mode (switchport mode access), and finally binding the port to the VLAN (switchport access vlan 20).
Cisco IOS configuration follows a strict modal hierarchy. The administrator must first enter global configuration mode (`configure terminal`), instantiate VLAN 20 (`vlan 20`), name it while in `config-vlan` sub-mode (`name VOICE`), navigate to the desired interface (`interface fastethernet 0/1`), set the operational mode (`switchport mode access`), and assign the access VLAN (`switchport access vlan 20`).

Step-by-Step Solution

1
Enter Global Configuration mode
Switch prompt changes to Switch(config)#
CLI context must be in global configuration mode to create network-wide objects such as VLANs or navigate to specific interfaces.
2
Create VLAN 20
Switch prompt changes to Switch(config-vlan)#
Executing 'vlan 20' creates the L2 broadcast domain in the VLAN database and shifts context to VLAN configuration mode.
3
Assign the VLAN Name
VLAN 20 is named 'VOICE'
Sub-commands like 'name' must be issued while in Config-VLAN mode directly following VLAN creation.
4
Navigate to target switchport interface
Switch prompt changes to Switch(config-if)#
Interface commands require entering interface configuration mode for FastEthernet 0/1.
5
Set port operational mode to access
DTP dynamic negotiation is disabled or overridden to static access mode
Best security and operational practice requires explicitly defining 'switchport mode access' before or alongside VLAN assignment.
6
Assign interface to VLAN 20
Interface FastEthernet 0/1 actively forwards untagged traffic for VLAN 20
Executing 'switchport access vlan 20' under interface configuration mode completes the access port assignment.

Key Concept

Cisco IOS CLI Configuration Hierarchy for VLAN Creation and Access Port Binding
Question 90Question

When a Layer 2 Ethernet switch receives an ingress frame, it processes the header information in a specific sequential order. Place the steps taken by the switch into the correct chronological order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of switch operation is: 1) The frame arrives on an ingress port, 2) The switch learns or updates the source MAC address and port mapping in the MAC address table, 3) The switch performs a table lookup for the destination MAC address, and 4) The switch forwards or floods the frame out the appropriate port(s).
A Layer 2 Ethernet switch always follows a standard pipeline: frame reception on ingress, source MAC learning and table updating, destination MAC address lookup, and finally executing unicast forwarding or VLAN flooding.

Step-by-Step Solution

1
Receive ingress frame
The physical frame is received on an active Layer 2 switch port.
Initial reception triggers Layer 2 inspection.
2
Source MAC learning
The source MAC address is mapped to the ingress port in the MAC address table.
Switches always learn source MAC locations before executing forwarding logic.
3
Destination MAC lookup
The MAC address table is searched for the destination MAC address.
Determines whether the egress interface is known or unknown.
4
Frame forwarding decision
The frame is unicast forwarded to a single port or flooded across the VLAN (excluding ingress port).
Completes the Layer 2 delivery cycle.

Key Concept

Layer 2 Frame Ingress Processing and MAC Table Pipeline
Question 91Question

A network administrator is migrating a pair of trunk links connecting two distribution switches to a routed Layer 3 EtherChannel using IEEE 802.3ad LACP. Interfaces GigabitEthernet1/0/1 and GigabitEthernet1/0/2 need to be bundled into Port-channel 5 with IPv4 address 10.0.5.1/3010.0.5.1/30 assigned to the logical interface. In what operational sequence must these CLI configuration steps be executed on the switch to successfully create this Layer 3 EtherChannel?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence begins by selecting physical member interfaces via interface range mode, converting them to Layer 3 routed ports using `no switchport`, binding them to LACP bundle 5 with `channel-group 5 mode active`, entering `interface Port-channel 5` configuration mode, and finally assigning IPv4 address 10.0.5.1/3010.0.5.1/30 directly to the logical port-channel.
To build an operational Layer 3 LACP EtherChannel, physical member links must first be selected and converted into routed interfaces (`no switchport`). Adding these converted interfaces to a channel group with `mode active` automatically creates a Layer 3 logical port-channel and starts LACP negotiation. Finally, configuration transitions to `interface Port-channel 5`, where the IP address is applied to the logical bundle.

Step-by-Step Solution

1
Execute `interface range GigabitEthernet1/0/1 - 2`.
Enters range interface configuration mode for both physical member interfaces.
Configuration commands must be applied simultaneously to member interfaces to maintain identical operational states.
2
Execute `no switchport` on the physical interface range.
Converts physical member interfaces from Layer 2 switchports into Layer 3 routed ports.
Member interfaces must be routed ports prior to group assignment so that Cisco IOS instantiates a Layer 3 Port-channel interface.
3
Execute `channel-group 5 mode active`.
Instantiates Port-channel 5 and enables active IEEE 802.3ad LACP negotiation on the physical interfaces.
Active mode ensures the switch actively sends LACP Link Aggregation Control Protocol Data Units (LACPDUs) to negotiate EtherChannel formation.
4
Execute `interface Port-channel 5`.
Enters interface configuration sub-mode for logical interface Port-channel 5.
Layer 3 protocol configuration and IP routing parameters belong to the logical bundle interface.
5
Execute `ip address 10.0.5.1 255.255.255.252` on the port-channel interface.
Configures the IP address and subnet mask on the logical EtherChannel bundle.
In Layer 3 EtherChannels, packets are routed to the port-channel interface, which then distributes traffic across physical member links using the load-balancing hash.

Key Concept

Layer 3 EtherChannel LACP Configuration Sequence
Question 92Question

When a non-PortFast interface on a Cisco switch using classic IEEE 802.1D Spanning Tree Protocol (STP) comes up, it undergoes a specific sequence of port states to prevent Layer 2 loops before it begins processing user traffic. Place the following STP port states in the correct chronological order from link initialization to full data forwarding.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence of classic 802.1D STP port states is Blocking State, followed by Listening State, then Learning State, and finally Forwarding State.
Under standard IEEE 802.1D Spanning Tree Protocol operational rules, an interface transitions sequentially from Blocking (preventing loops) to Listening (participating in BPDU role election), then to Learning (building MAC table entries), and finally reaches Forwarding (processing and forwarding user traffic).

Step-by-Step Solution

1
Identify the initial port state upon link initialization.
The switch interface starts in the Blocking state where it drops user frames and does not learn MAC addresses to prevent loops.
STP defaults to a loop-preventative state whenever a link transitions to up.
2
Determine the state focused on root bridge election and port role determination.
The interface moves to the Listening state, where BPDUs are processed and sent, but user data is still dropped and MAC learning is disabled.
The switch must determine topology roles (Root Port, Designated Port, or Alternate Port) before modifying table structures.
3
Determine the intermediate state focused on MAC table population.
After the first 15-second Forward Delay timer, the interface enters the Learning state, where it populates the MAC table from incoming frame headers but still drops user payload data.
Populating MAC addresses in advance prevents massive unicast flooding when the port starts forwarding.
4
Identify the final operational state allowing full traffic transmission.
After the second 15-second Forward Delay timer, the interface transitions to the Forwarding state.
The port is now confirmed loop-free and fully prepared to forward data frames.

Key Concept

IEEE 802.1D STP Port State Convergence Sequence
Estimated Time:45s
Question 93Question

A network engineer is configuring a routed (Layer 3) EtherChannel bundle (Port-channel 12) on a Cisco Catalyst switch using Link Aggregation Control Protocol (LACP). The bundle must aggregate physical interfaces GigabitEthernet1/0/1 and GigabitEthernet1/0/2, actively negotiate LACP trunking, and host the IPv4 default gateway subnet interface with IP address 192.168.100.1/30. Place the Cisco IOS configuration command steps in the correct sequential order from first to last to complete this configuration cleanly.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of commands is: 1) interface range GigabitEthernet1/0/1 - 2, 2) no switchport, 3) channel-group 12 mode active, 4) interface Port-channel 12, 5) ip address 192.168.100.1 255.255.255.252.
To create a routed (Layer 3) EtherChannel using LACP, the physical interfaces must first be selected ('interface range GigabitEthernet1/0/1 - 2') and converted to Layer 3 routed ports ('no switchport'). Next, the LACP dynamic bundle is formed using 'channel-group 12 mode active'. Afterwards, the administrator switches to the logical bundle interface context ('interface Port-channel 12') to assign the IPv4 address ('ip address 192.168.100.1 255.255.255.252').

Step-by-Step Solution

1
Select the target physical member interfaces
Enters interface range configuration mode for GigabitEthernet1/0/1 and 1/0/2.
Configuration changes must apply to both member links simultaneously.
2
Remove Layer 2 switching capabilities
Converts physical member interfaces to Layer 3 routed ports.
Issuing 'no switchport' on member interfaces prior to bundling ensures the created port-channel automatically inherits routed Layer 3 operational mode.
3
Create and bind member interfaces to the channel-group
Adds physical member interfaces to Port-channel 12 using LACP active mode.
The 'mode active' keyword specifies active LACP packet transmission to initiate bundle formation.
4
Navigate to the logical bundle interface
Enters configuration mode for interface Port-channel 12.
Logical layer configurations (such as IP addressing) must be applied directly to the port-channel interface.
5
Configure IP address on the port-channel
Assigns IP address 192.168.100.1/30 to Port-channel 12.
Layer 3 EtherChannels hold IP configuration on the logical interface, allowing traffic routing over the aggregated links.

Key Concept

Layer 3 EtherChannel LACP Configuration Sequence
Question 94Question

A network administrator needs to establish a routed (Layer 3) EtherChannel between two Cisco switches using LACP active mode across physical interfaces GigabitEthernet0/1 and GigabitEthernet0/2. In what correct chronological order should the administrator execute the Cisco IOS CLI commands to configure this Layer 3 EtherChannel from global configuration mode?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct configuration order requires selecting physical member interfaces first, converting them to Layer 3 routed ports using 'no switchport', assigning them to EtherChannel group 10 with LACP active mode, entering Port-channel 10 configuration mode, and finally configuring the IPv4 address on the logical Port-channel interface.
The correct order follows Cisco standard CLI logic for Layer 3 EtherChannel configuration: select physical member interfaces ('interface range GigabitEthernet0/1 - 2'), convert them to routed ports ('no switchport'), form the LACP EtherChannel bundle ('channel-group 10 mode active'), navigate into the logical interface ('interface Port-channel 10'), and assign the IP address ('ip address 10.10.10.1 255.255.255.252').

Step-by-Step Solution

1
Select physical member interfaces
Entered interface range configuration mode for GigabitEthernet0/1 - 2.
CLI commands must be applied to physical interfaces first before grouping them into a bundle.
2
Execute 'no switchport' on physical member interfaces
Member interfaces are converted from Layer 2 switch ports to Layer 3 routed ports.
A Layer 3 EtherChannel requires member interfaces to be configured as routed interfaces before establishing the channel group.
3
Execute 'channel-group 10 mode active'
Physical interfaces are added to Port-channel 10 under LACP active negotiation mode.
The channel-group command dynamically creates the Port-channel interface with LACP protocol.
4
Enter logical interface mode via 'interface Port-channel 10'
Router moves into logical interface configuration prompt.
Layer 3 configurations (IP addressing) must be defined on the logical port-channel interface itself.
5
Apply IP address parameters on Port-channel 10
IP address 10.10.10.1/30 is bound to Port-channel 10.
Traffic routing across Layer 3 EtherChannel uses the logical interface IP address.

Key Concept

Layer 3 EtherChannel CLI configuration workflow requires setting 'no switchport' on physical member interfaces prior to creating the channel-group and applying IP addressing on the logical Port-channel interface.
Question 95Question

A network administrator needs to create VLAN 20 on a Cisco Catalyst switch and configure interface GigabitEthernet0/1 as an access port belonging to VLAN 20. Arrange the CLI commands in the correct sequence, starting from privileged EXEC mode.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct CLI configuration sequence begins by entering global configuration mode with 'configure terminal', creating the VLAN with 'vlan 20', navigating to the target interface with 'interface GigabitEthernet0/1', defining static access mode via 'switchport mode access', and finally binding the interface to the VLAN using 'switchport access vlan 20'.
The configuration progression follows Cisco IOS hierarchical logic: enter global configuration mode ('configure terminal'), create the VLAN in the database ('vlan 20'), transition to the specific interface context ('interface GigabitEthernet0/1'), force the link to operate as an access link ('switchport mode access'), and assign it to the desired broadcast domain ('switchport access vlan 20').

Step-by-Step Solution

1
Enter global configuration mode
Switch prompt changes to Switch(config)#
Global configuration mode is required before creating VLANs or specifying interface configurations.
2
Create VLAN 20
VLAN 20 is added to the database and prompt changes to Switch(config-vlan)#
Creating the VLAN ensures the broadcast domain exists prior to assigning switch ports to it.
3
Enter interface configuration mode for GigabitEthernet0/1
Switch prompt changes to Switch(config-if)#
Interface parameters must be configured within the specific interface configuration context.
4
Configure static access mode on the interface
Disables DTP trunk negotiation and sets interface to access mode
Explicitly declaring access mode ensures the port will not form a trunk link.
5
Assign the interface to VLAN 20
Interface GigabitEthernet0/1 is placed into VLAN 20
Associates untagged layer 2 traffic on GigabitEthernet0/1 with broadcast domain VLAN 20.

Key Concept

Cisco IOS CLI hierarchy for VLAN creation and switchport access assignment
Question 96Question

A network administrator is configuring a secure interswitch 802.1Q trunk link on Cisco switch interface GigabitEthernet0/1. The task requires statically enabling trunking, stopping DTP frame negotiation, reassigning the native VLAN to VLAN 99, and removing VLAN 1 from the trunk's allowed list. Place the CLI commands and actions in the correct logical configuration order.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins by entering interface mode, enforcing static trunking, disabling DTP negotiation, setting native VLAN 99, and finally removing VLAN 1 from the allowed VLAN list.
Configuring a static 802.1Q trunk on a Cisco Catalyst switch requires stepping into interface configuration mode first. Setting switchport mode trunk must precede switchport nonegotiate because DTP disabling is rejected by Cisco IOS on dynamic interfaces. Configuring native VLAN 99 and pruning VLAN 1 completes the trunk hardening workflow.

Step-by-Step Solution

1
Execute interface GigabitEthernet0/1 in global configuration mode.
Enters interface configuration context.
Port configuration parameters must be applied within the specific interface context.
2
Execute switchport mode trunk.
Sets administrative state to unconditional trunking.
Cisco IOS requires an explicit static mode (trunk or access) prior to issuing switchport nonegotiate.
3
Execute switchport nonegotiate.
Stops transmission of DTP frames.
Prevents unauthorized trunk negotiation while ensuring the link remains statically operational.
4
Execute switchport trunk native vlan 99.
Configures VLAN 99 as the native untagged VLAN.
Overrides default VLAN 1 untagged frame behavior to prevent security issues such as VLAN hopping.
5
Execute switchport trunk allowed vlan remove 1.
Removes VLAN 1 from the trunk forwarding topology.
Ensures default management VLAN traffic does not traverse the interswitch link.

Key Concept

802.1Q Trunk CLI Configuration Order and DTP Prerequisites
Question 97Question

A network administrator needs to configure a routed (Layer 3) EtherChannel using LACP dynamic negotiation across physical interfaces GigabitEthernet0/1 and GigabitEthernet0/2 on a Cisco switch. Place the configuration steps in the correct sequential order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of steps to configure a Layer 3 EtherChannel using LACP is: 1) Enter interface range configuration mode for the physical member interfaces; 2) Execute the 'no switchport' command on the physical member interfaces; 3) Execute the 'channel-group 1 mode active' command on the physical member interfaces; 4) Enter logical interface Port-channel 1 configuration mode and assign the IPv4 address and subnet mask.
The proper administrative workflow begins by selecting physical member links GigabitEthernet0/1 and GigabitEthernet0/2. Disabling Layer 2 switching on these interfaces via 'no switchport' establishes them as routed interfaces. Binding them to channel-group 1 using LACP active mode creates the logical port-channel and begins dynamic trunk negotiation. Finally, navigating into interface Port-channel 1 mode permits configuration of the routed IP address.

Step-by-Step Solution

1
Select physical member links
Switch prompt changes to (config-if-range).
Allows configuration changes to be applied simultaneously across both physical interfaces.
2
Disable Layer 2 switchport mode on physical interfaces
'no switchport' command converts physical member links into routed ports.
Layer 3 EtherChannels require member interfaces to operate as routed ports rather than Layer 2 switchports.
3
Enable LACP active mode on physical interfaces
'channel-group 1 mode active' dynamically creates logical interface Port-channel 1.
Active mode ensures the switch actively initiates LACP negotiation across the member links.
4
Assign IP address to the logical port-channel
IPv4 address and subnet mask are configured on interface Port-channel 1.
For Layer 3 EtherChannels, IP routing occurs on the aggregate logical interface.

Key Concept

Layer 3 EtherChannel LACP Configuration Sequence
Estimated Time:1m 0s
Question 98Question

A network administrator enables an access switch interface connected to a workstation running standard IEEE 802.1D Spanning Tree Protocol (STP) without PortFast configured. Arrange the standard operational port states in the exact chronological sequence through which the interface transitions from initial link activation to full user data frame transmission.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological sequence for standard IEEE 802.1D STP port state initialization is: Blocking state, Listening state, Learning state, and finally Forwarding state.
Under standard IEEE 802.1D Spanning Tree Protocol operational behavior, an interface enabling without PortFast goes through a strict multi-step sequence to prevent Layer 2 loops. It begins in the Blocking state (discarding data, listening to BPDUs), transitions to Listening (exchanging BPDUs, electing roles for 15 seconds), advances to Learning (exchanging BPDUs and building MAC address table for 15 seconds), and culminates in the Forwarding state (full data frame transmission and MAC learning).

Step-by-Step Solution

1
Identify the initial state upon link bring-up.
The port initializes in the Blocking state where it drops frames and only listens to BPDUs to avoid loops.
802.1D forces ports to start in Blocking so they can detect BPDUs from neighbor switches before taking any active roles.
2
Determine the second state following election participation.
The port transitions to the Listening state for 15 seconds (Forward Delay).
In Listening state, the switch sends and receives BPDUs to clear invalid topology entries and elect Root/Designated ports without populating MAC tables or forwarding data.
3
Identify the state where MAC address learning begins.
The port transitions to the Learning state for another 15 seconds (Forward Delay).
In Learning state, the port learns source MAC addresses to pre-populate the MAC table, reducing unicast flooding prior to data forwarding.
4
Determine the final operational state.
The port transitions to the Forwarding state.
Having safely passed both Forward Delay periods without loop creation, the port now processes and forwards data traffic normally.

Key Concept

IEEE 802.1D Spanning Tree Protocol Port State Transitions
Estimated Time:2m 0s
Question 99Question

A network administrator needs to create VLAN 100 named VOICE on a Cisco Catalyst switch and assign interface GigabitEthernet0/2 as a static access port in VLAN 100. Starting from Privileged EXEC mode (Switch#Switch\#), in what sequence must the Cisco IOS CLI commands be executed?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct command sequence begins with entering global configuration mode (configure terminal), creating VLAN 100 (vlan 100), naming the VLAN (name VOICE), navigating to interface GigabitEthernet0/2 (interface gigabitethernet0/2), configuring access mode (switchport mode access), and assigning the port to VLAN 100 (switchport access vlan 100).
The correct order follows Cisco IOS configuration hierarchy. The sequence starts in Privileged EXEC mode with 'configure terminal' to enter Global Configuration mode. Next, 'vlan 100' creates the VLAN and switches to VLAN Configuration mode, where 'name VOICE' is applied. After returning to global configuration scope, 'interface gigabitethernet0/2' opens Interface Configuration mode, where 'switchport mode access' enforces static access behavior and 'switchport access vlan 100' places the port into VLAN 100.

Step-by-Step Solution

1
Transition from Privileged EXEC mode to Global Configuration mode.
The CLI prompt changes to Switch(config)#.
Global configuration mode is required to configure system-wide parameters and enter specific subconfiguration modes.
2
Create VLAN 100 and enter VLAN Configuration submode.
The CLI prompt changes to Switch(config-vlan)#.
VLAN 100 must be instantiated before configuring its parameters or assigning ports.
3
Assign the name VOICE to VLAN 100.
VLAN 100 is assigned the descriptive name VOICE.
The 'name' command is specific to VLAN configuration mode.
4
Navigate to Interface Configuration mode for GigabitEthernet0/2.
The CLI prompt changes to Switch(config-if)#.
Targeting an interface requires switching from global configuration to interface configuration mode.
5
Configure GigabitEthernet0/2 as a static access port.
Trunk negotiation is disabled, establishing static access operation.
Executing 'switchport mode access' explicitly defines the interface operational mode.
6
Assign GigabitEthernet0/2 to VLAN 100.
Untagged frames entering GigabitEthernet0/2 are assigned to broadcast domain VLAN 100.
Executing 'switchport access vlan 100' maps the access port to VLAN 100.

Key Concept

Cisco IOS hierarchical context navigation and sequential syntax execution for VLAN creation and static access port configuration.
Question 100Question

A network engineer must manually configure a routed (Layer 3) Link Aggregation Control Protocol (LACP) EtherChannel bundle on a Cisco Catalyst switch using physical member interfaces GigabitEthernet1/0/1 and GigabitEthernet1/0/2. The EtherChannel must use Port-channel 20 and be configured with IP address 10.20.20.1/30. Arrange the CLI configuration commands into the correct execution sequence from top to bottom.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct CLI sequence is: 1) interface range GigabitEthernet1/0/1 - 2, 2) no switchport, 3) channel-group 20 mode active, 4) interface Port-channel 20, and 5) ip address 10.20.20.1 255.255.255.252.
To successfully deploy a routed (Layer 3) LACP EtherChannel, physical interfaces must first be selected, configured with 'no switchport' to disable Layer 2 switching, and bound to a channel group using an active LACP mode. Afterwards, the administrator enters the logical port-channel interface context to configure the IP address parameters.

Step-by-Step Solution

1
Select physical member interfaces
Enters interface range configuration mode for GigabitEthernet1/0/1 and GigabitEthernet1/0/2.
Configuration must start at physical interfaces to prepare them before bundling.
2
Convert physical interfaces to Layer 3 routed interfaces
Disables Layer 2 switching capabilities on physical member ports.
Physical member ports of a routed EtherChannel must have 'no switchport' applied before participating in a Layer 3 channel group.
3
Assign interfaces to an active LACP channel group
Creates Port-channel 20 automatically and sets LACP mode to active.
The 'mode active' parameter enables LACP dynamic negotiation on the physical member interfaces.
4
Select logical Port-channel interface
Enters interface configuration mode for Port-channel 20.
Network configuration, including IP addressing, must be applied directly to the logical port-channel container.
5
Configure IP address on Port-channel interface
Assigns IPv4 address 10.20.20.1/30 to Port-channel 20.
Layer 3 EtherChannels hold IP addressing at the port-channel level rather than individual member links.

Key Concept

Layer 3 EtherChannel (LACP) Configuration Sequence
PreviousPage 5 / 11Next
All practice questions — Cisco CCNA | Examkin