How should I use these Device Management practice questions?

Read each scenario carefully and choose your answer before revealing the explanation. Then check why your choice was right or wrong. Repeat until the reasoning feels automatic.

Can I practise just Device Management questions in a focused session?

Yes — use the session launcher on this page to start a 10-, 20-, 30- or 50-question session drawn entirely from the Device Management domain.

300-410 · topic practice

Device Management practice questions

Practise Cisco CCNP ENARSI 300-410 Device Management practice questions — original exam-style scenarios with answer choices, explanations, and analysis of common mistakes.

Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.

Reviewed byJohnson Ajibi· MSc IT Security

20 questionsDomain: Device Management

Practice 10 questions Browse domain →

What the exam tests

What to know about Device Management

Device Management questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Watch out for

Common Device Management exam traps

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Practice set

Device Management questions

20 questions · select your answer, then reveal the explanation

Question 1mediummultiple choice

Read the full network assurance explanation →

A network engineer is troubleshooting a router that is not sending SNMP traps to the NMS server at 10.1.1.100. The SNMP configuration includes 'snmp-server enable traps' and 'snmp-server host 10.1.1.100 version 2c public'. The engineer can ping the NMS server from the router, and 'show snmp' indicates SNMP is enabled. What is the most likely cause of the missing traps?

Trap 1: The NMS server is not listening on UDP port 162.

The NMS server is reachable via ping, but this does not confirm the SNMP trap receiver is listening; however, the more common cause on the router side is the missing trap-source.

Trap 2: The SNMP community string 'public' is not configured on the router.

The community 'public' is configured in the 'snmp-server host' command, and 'show snmp' would show it; missing community would prevent responses to polls, not traps.

Trap 3: The router's ACL is blocking outbound UDP traffic to port 162.

While possible, the engineer can ping the NMS, and typically SNMP traps use UDP; an ACL blocking UDP 162 would be a less common default scenario.

Study all Device Management common traps →

A
The NMS server is not listening on UDP port 162.
Why wrong: The NMS server is reachable via ping, but this does not confirm the SNMP trap receiver is listening; however, the more common cause on the router side is the missing trap-source.
B
The 'snmp-server trap-source' command is missing, causing traps to use an incorrect source IP.
Without 'snmp-server trap-source', the router uses the outgoing interface IP, which may not match the NMS's expected source or may be unreachable.
C
The SNMP community string 'public' is not configured on the router.
Why wrong: The community 'public' is configured in the 'snmp-server host' command, and 'show snmp' would show it; missing community would prevent responses to polls, not traps.
D
The router's ACL is blocking outbound UDP traffic to port 162.
Why wrong: While possible, the engineer can ping the NMS, and typically SNMP traps use UDP; an ACL blocking UDP 162 would be a less common default scenario.

Full breakdown with real-world context →

Question 2mediummultiple choice

Read the full NAT/PAT explanation →

An engineer is troubleshooting a router that fails to write its running configuration to startup configuration using 'copy running-config startup-config'. The command returns 'Destination filename [startup-config]?' and then the prompt returns without error. 'show startup-config' shows an empty configuration. What is the most likely cause?

Trap 1: The NVRAM is full and the router cannot save the configuration.

A full NVRAM would generate an explicit error message like 'NVRAM is full', not a silent failure.

Trap 2: The 'file prompt quiet' command is configured, suppressing prompts.

'file prompt quiet' suppresses confirmation prompts but would still show errors; it would not cause a silent empty startup-config.

Trap 3: The router is running in ROMMON mode.

In ROMMON mode, the router cannot boot IOS fully and 'copy running-config startup-config' would not be available.

Study all Device Management common traps →

A
The router is configured to boot from a TFTP server using the 'boot host' command, and the TFTP server is unreachable or does not allow writes.
When 'boot host' points to a remote file, 'copy running-config startup-config' tries to write to that remote server; if it fails, the local startup-config remains empty.
B
The NVRAM is full and the router cannot save the configuration.
Why wrong: A full NVRAM would generate an explicit error message like 'NVRAM is full', not a silent failure.
C
The 'file prompt quiet' command is configured, suppressing prompts.
Why wrong: 'file prompt quiet' suppresses confirmation prompts but would still show errors; it would not cause a silent empty startup-config.
D
The router is running in ROMMON mode.
Why wrong: In ROMMON mode, the router cannot boot IOS fully and 'copy running-config startup-config' would not be available.

Full breakdown with real-world context →

Question 3hardmultiple choice

Review the full routing breakdown →

A network engineer is troubleshooting a router that has been running for 200 days. The router experiences a sudden reboot, and after reload, the configuration is missing. 'show startup-config' returns 'startup-config is not present'. The engineer checks the boot variable: 'boot system flash:ios-image.bin'. What is the most likely cause of the configuration loss?

Trap 1: The router's NVRAM has a hardware failure and lost the…

Hardware failure is possible but less common; the more likely cause is that the configuration was never saved to NVRAM.

Trap 2: The 'boot system' command points to a TFTP server that also…

The 'boot system' command only specifies the IOS image; it does not affect the startup configuration unless a 'boot config' command is used.

Trap 3: The router's configuration register is set to 0x2142, ignoring…

Configuration register 0x2142 causes the router to bypass startup-config on boot, but the startup-config would still be present; 'show startup-config' would show the configuration, not 'not present'.

Study all Device Management common traps →

A
The router's NVRAM has a hardware failure and lost the configuration.
Why wrong: Hardware failure is possible but less common; the more likely cause is that the configuration was never saved to NVRAM.
B
The engineer did not execute 'copy running-config startup-config' before the reboot.
The router had been running for 200 days without a save; after reload, the running-config is lost, and startup-config is empty because it was never saved.
C
The 'boot system' command points to a TFTP server that also contains a configuration file, overwriting the local startup-config.
Why wrong: The 'boot system' command only specifies the IOS image; it does not affect the startup configuration unless a 'boot config' command is used.
D
The router's configuration register is set to 0x2142, ignoring startup-config.
Why wrong: Configuration register 0x2142 causes the router to bypass startup-config on boot, but the startup-config would still be present; 'show startup-config' would show the configuration, not 'not present'.

Full breakdown with real-world context →

Question 4mediummultiple choice

Read the full network assurance explanation →

An engineer is troubleshooting a router that is not sending syslog messages to the syslog server at 192.168.1.10. The configuration includes 'logging host 192.168.1.10' and 'logging trap informational'. The engineer can ping the syslog server from the router. 'show logging' shows that the logging buffer is filling with messages. What is the most likely cause?

Trap 1: The syslog server is not listening on UDP port 514.

While possible, the more common router-side issue is the missing source-interface, which can cause the server to drop messages if the source IP is not expected.

Trap 2: The 'logging on' command is not configured.

'logging on' is enabled by default; 'show logging' would indicate if it is disabled, and the buffer is filling, so logging is on.

Trap 3: The syslog server's IP address is incorrect in the configuration.

The engineer can ping the server, so the IP is reachable; the configuration shows the correct IP.

Study all Device Management common traps →

A
The syslog server is not listening on UDP port 514.
Why wrong: While possible, the more common router-side issue is the missing source-interface, which can cause the server to drop messages if the source IP is not expected.
B
The 'logging source-interface' command is missing, causing syslog messages to use an incorrect source IP.
Without 'logging source-interface', the router uses the IP of the egress interface, which may not be reachable from the syslog server or may be filtered.
C
The 'logging on' command is not configured.
Why wrong: 'logging on' is enabled by default; 'show logging' would indicate if it is disabled, and the buffer is filling, so logging is on.
D
The syslog server's IP address is incorrect in the configuration.
Why wrong: The engineer can ping the server, so the IP is reachable; the configuration shows the correct IP.

Full breakdown with real-world context →

Question 5mediummultiple choice

Study the full ACL explanation →

A network engineer is troubleshooting a router that is not responding to ICMP echo requests from a management station at 10.10.10.1. The router has an ACL applied to the VTY lines that permits only 10.10.10.0/24. The engineer can telnet to the router from the management station. What is the most likely cause?

Trap 1: The VTY ACL also applies to ICMP traffic.

VTY ACLs only control Telnet/SSH access, not ICMP.

Trap 2: The router has 'no ip icmp echo' configured globally.

There is no such global command; ICMP echo responses are controlled by interface ACLs or the 'ip icmp rate-limit' feature.

Trap 3: The management station is not in the routing table of the router.

If the management station were not reachable, Telnet would also fail.

Study all Device Management common traps →

A
The VTY ACL also applies to ICMP traffic.
Why wrong: VTY ACLs only control Telnet/SSH access, not ICMP.
B
An inbound ACL on the interface denies ICMP from 10.10.10.1.
Since Telnet works, the VTY ACL is not the issue; an interface ACL blocking ICMP is the likely cause.
C
The router has 'no ip icmp echo' configured globally.
Why wrong: There is no such global command; ICMP echo responses are controlled by interface ACLs or the 'ip icmp rate-limit' feature.
D
The management station is not in the routing table of the router.
Why wrong: If the management station were not reachable, Telnet would also fail.

Full breakdown with real-world context →

Question 6hardmultiple choice

Review the full routing breakdown →

An engineer is troubleshooting a router that is configured as an NTP client. The router's clock is not synchronizing with the NTP server at 192.168.1.1. 'show ntp status' shows 'clock is unsynchronized', and 'show ntp associations' shows the server as '.INIT.' with no reachability. The engineer can ping the NTP server. What is the most likely cause?

Trap 1: The router's 'ntp source' command is missing, causing NTP packets…

While possible, the 'ntp source' command is optional; the router will use the egress interface IP, which should be reachable. The server being unreachable for NTP is more specific.

Trap 2: The router's clock is set too far in the future, causing NTP to…

NTP can adjust large time differences, but the router would still show the server as reachable; the issue is no reachability at all.

Trap 3: The router has 'ntp authenticate' enabled without the proper key.

If authentication were mismatched, the association would show as 'configured' but not synchronized; the server would still show reachability.

Study all Device Management common traps →

A
The NTP server is not configured to respond to NTP requests from this client.
Ping works, but NTP uses UDP 123; the server may be configured to deny service to this client, or the server's NTP service is not running.
B
The router's 'ntp source' command is missing, causing NTP packets to use an incorrect source IP.
Why wrong: While possible, the 'ntp source' command is optional; the router will use the egress interface IP, which should be reachable. The server being unreachable for NTP is more specific.
C
The router's clock is set too far in the future, causing NTP to reject the server's time.
Why wrong: NTP can adjust large time differences, but the router would still show the server as reachable; the issue is no reachability at all.
D
The router has 'ntp authenticate' enabled without the proper key.
Why wrong: If authentication were mismatched, the association would show as 'configured' but not synchronized; the server would still show reachability.

Full breakdown with real-world context →

Question 7mediummultiple choice

Read the full network assurance explanation →

A network engineer is troubleshooting a router that is not responding to SNMP polls from the NMS at 10.1.1.100. The SNMP configuration includes 'snmp-server community public RO' and 'snmp-server community private RW'. The engineer can ping the router from the NMS. 'show snmp' shows SNMP is enabled. What is the most likely cause?

Trap 1: The NMS is using the wrong SNMP version.

The router supports SNMPv2c by default; if the NMS uses SNMPv1, it would still work with the community string. Version mismatch is less common than ACL filtering.

Trap 2: The router's SNMP agent is disabled due to high CPU.

High CPU would not disable SNMP; the agent would still respond, albeit slowly.

Trap 3: The NMS is using the wrong community string.

While possible, the engineer has verified the configuration; the community strings are correct, so the issue is likely access control.

Study all Device Management common traps →

A
The NMS is using the wrong SNMP version.
Why wrong: The router supports SNMPv2c by default; if the NMS uses SNMPv1, it would still work with the community string. Version mismatch is less common than ACL filtering.
B
An ACL is applied to the SNMP community that denies the NMS IP.
The configuration may include 'snmp-server community public RO 10', where ACL 10 denies the NMS; this is a common misconfiguration.
C
The router's SNMP agent is disabled due to high CPU.
Why wrong: High CPU would not disable SNMP; the agent would still respond, albeit slowly.
D
The NMS is using the wrong community string.
Why wrong: While possible, the engineer has verified the configuration; the community strings are correct, so the issue is likely access control.

Full breakdown with real-world context →

Question 8hardmultiple choice

Read the full NAT/PAT explanation →

An engineer is troubleshooting a router that is configured to archive configurations to a TFTP server at 192.168.1.10. The 'archive' configuration includes 'path tftp://192.168.1.10/config-archive' and 'write-memory'. The engineer notices that the archive is not being created after 'copy running-config startup-config'. What is the most likely cause?

Trap 1: The 'archive' configuration is missing the 'time-period' command.

The 'time-period' command is for periodic archiving, not for 'write-memory' triggered archiving.

Trap 2: The router's 'file prompt quiet' command is configured, suppressing…

Even with 'file prompt quiet', errors would still be logged; the archive would still attempt to write.

Trap 3: The TFTP server's IP address is incorrect in the path.

The engineer can likely ping the server; if the IP were wrong, the archive would fail with a timeout, but the server being unreachable is less specific than write permissions.

Study all Device Management common traps →

A
The TFTP server does not have write permissions for the directory.
TFTP servers often require a pre-existing file or write permissions; if the server cannot create the file, the archive fails silently.
B
The 'archive' configuration is missing the 'time-period' command.
Why wrong: The 'time-period' command is for periodic archiving, not for 'write-memory' triggered archiving.
C
The router's 'file prompt quiet' command is configured, suppressing error messages.
Why wrong: Even with 'file prompt quiet', errors would still be logged; the archive would still attempt to write.
D
The TFTP server's IP address is incorrect in the path.
Why wrong: The engineer can likely ping the server; if the IP were wrong, the archive would fail with a timeout, but the server being unreachable is less specific than write permissions.

Full breakdown with real-world context →

Question 9hardmultiple choice

Review the full routing breakdown →

A network engineer is troubleshooting a router that is not allowing SSH connections from any management station. The router has 'ip domain-name example.com' and 'crypto key generate rsa' configured. 'line vty 0 4' has 'transport input ssh' and 'login local'. The engineer can ping the router from a management station. What is the most likely cause?

Trap 1: The VTY lines are missing the 'login local' command.

The stem states 'login local' is configured, so this is not the issue.

Trap 2: The router has 'ip ssh version 1' configured, and the client only…

While possible, the default is SSHv2; the engineer would need to explicitly configure version 1, which is less common.

Trap 3: The management station is using the wrong username or password.

If the RSA key is valid, SSH would attempt authentication; the symptom of no connection at all suggests a transport layer issue, not authentication.

Study all Device Management common traps →

A
The RSA key was generated with a modulus less than 768 bits, causing SSH to fail.
Cisco IOS requires a minimum 768-bit RSA key for SSHv2; if the key is smaller, SSH will not accept connections.
B
The VTY lines are missing the 'login local' command.
Why wrong: The stem states 'login local' is configured, so this is not the issue.
C
The router has 'ip ssh version 1' configured, and the client only supports SSHv2.
Why wrong: While possible, the default is SSHv2; the engineer would need to explicitly configure version 1, which is less common.
D
The management station is using the wrong username or password.
Why wrong: If the RSA key is valid, SSH would attempt authentication; the symptom of no connection at all suggests a transport layer issue, not authentication.

Full breakdown with real-world context →

Question 10easymultiple choice

Study the full EIGRP explanation →

A network engineer runs the following command on Router R1:

R1# show ip eigrp neighbors

IP-EIGRP neighbors for process 100 H Address Interface Hold Uptime SRTT RTO Q Seq (sec) (ms) Cnt Num 0 192.168.1.2 Gi0/0 13 00:12:34 10 200 0 15 1 192.168.2.2 Gi0/1 10 00:10:22 12 200 0 22 2 10.10.10.2 Gi0/2 14 00:08:15 15 200 0 18

Based on this output, which statement is correct?

Trap 1: Neighbor 192.168.1.2 has a high SRTT indicating a slow link.

SRTT of 10 ms is low, not high.

Trap 2: Neighbor 10.10.10.2 is experiencing packet loss due to high RTO.

RTO of 200 ms is standard for this SRTT.

Trap 3: The Q count of 0 indicates that EIGRP is not exchanging routes.

Q count of 0 means no packets are queued, which is normal.

Study all Device Management common traps →

A
Neighbor 192.168.1.2 has a high SRTT indicating a slow link.
Why wrong: SRTT of 10 ms is low, not high.
B
All EIGRP neighbors are operating normally.
All neighbors show normal hold timers, uptimes, and zero queued packets.
C
Neighbor 10.10.10.2 is experiencing packet loss due to high RTO.
Why wrong: RTO of 200 ms is standard for this SRTT.
D
The Q count of 0 indicates that EIGRP is not exchanging routes.
Why wrong: Q count of 0 means no packets are queued, which is normal.

Full breakdown with real-world context →

Question 11mediummultiple choice

Review the full OSPF breakdown →

A network engineer runs the following command on Router R1:

R1# show ip ospf neighbor

Neighbor ID     Pri   State           Dead Time   Address         Interface
192.168.1.2      1   FULL/DR         00:00:35    192.168.1.2     Gi0/0
192.168.2.2      1   2WAY/DROTHER    00:00:38    192.168.2.2     Gi0/1
10.10.10.2       1   FULL/BDR        00:00:32    10.10.10.2      Gi0/2

Based on this output, what is a potential issue?

Trap 1: Neighbor 192.168.2.2 is stuck in 2WAY state, indicating a problem.

2WAY is a normal state for DROTHER neighbors.

Trap 2: The DR election is incomplete on Gi0/0.

The state is FULL/DR, which is correct.

Trap 3: Neighbor 10.10.10.2 should be in FULL/DR state.

It is the BDR, so FULL/BDR is correct.

Study all Device Management common traps →

A
Neighbor 192.168.2.2 is stuck in 2WAY state, indicating a problem.
Why wrong: 2WAY is a normal state for DROTHER neighbors.
B
The DR election is incomplete on Gi0/0.
Why wrong: The state is FULL/DR, which is correct.
C
All OSPF neighbors are in appropriate states for their roles.
Each neighbor is in the correct state based on its role (DR, BDR, DROTHER).
D
Neighbor 10.10.10.2 should be in FULL/DR state.
Why wrong: It is the BDR, so FULL/BDR is correct.

Full breakdown with real-world context →

Question 12mediummultiple choice

Open the full BGP breakdown →

A network engineer runs the following command on Router R1:

R1# show bgp ipv4 unicast summary

BGP router identifier 192.168.0.1, local AS number 65001 BGP table version is 10, main routing table version 10

Neighbor        V           AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
192.168.1.2     4        65002    1002    1000       10    0    0 00:15:30        5
192.168.2.2     4        65003    1005    1003       10    0    0 00:14:20        3
10.10.10.2      4        65004       0       0        0    0    0 00:00:05 Idle

Based on this output, what is the problem with neighbor 10.10.10.2?

Trap 1: The neighbor is administratively shut down.

Idle state can result from many issues, but not specifically admin shutdown without further evidence.

Trap 2: The neighbor is in the process of establishing the session.

Idle is not a transitional state; it indicates a failure.

Trap 3: The neighbor has sent all its prefixes and is waiting for updates.

Idle state means no session exists.

Study all Device Management common traps →

A
The neighbor is administratively shut down.
Why wrong: Idle state can result from many issues, but not specifically admin shutdown without further evidence.
B
The BGP session is not established; possible misconfiguration or reachability issue.
Idle state with no messages indicates the session is down.
C
The neighbor is in the process of establishing the session.
Why wrong: Idle is not a transitional state; it indicates a failure.
D
The neighbor has sent all its prefixes and is waiting for updates.
Why wrong: Idle state means no session exists.

Full breakdown with real-world context →

Question 13easymultiple choice

Review the full routing breakdown →

A network engineer runs the following command on Router R1:

R1# show route-map TEST

route-map TEST, permit, sequence 10 Match clauses:

ip address (access-lists): 10

Set clauses: metric 50 route-map TEST, deny, sequence 20 Match clauses:

ip address (access-lists): 20

Set clauses:

Based on this output, what is the effect of this route-map when applied to a redistribution command?

Trap 1: All routes are redistributed with metric 50.

Only routes matching ACL 10 get metric 50; others are denied.

Trap 2: Routes matching ACL 20 are redistributed with default metric.

Sequence 20 is deny, so those routes are not redistributed.

Trap 3: The route-map has no effect because set clauses are missing in…

The deny action still prevents redistribution.

Study all Device Management common traps →

A
All routes are redistributed with metric 50.
Why wrong: Only routes matching ACL 10 get metric 50; others are denied.
B
Routes matching ACL 10 are redistributed with metric 50; routes matching ACL 20 are denied; all other routes are also denied.
This matches the route-map logic.
C
Routes matching ACL 20 are redistributed with default metric.
Why wrong: Sequence 20 is deny, so those routes are not redistributed.
D
The route-map has no effect because set clauses are missing in sequence 20.
Why wrong: The deny action still prevents redistribution.

Full breakdown with real-world context →

Question 14mediummultiple choice

Read the full MPLS explanation →

A network engineer runs the following command on Router R1:

R1# show mpls ldp neighbor

Peer LDP Ident: 192.168.1.2:0, Local LDP Ident: 192.168.0.1:0 TCP connection: 192.168.1.2.646 - 192.168.0.1.49876 State: Oper; Msgs sent/rcvd: 100/105; Downstream on demand Up time: 00:10:30 LDP discovery sources: GigabitEthernet0/0, Src IP addr: 192.168.1.2 Addresses bound to peer LDP Ident:

192.168.1.2        10.1.1.2

Based on this output, what is the state of the LDP session?

Trap 1: The LDP session is down due to a TCP connection issue.

The state is Oper, meaning it is up.

Trap 2: The LDP session is in the process of being established.

Oper is not a transitional state.

Trap 3: The LDP session is using downstream on demand mode, which is a…

Downstream on demand is a valid mode.

Study all Device Management common traps →

A
The LDP session is down due to a TCP connection issue.
Why wrong: The state is Oper, meaning it is up.
B
The LDP session is operational and exchanging label information.
State Oper indicates the session is up and running.
C
The LDP session is in the process of being established.
Why wrong: Oper is not a transitional state.
D
The LDP session is using downstream on demand mode, which is a problem.
Why wrong: Downstream on demand is a valid mode.

Full breakdown with real-world context →

Question 15mediummultiple choice

Read the full VPN explanation →

A network engineer runs the following command on Router R1:

R1# show dmvpn

Legend: Attrb -> S: Static, D: Dynamic, I: Incomplete N: NATed, L: Local, X: No Socket

# Entries: 2
Interface: Tunnel0, IPv4 NHRP Details

Type: Hub, NHRP Peers: 2,

# Ent  Peer NBMA Addr Peer Tunnel Addr State  UpDn Tm Attrb

----- --------------- --------------- ----- -------- ----- 1 192.168.1.2 10.0.0.2 UP 00:15:30 D 2 192.168.2.2 10.0.0.3 UP 00:14:20 D

Based on this output, which statement is correct?

Trap 1: The DMVPN tunnel is not functioning because there are only two…

Two peers is normal for a hub with two spokes.

Trap 2: The hub router has static NHRP entries for the spokes.

The entries are marked D for dynamic.

Trap 3: The spokes are not able to communicate with each other.

This output does not provide information about spoke-to-spoke communication.

Study all Device Management common traps →

A
The DMVPN tunnel is not functioning because there are only two peers.
Why wrong: Two peers is normal for a hub with two spokes.
B
Both spoke routers have established dynamic NHRP registrations with the hub.
The state is UP and attribute is D (dynamic).
C
The hub router has static NHRP entries for the spokes.
Why wrong: The entries are marked D for dynamic.
D
The spokes are not able to communicate with each other.
Why wrong: This output does not provide information about spoke-to-spoke communication.

Full breakdown with real-world context →

Question 16hardmultiple choice

Study the full ACL explanation →

A network engineer runs the following command on Router R1:

R1# show policy-map control-plane

Control Plane

Service-policy input: CoPP class-map: MANAGEMENT (match-all) 100 packets, 5000 bytes 5 minute offered rate 0 bps police: 8000 bps, 1500 limit, 1500 extended limit conformed 95 packets, 4750 bytes; action: transmit exceeded 5 packets, 250 bytes; action: drop conformed 0 bps, exceed 0 bps

class-map: ROUTING (match-all) 200 packets, 10000 bytes 5 minute offered rate 0 bps police: 16000 bps, 3000 limit, 3000 extended limit conformed 200 packets, 10000 bytes; action: transmit exceeded 0 packets, 0 bytes; action: drop conformed 0 bps, exceed 0 bps

Based on this output, what is happening to traffic matching the MANAGEMENT class?

Trap 1: All management traffic is being transmitted without any drops.

5 packets were dropped.

Trap 2: The management traffic is being rate-limited but no packets are…

Drops are occurring.

Trap 3: The police rate is too high, causing all traffic to be dropped.

Only 5 out of 100 packets were dropped.

Study all Device Management common traps →

A
All management traffic is being transmitted without any drops.
Why wrong: 5 packets were dropped.
B
Some management traffic is being dropped because it exceeds the configured police rate.
The exceeded counter shows 5 packets dropped.
C
The management traffic is being rate-limited but no packets are dropped.
Why wrong: Drops are occurring.
D
The police rate is too high, causing all traffic to be dropped.
Why wrong: Only 5 out of 100 packets were dropped.

Full breakdown with real-world context →

Question 17easymultiple choice

Review the full routing breakdown →

A network engineer runs the following command on Router R1:

R1# show ip sla statistics

IPSLAs Latest Statistics:

Round Trip Time (RTT) for Index 1 Latest RTT: 10 ms Latest RTT (milliseconds): 10 Number of successes: 100 Number of failures: 0 Operation time to live: 3000 Operation frequency: 60 seconds Next operation start time: 00:00:45

Based on this output, what is the status of the IP SLA operation?

Trap 1: The IP SLA operation has failed 100 times.

Number of failures is 0.

Trap 2: The IP SLA operation is not configured correctly.

The statistics show normal operation.

Trap 3: The IP SLA operation is about to expire.

Time to live is 3000, which is sufficient.

Study all Device Management common traps →

A
The IP SLA operation has failed 100 times.
Why wrong: Number of failures is 0.
B
The IP SLA operation is successful and has a low RTT.
100 successes and 10 ms RTT indicate good performance.
C
The IP SLA operation is not configured correctly.
Why wrong: The statistics show normal operation.
D
The IP SLA operation is about to expire.
Why wrong: Time to live is 3000, which is sufficient.

Full breakdown with real-world context →

Question 18mediummultiple choice

Read the full MPLS explanation →

A network engineer runs the following command on Router R1:

R1# show flow interface GigabitEthernet0/0
Interface GigabitEthernet0/0

FNF: enabled Ingress IPV4/IPV6 flow monitoring: enabled Exporter: EXPORTER1 Monitor: MONITOR1 Egress IPV4/IPV6 flow monitoring: disabled Ingress MPLS flow monitoring: disabled Egress MPLS flow monitoring: disabled

Based on this output, what is the state of NetFlow on this interface?

Trap 1: NetFlow is fully enabled for both ingress and egress traffic.

Egress is disabled.

Trap 2: NetFlow is not configured on this interface.

It is enabled for ingress.

Trap 3: NetFlow is only monitoring MPLS traffic.

MPLS monitoring is disabled.

Study all Device Management common traps →

A
NetFlow is fully enabled for both ingress and egress traffic.
Why wrong: Egress is disabled.
B
NetFlow is only monitoring incoming traffic on this interface.
Ingress is enabled, egress is disabled.
C
NetFlow is not configured on this interface.
Why wrong: It is enabled for ingress.
D
NetFlow is only monitoring MPLS traffic.
Why wrong: MPLS monitoring is disabled.

Full breakdown with real-world context →

Question 19mediummultiple choice

Study the full EIGRP explanation →

Given the following partial configuration on router R1:

router eigrp 100
 network 10.0.0.0 0.255.255.255
 network 192.168.1.0 0.0.0.255

interface GigabitEthernet0/0
 ip address 10.1.1.1 255.255.255.0

interface GigabitEthernet0/1
 ip address 192.168.1.1 255.255.255.0

interface GigabitEthernet0/2
 ip address 172.16.1.1 255.255.255.0

What is the effect of this configuration?

Trap 1: EIGRP will form adjacencies and advertise all three interfaces…

The network 172.16.1.0 is not covered by any network statement; 10.0.0.0 covers 10.1.1.0/24, and 192.168.1.0 covers 192.168.1.0/24, but 172.16.1.0/24 is not included.

Trap 2: EIGRP will advertise all three networks because the network…

The network 10.0.0.0 command only matches interfaces whose IP address falls within the 10.0.0.0/8 range, not 172.16.x.x or 192.168.x.x.

Trap 3: EIGRP will not form any adjacencies because the network statements…

EIGRP network statements can use wildcard masks; the configuration is valid. The issue is the missing network statement for 172.16.1.0/24.

Study all Device Management common traps →

A
EIGRP will form adjacencies and advertise all three interfaces because the network statements use classful boundaries.
Why wrong: The network 172.16.1.0 is not covered by any network statement; 10.0.0.0 covers 10.1.1.0/24, and 192.168.1.0 covers 192.168.1.0/24, but 172.16.1.0/24 is not included.
B
EIGRP will only advertise the 10.1.1.0/24 and 192.168.1.0/24 networks; the 172.16.1.0/24 network will not be advertised and no EIGRP adjacency will be formed on that interface.
Only interfaces matching the network statements are enabled for EIGRP. 172.16.1.0/24 does not match 10.0.0.0 or 192.168.1.0, so it is excluded.
C
EIGRP will advertise all three networks because the network 10.0.0.0 command includes all interfaces with an IP starting with 1, 172, or 192.
Why wrong: The network 10.0.0.0 command only matches interfaces whose IP address falls within the 10.0.0.0/8 range, not 172.16.x.x or 192.168.x.x.
D
EIGRP will not form any adjacencies because the network statements must use exact subnet masks instead of wildcard masks.
Why wrong: EIGRP network statements can use wildcard masks; the configuration is valid. The issue is the missing network statement for 172.16.1.0/24.

Full breakdown with real-world context →

Question 20mediummultiple choice

Review the full OSPF breakdown →

Consider the following partial configuration on router R2:

interface GigabitEthernet0/0
 ip address 10.0.0.2 255.255.255.0
 ip ospf 1 area 0

interface GigabitEthernet0/1
 ip address 192.168.1.2 255.255.255.0
 ip ospf 1 area 0

router ospf 1

router-id 2.2.2.2

network 10.0.0.0 0.0.0.255 area 0
 network 192.168.1.0 0.0.0.255 area 0

What is the effect of this configuration?

Trap 1: OSPF will not form adjacencies because the interface and network…

There is no conflict; both methods can be used together. OSPF will use the interface configuration and the network statement will also apply, but no conflict arises.

Trap 2: OSPF will form adjacencies on both interfaces, but the router-id…

The router-id is explicitly set to 2.2.2.2 and will not be overridden by any interface IP unless the router-id is removed or reset.

Trap 3: OSPF will only form adjacency on GigabitEthernet0/1 because the…

The network 10.0.0.0 0.0.0.255 area 0 correctly matches the 10.0.0.0/24 subnet on GigabitEthernet0/0.

Study all Device Management common traps →

A
OSPF will not form adjacencies because the interface and network commands conflict, causing OSPF to ignore the network statements.
Why wrong: There is no conflict; both methods can be used together. OSPF will use the interface configuration and the network statement will also apply, but no conflict arises.
B
OSPF will form adjacencies on both interfaces, but the router-id 2.2.2.2 will be overridden by the highest loopback IP.
Why wrong: The router-id is explicitly set to 2.2.2.2 and will not be overridden by any interface IP unless the router-id is removed or reset.
C
OSPF will form adjacencies on both interfaces as intended; the configuration is redundant but functional.
Both interfaces have OSPF enabled via the interface command and the network statement. This is acceptable and OSPF will operate normally.
D
OSPF will only form adjacency on GigabitEthernet0/1 because the network statement for 10.0.0.0 is incorrect.
Why wrong: The network 10.0.0.0 0.0.0.255 area 0 correctly matches the 10.0.0.0/24 subnet on GigabitEthernet0/0.

Full breakdown with real-world context →

Continue with 20-question session →

Free account

Track your progress over time

Create a free account to save your results and see which topics improve across sessions.

Focused Device Management sessions

Start a Device Management only practice session

Every question in these sessions is drawn from the Device Management domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all Device Management questions →Mixed 300-410 session

Frequently asked questions

What does the 300-410 exam test about Device Management?: Device Management questions test whether you can apply the concept in context, not just recognise a definition.
How should I use these practice questions?: Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just Device Management questions in a focused session?: Yes — the session launcher on this page draws every question from the Device Management domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other 300-410 topics?: Use the topic links above to move to related areas, or go back to the 300-410 question bank to see all topics.
Are these real exam questions or dumps?: These are original practice questions written to test the same concepts the 300-410 exam covers. They are not copied from any real exam or dump site.

Device Management only

10 questions 20 questions 30 questions 50 questions

Mixed 300-410 session

Track your progress

A free account saves results across sessions and highlights which topics need work.

Study resources

All 300-410 questions Device Management domain overview 300-410 exam guide

Exam traps to avoid

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Device Management practice questions

What to know about Device Management

Common Device Management exam traps

Device Management questions

Track your progress over time

Start a Device Management only practice session

Related 300-410 topic practice pages

Layer 3 Technologies practice questions

EIGRP Troubleshooting practice questions

OSPF Troubleshooting (v2/v3) practice questions

BGP Troubleshooting practice questions

Route Redistribution practice questions

Policy-Based Routing (PBR) practice questions

VRF-Lite practice questions

Route Maps and Route Filtering practice questions

Administrative Distance practice questions

Route Summarization practice questions

Bidirectional Forwarding Detection (BFD) practice questions

VPN Technologies practice questions

Frequently asked questions

Track your progress

Study resources

Exam traps to avoid