Courseiva

CCNA Snmp Questions

24 questions · Snmp topic · All types, answers revealed

1
MCQmedium

What is a key difference between SNMPv3 and earlier SNMP versions?

A.SNMPv3 supports IPv4 only
B.SNMPv3 adds authentication and encryption features
C.SNMPv3 cannot be used for monitoring interface counters
D.SNMPv3 replaces syslog completely
AnswerB

SNMPv3's defining improvement over SNMPv1/v2c is its User-based Security Model (USM), providing message authentication via HMAC-MD5 or HMAC-SHA and encryption using DES or AES. Whereas earlier versions pass community strings in cleartext and offer no true authentication, SNMPv3 validates each message's integrity and origin and protects the payload from eavesdropping. This strong security is precisely why SNMPv3 is considered the primary differentiator for secure network management.

Why this answer

SNMPv3 improves security by adding authentication, message integrity, and privacy features. Earlier versions, especially SNMPv1 and v2c, rely on community strings and provide much weaker protection.

Exam trap

A common exam trap is to mistakenly believe that SNMPv3 restricts network monitoring capabilities or IP protocol support. Some candidates incorrectly think SNMPv3 supports only IPv4 or that it replaces syslog entirely. These misconceptions arise because the question emphasizes SNMPv3’s differences without clarifying what remains unchanged.

The trap is to focus on unrelated protocol features rather than the core improvement: security. Selecting options that mention monitoring limitations or protocol replacement leads to incorrect answers. Understanding that SNMPv3’s main advancement is adding authentication and encryption prevents falling into this trap.

Why the other options are wrong

A

Option A is incorrect because SNMPv3 supports both IPv4 and IPv6 networks. It is not limited to IPv4 only, so this option misrepresents SNMPv3’s capabilities.

C

Option C is incorrect since SNMPv3 continues to support monitoring functions such as interface counters. It does not remove or restrict these capabilities.

D

Option D is incorrect because SNMPv3 does not replace syslog. Both protocols coexist and serve different roles in network management and logging.

2
Multi-Selectmedium

Which two statements about SNMPv2c are correct? (Choose two.)

Select 2 answers
A.It uses a community string that is transmitted in clear text.
B.It encrypts messages with AES by default.
C.It supports the GetBulk operation to retrieve large tables efficiently.
D.It authenticates each user with a username and SHA hash.
E.It transports messages over TCP port 161.
AnswersA, C

Community strings are not encrypted.

Why this answer

SNMPv2c authenticates with a community string that is sent in clear text, and it adds GetBulk and 64-bit counters over v1. It provides no encryption.

Why the other options are wrong

B

v2c has no privacy.

D

v2c uses community strings.

E

Default transport is UDP 161/162.

3
Multi-Selectmedium

Which TWO statements correctly describe characteristics of SNMPv2c and SNMPv3 for network monitoring?

Select 2 answers
A.SNMPv3 supports authentication and encryption for secure network monitoring.
B.SNMPv2c uses community strings sent in clear text to authenticate requests.
C.SNMPv3 provides the same security level as SNMPv2c but with additional trap support.
D.SNMPv2c supports only GET and SET operations, but not traps.
E.SNMPv3 uses community strings to authenticate agents and managers.
AnswersA, B

SNMPv3 is correct because it introduces a User-based Security Model (USM) offering three security levels: noAuthNoPriv (no authentication or encryption, but still uses usernames), authNoPriv (HMAC-MD5 or HMAC-SHA authentication, no encryption), and authPriv (authentication plus DES or AES encryption). This allows network monitoring to operate with data integrity, source authentication, and confidentiality, protecting against sniffing and unauthorized modifications. No other version provides these combined security features, making it suitable for production and large-scale networks.

Why this answer

SNMPv3 is correct because it introduces authentication (MD5/SHA) and encryption (DES/AES) for secure monitoring. SNMPv2c is correct because it uses community strings transmitted in cleartext, lacking security. Option C is wrong: SNMPv3 is more secure than v2c, not the same.

Option D is wrong: SNMPv2c supports traps in addition to GET and SET. Option E is wrong: SNMPv3 uses usernames and security models, not community strings.

Exam trap

Cisco often tests the misconception that SNMPv3 is merely an extension of SNMPv2c with added trap support, when in fact the key differentiator is the security model (authentication and encryption), and both versions support traps.

Why the other options are wrong

C

SNMPv3 provides significantly higher security than SNMPv2c by adding authentication and encryption, whereas SNMPv2c uses only community strings in clear text. Both versions support traps, so the statement incorrectly claims SNMPv3 has additional trap support, which is not a distinguishing feature.

D

SNMPv2c supports GET, SET, and trap operations, just like SNMPv1 and SNMPv3. The statement is incorrect because it claims SNMPv2c does not support traps, which is false; traps are a key feature for asynchronous notifications in network monitoring.

E

SNMPv3 uses the User-based Security Model (USM) with usernames and authentication keys, not community strings. Community strings are a feature of SNMPv1 and SNMPv2c, which are transmitted in clear text and provide weak security.

4
PBQhard

You are connected to R1, a Cisco ISR 4331 running IOS-XE. Configure SNMP: community 'public' read-only and 'private' read-write for SNMPv2c; SNMPv3 group V3GRP requiring authentication and privacy, with user 'admin' using SHA authentication (password Cisco123) and AES-128 encryption (password Cisco456); and send traps to the management server 203.0.113.10 both as SNMPv2c using community 'public' and as SNMPv3 for user 'admin' with authentication and privacy. Verify with show snmp and show snmp user.

Hints

  • •SNMPv3 needs a group (with a security level) before the user can be bound to it.
  • •The SNMPv3 user requires both auth and priv passwords for priv security level.
  • •Use snmp-server enable traps and then define each trap receiver with snmp-server host.
A.snmp-server community public RO snmp-server community private RW snmp-server group V3GRP v3 priv snmp-server user admin V3GRP v3 auth sha Cisco123 priv aes 128 Cisco456 snmp-server enable traps snmp-server host 203.0.113.10 version 2c public snmp-server host 203.0.113.10 version 3 priv admin
B.snmp-server community public snmp-server community private snmp-server group V3GRP v3 priv snmp-server user admin V3GRP v3 auth md5 Cisco123 priv des Cisco456 snmp-server enable traps snmp-server host 203.0.113.10 version 2c public snmp-server host 203.0.113.10 version 3 priv admin
C.snmp-server community public RO snmp-server community private RW snmp-server group V3GRP v3 priv snmp-server user admin V3GRP v3 auth sha Cisco123 priv aes 128 Cisco456 snmp-server enable traps snmp-server host 203.0.113.10 version 2c private snmp-server host 203.0.113.10 version 3 priv admin
D.snmp-server community public RO snmp-server community private RW snmp-server group V3GRP v3 priv snmp-server user admin V3GRP v3 auth sha Cisco123 priv aes 128 Cisco456 snmp-server enable traps snmp-server host 203.0.113.10 version 2c public snmp-server host 203.0.113.10 version 3 noauth admin
AnswerA
solution
! R1
snmp-server community public RO
snmp-server community private RW
snmp-server group V3GRP v3 priv
snmp-server user admin V3GRP v3 auth sha Cisco123 priv aes 128 Cisco456
snmp-server enable traps
snmp-server host 203.0.113.10 version 2c public
snmp-server host 203.0.113.10 version 3 priv admin

Why this answer

SNMPv2c uses community strings (snmp-server community <string> RO|RW). SNMPv3 needs a group that defines the security model and level (snmp-server group V3GRP v3 priv) and a user bound to that group (snmp-server user admin V3GRP v3 auth sha <pw> priv aes 128 <pw>). Traps are enabled with snmp-server enable traps and sent with snmp-server host: for v2c the community string is given, for v3 the security level (priv) and the user name.

The v3 host security level must match what the user is configured for.

Exam trap

Watch out for common mistakes: using MD5/DES instead of SHA/AES for SNMPv3, forgetting RO/RW keywords on community strings, using the wrong community string for traps, and selecting the wrong NetFlow version. Always verify the exact requirements in the question.

Why the other options are wrong

B

The specific factual error: SNMPv3 user is configured with MD5 and DES instead of SHA and AES 128; community strings are missing RO/RW keywords.

C

The specific factual error: The v2c trap host uses 'private' instead of 'public' community string.

D

The v3 trap receiver must use the same security level (priv) as the user and group; noauth does not match.

5
PBQhard

You are connected to R1. Configure SNMPv3 for user 'monitor' in group 'AdminGroup' with authentication (SHA) and encryption (AES-128), with read access limited to a view named AdminView that includes the whole iso tree. Also configure an SNMPv2c read-only community 'cisco123' and send traps to the management server 192.0.2.100 using that community.

Network Topology
G0/010.0.0.1/30G0/010.0.0.2/30linkG0/1203.0.113.1/30G0/1203.0.113.2/30linkR1R2R3

Hints

  • •Create the SNMPv3 view before the group that references it.
  • •The group security level must be priv for AES-128 encryption.
  • •The v2c community string is referenced by the trap host, so define it and enable traps.
A.snmp-server view AdminView iso included snmp-server group AdminGroup v3 priv read AdminView snmp-server user monitor AdminGroup v3 auth sha cisco123 priv aes 128 cisco123 snmp-server community cisco123 RO snmp-server enable traps snmp-server host 192.0.2.100 version 2c cisco123
B.snmp-server view AdminView iso included snmp-server group AdminGroup v3 priv read AdminView snmp-server user monitor AdminGroup v3 auth sha cisco123 priv aes 128 cisco123 snmp-server community cisco123 RW snmp-server enable traps snmp-server host 192.0.2.100 version 2c cisco123
C.snmp-server view AdminView iso included snmp-server group AdminGroup v3 priv read AdminView snmp-server user monitor AdminGroup v3 auth sha cisco123 priv des cisco123 snmp-server community cisco123 RO snmp-server enable traps snmp-server host 192.0.2.100 version 2c cisco123
D.snmp-server view AdminView iso included snmp-server group AdminGroup v3 priv read AdminView snmp-server user monitor AdminGroup v3 auth sha cisco123 priv aes 128 cisco123 snmp-server community cisco123 RO snmp-server host 192.0.2.100 version 2c cisco123
AnswerA
solution
! R1
snmp-server view AdminView iso included
snmp-server group AdminGroup v3 priv read AdminView
snmp-server user monitor AdminGroup v3 auth sha cisco123 priv aes 128 cisco123
snmp-server community cisco123 RO
snmp-server enable traps
snmp-server host 192.0.2.100 version 2c cisco123

Why this answer

The v3 group needs a view for its read access (snmp-server view AdminView iso included), the group is created with security level priv (snmp-server group AdminGroup v3 priv read AdminView), and the user is bound to it with SHA and AES-128 (snmp-server user monitor AdminGroup v3 auth sha <pw> priv aes 128 <pw>). The v2c community is read-only (RO). Traps require snmp-server enable traps and a trap receiver, snmp-server host 192.0.2.100 version 2c cisco123.

Exam trap

Pay close attention to the exact security requirements: 'priv' for encryption, AES-128 specifically, and NetFlow version 9. The exam often tests subtle differences between 'auth' and 'priv' levels, encryption algorithms, and NetFlow versions.

Why the other options are wrong

B

A read-write community exceeds the read-only requirement.

C

The encryption algorithm specified is DES (56-bit) instead of AES-128.

D

Without snmp-server enable traps no traps are generated even though a receiver is defined.

6
PBQhard

You are connected to R1 running IOS-XE. Configure SNMPv2c with the read-only community 'monitorRO'; SNMPv3 group ADMINS requiring authentication and privacy with user 'admin' using MD5 authentication (password cisco123) and DES encryption (password cisco456); and send linkUp/linkDown traps to the management server 192.0.2.100 using SNMPv2c and community 'monitorRO'.

Network Topology
G0/010.0.0.1/30G0/010.0.0.2/30linkR1R2

Hints

  • •Create the SNMPv3 group (priv) before the user that belongs to it.
  • •The SNMPv3 user needs both auth and priv parameters.
  • •Use snmp-server enable traps to activate trap generation, then define the trap receiver with snmp-server host.
A.snmp-server community monitorRO RO snmp-server group ADMINS v3 priv snmp-server user admin ADMINS v3 auth md5 cisco123 priv des cisco456 snmp-server enable traps snmp linkdown linkup snmp-server host 192.0.2.100 traps version 2c monitorRO
B.snmp-server community monitorRO RW snmp-server group ADMINS v3 priv snmp-server user admin ADMINS v3 auth md5 cisco123 priv des cisco456 snmp-server enable traps snmp linkdown linkup snmp-server host 192.0.2.100 traps version 2c monitorRO
C.snmp-server community monitorRO RO snmp-server user admin v3 auth md5 cisco123 priv des cisco456 snmp-server enable traps snmp linkdown linkup snmp-server host 192.0.2.100 traps version 2c monitorRO
D.snmp-server community monitorRO RO snmp-server group ADMINS v3 priv snmp-server user admin ADMINS v3 auth md5 cisco123 priv des cisco456 snmp-server host 192.0.2.100 traps version 2c monitorRO
AnswerA
solution
! R1
snmp-server community monitorRO RO
snmp-server group ADMINS v3 priv
snmp-server user admin ADMINS v3 auth md5 cisco123 priv des cisco456
snmp-server enable traps snmp linkdown linkup
snmp-server host 192.0.2.100 traps version 2c monitorRO

Why this answer

The v2c community is read-only (RO). SNMPv3 needs a group that sets the security level (snmp-server group ADMINS v3 priv) and a user bound to it (snmp-server user admin ADMINS v3 auth md5 ... priv des ...). Traps need snmp-server enable traps snmp linkdown linkup and a receiver with snmp-server host 192.0.2.100 traps version 2c monitorRO.

Exam trap

Students often forget to apply NetFlow on an interface with 'ip flow ingress' or confuse it with Flexible NetFlow commands. Also, they may omit the trap enable command or use the wrong SNMP version for trap delivery. Always ensure that NetFlow collection is enabled on an interface and that SNMP traps are both enabled globally and sent to the correct host.

Why the other options are wrong

B

The configuration omits the 'ip flow ingress' (or any) interface command, so NetFlow will not collect any traffic.

C

The 'ip flow egress' command monitors outbound traffic, not the specified inbound traffic on GigabitEthernet0/0.

D

The 'ip flow monitor FLOW-MONITOR input' command references a flexible NetFlow monitor that does not exist; traditional 'ip flow ingress' is required.

7
MCQhard

A network engineer notices that an NMS at 10.1.1.200 cannot poll a router that has SNMPv2c configured with community string 'public'. What is causing this issue?

A.SNMPv2c is not enabled on the router.
B.The SNMP community 'public' has an access list that only permits host 10.1.1.100.
C.The NMS is using the wrong community string.
D.The router's SNMP agent is not listening on the interface facing 10.1.1.200.
AnswerB

The community string 'public' has an access control list applied that restricts source addresses to 10.1.1.100 only. When the NMS at 10.1.1.200 sends an SNMP poll, the router checks the source IP against the ACL bound to the community string; because 10.1.1.200 is not permitted, the router silently discards the request. This explains why the NMS receives no response, even though the community string matches and the SNMP agent is running.

Why this answer

SNMPv2c community strings can be restricted by an access control list (ACL) that specifies which source IP addresses are allowed to poll the router. If the ACL only permits host 10.1.1.100, then the NMS at 10.1.1.200 will be denied access even though the community string 'public' is correct. This is a common configuration for security, but it prevents polling from unauthorized hosts.

Exam trap

Cisco often tests the misconception that SNMP community strings are the only authentication mechanism, leading candidates to overlook the ACL restriction that can silently block polling from specific hosts.

Why the other options are wrong

A

Many believe SNMP requires an additional global command to start; on Cisco IOS, a community string entry enables the agent.

C

Polling failures are often attributed to community string errors, but when the string matches, an ACL restriction produces identical symptoms.

D

Candidates may assume the agent must be bound to an interface, but Cisco IOS SNMP agents respond on any interface unless limited by an ACL or VRF.

8
PBQhard

You are connected to R1, a Cisco ISR 4321 running IOS-XE. Configure SNMPv2c with the read-only community 'public' and SNMPv3 with user 'admin' (in group ADMINS, authPriv) using SHA authentication and AES-128 encryption. Send SNMP traps to the management server 203.0.113.10. Also configure Flexible NetFlow to export NetFlow version 9 records to 203.0.113.20 on UDP port 2055 for traffic entering GigabitEthernet0/0. Verify with show commands.

Network Topology
G0/0192.168.1.1/24Management NetworkR1Server

Hints

  • •An SNMPv3 user must belong to a group; create 'snmp-server group ADMINS v3 priv' first, then the user with auth sha and priv aes 128.
  • •Traps need 'snmp-server enable traps' and an 'snmp-server host' receiver.
  • •Flexible NetFlow needs an exporter (destination, transport udp 2055, export-protocol netflow-v9), a monitor that uses it, and the monitor applied to the interface.
A.snmp-server community public RO snmp-server group ADMINS v3 priv snmp-server user admin ADMINS v3 auth sha AuthPass123 priv aes 128 PrivPass123 snmp-server enable traps snmp-server host 203.0.113.10 traps version 2c public flow exporter EXP1 destination 203.0.113.20 transport udp 2055 export-protocol netflow-v9 flow monitor MON1 exporter EXP1 record netflow ipv4 original-input interface GigabitEthernet0/0 ip flow monitor MON1 input
B.snmp-server community public RO snmp-server group ADMINS v3 priv snmp-server user admin ADMINS v3 auth sha AuthPass123 priv aes 128 PrivPass123 snmp-server enable traps snmp-server host 203.0.113.10 traps version 2c public flow exporter EXP1 destination 203.0.113.20 transport udp 9996 export-protocol ipfix flow monitor MON1 exporter EXP1 record netflow ipv4 original-input interface GigabitEthernet0/0 ip flow monitor MON1 input
C.snmp-server community public RO snmp-server group ADMINS v3 priv snmp-server user admin ADMINS v3 auth md5 AuthPass123 priv des PrivPass123 snmp-server enable traps snmp-server host 203.0.113.10 traps version 2c public flow exporter EXP1 destination 203.0.113.20 transport udp 2055 export-protocol netflow-v9 flow monitor MON1 exporter EXP1 record netflow ipv4 original-input interface GigabitEthernet0/0 ip flow monitor MON1 input
D.snmp-server community public RO snmp-server group ADMINS v3 priv snmp-server user admin ADMINS v3 auth sha AuthPass123 priv aes 128 PrivPass123 snmp-server enable traps snmp-server host 203.0.113.10 traps version 2c public flow exporter EXP1 destination 203.0.113.20 transport udp 2055 export-protocol netflow-v9 flow monitor MON1 exporter EXP1 record netflow ipv4 original-input
AnswerA
solution
! R1
configure terminal
snmp-server community public RO
snmp-server group ADMINS v3 priv
snmp-server user admin ADMINS v3 auth sha AuthPass123 priv aes 128 PrivPass123
snmp-server enable traps
snmp-server host 203.0.113.10 traps version 2c public
flow exporter EXP1
destination 203.0.113.20
transport udp 2055
export-protocol netflow-v9
exit
flow monitor MON1
exporter EXP1
record netflow ipv4 original-input
exit
interface GigabitEthernet0/0
ip flow monitor MON1 input
end

Why this answer

SNMPv3 needs a group (snmp-server group ADMINS v3 priv) and a user in that group with auth sha and priv aes 128, and passwords of sufficient length. Traps require snmp-server enable traps and an snmp-server host for 203.0.113.10 (version 2c with the community). On an ISR 4321, NetFlow v9 export uses Flexible NetFlow: a flow exporter with destination 203.0.113.20, transport udp 2055 and export-protocol netflow-v9, a flow monitor using the exporter and a record, and the monitor applied to the interface with ip flow monitor MON1 input.

Without applying the monitor to the interface, no flows are exported.

Exam trap

Forgetting to include a group name and the 'v3' keyword in the 'snmp-server user' command is a common syntax error that will cause the configuration to be rejected on real devices.

Why the other options are wrong

B

Wrong export port and protocol.

C

Wrong SNMPv3 algorithms.

D

Monitor not applied to the interface.

9
MCQhard

An administrator sees high interface utilization through SNMP graphs but wants to identify which conversations are responsible. Which addition best closes that visibility gap?

A.NetFlow
B.Another DHCP scope
C.A new STP priority
D.A larger OSPF metric
AnswerA

NetFlow (and similar flow export technologies) captures metadata for each IP conversation traversing the interface, including source/destination addresses, L4 ports, and byte counts. This allows the administrator to aggregate by host, application, or TCP/UDP port and immediately identify the top talkers driving the interface to high utilization. Unlike SNMP counters that show only aggregate usage, NetFlow correlates the utilization to specific flows.

Why this answer

NetFlow provides conversation-level visibility into which hosts and applications are consuming bandwidth, closing the gap left by SNMP's interface totals. A new DHCP scope assigns IP addresses but offers no traffic insight. An STP priority manages loop-free topology and does not affect monitoring.

A larger OSPF metric influences routing path selection, not traffic analysis.

Exam trap

Avoid assuming all network monitoring tools provide the same level of detail. Understand the specific capabilities of each tool.

Why the other options are wrong

B

A DHCP scope handles address assignment and has no role in traffic conversation visibility.

C

An STP priority manages spanning-tree topology and does not provide bandwidth usage details.

D

A larger OSPF metric affects routing path selection but does not reveal which conversations are using bandwidth.

10
MCQhard

A network administrator wants to receive an immediate notification from a device when a significant event occurs, rather than polling the device repeatedly. Which SNMP feature is most associated with that requirement?

A.SNMP traps
B.Syslog severity 7
C.DHCP relay
D.NetFlow exporters
AnswerA

An SNMP trap is an unsolicited, event-driven message that a managed device sends directly to a network management station (NMS) to alert it of a fault, status change, or security incident. Unlike SNMP polling, which requires the NMS to request information, traps are pushed immediately when the triggering event occurs, enabling real-time notification without waiting for a poll cycle. This is exactly the behavior described by the requirement to receive an immediate notification from a device.

Why this answer

SNMP traps are the correct answer because they are an SNMP feature that sends unsolicited, event-driven notifications from the device to the management system when a significant event occurs, eliminating the need for polling. Option B (syslog severity 7) is incorrect because syslog is a separate protocol for logging; while syslog messages are also sent unsolicited, the question specifically asks for an SNMP feature. Options C (DHCP relay) and D (NetFlow exporters) are unrelated to immediate event notifications: DHCP relay forwards broadcast requests, and NetFlow exports traffic flow data for analysis.

Exam trap

A frequent exam trap is mistaking syslog messages or NetFlow exporters as the mechanism for immediate event notifications in SNMP. Syslog severity levels, such as severity 7, relate to logging detail but do not trigger unsolicited alerts to management stations. Similarly, NetFlow exporters focus on traffic flow analysis rather than event-driven notifications.

Candidates may also confuse DHCP relay, which is unrelated to SNMP, with notification features. The key is to remember that only SNMP traps send unsolicited, immediate notifications, distinguishing them from polling or other monitoring tools.

Why the other options are wrong

B

Syslog severity 7 refers to debug-level logging detail but does not trigger unsolicited alerts; syslog messages require polling or log monitoring and are not part of SNMP's event-driven notification.

C

DHCP relay is a mechanism to forward DHCP requests across networks and has no role in SNMP or event-driven notifications, making it irrelevant to the question.

D

NetFlow exporters provide detailed traffic flow information for analysis but do not send immediate event notifications; they are unrelated to SNMP traps or polling mechanisms.

11
MCQmedium

A security policy requires SNMP management traffic to be both authenticated and encrypted. Which configuration meets this requirement?

A.SNMPv2c with a long community string
B.SNMPv3 with noAuthNoPriv
C.SNMPv3 with authNoPriv
D.SNMPv3 with authPriv
AnswerD

Provides authentication and encryption.

Why this answer

Only SNMPv3 with the authPriv security level provides both authentication and encryption (privacy). SNMPv1 and v2c send community strings in clear text, and authNoPriv authenticates but does not encrypt.

Why the other options are wrong

A

Length does not add encryption.

B

No authentication or encryption.

C

Traffic is not encrypted.

12
MCQeasy

A network management station periodically asks a router for the current value of an interface counter. Which SNMP operation does the station use?

A.Get-Request
B.Set-Request
C.Trap
D.Inform-Response
AnswerA

Reads object values from the agent.

Why this answer

A Get-Request retrieves the value of one or more objects from the agent's MIB. Polling relies on Get-type operations initiated by the manager.

Why the other options are wrong

B

The station only needs to read the counter.

C

It is not sent by the manager.

D

It is not used to read counters.

13
MCQhard

An administrator configures a router as shown in the exhibit. An NMS at 192.168.1.60 sends an SNMP Set-Request using the community NetOps and it is ignored. What is the cause?

A.ACL 10 permits only host 192.168.1.50, so requests from 192.168.1.60 are denied.
B.The RW keyword allows only read operations.
C.Set-Requests are supported only in SNMPv3.
D.The router needs snmp-server enable traps before it accepts Set-Requests.
AnswerA

The ACL restricts allowed sources.

Why this answer

The community NetOps is bound to ACL 10, which permits only 192.168.1.50. Requests from 192.168.1.60 match the implicit deny and are ignored. The RW keyword is correct for Set operations, and v2c does not require v3 for this to work.

Why the other options are wrong

B

RW is read-write.

C

Set works with RW communities.

D

Traps are agent-initiated notifications.

14
MCQmedium

Which port-security violation mode drops frames from unauthorized MAC addresses but keeps the interface up and does not send an SNMP trap or syslog message?

A.protect
B.restrict
C.shutdown
D.shutdown vlan
AnswerA

Protect is the quietest switchport port-security violation mode: when the port's MAC address table is full, it silently drops frames from new, unknown MAC addresses while continuing to forward traffic for already-learned addresses. No SNMP trap or syslog message is generated, and the port remains up and operational, making the violation virtually invisible to network monitoring. This is the correct answer because the question asks which mode drops frames without any further action or notification.

Why this answer

Protect silently drops frames from unauthorized sources while leaving the interface up. Restrict also drops frames but increments the violation counter and can generate notifications.

Exam trap

Be careful not to confuse Protect with Restrict, as both drop frames but only Restrict sends notifications.

Why the other options are wrong

B

The 'restrict' mode allows frames from unauthorized MAC addresses to be dropped while sending SNMP traps and syslog messages, which contradicts the requirement of keeping the interface up without notifications.

C

The 'shutdown' mode disables the interface when a violation occurs, which is contrary to the requirement of keeping the interface up. It also does not align with the need to drop frames without sending SNMP traps or syslog messages.

D

Shutdown vlan err-disables the offending VLAN on the port and generates log messages, so it is not a silent drop-only mode. Only protect drops violating frames without notification.

15
PBQhard

You are connected to R1. R1 must send SNMPv2c traps (community public) to the management server at 203.0.113.10, provide SNMPv3 access for user admin in group MyGroup (SHA authentication and AES-128 privacy, password cisco123 for both), and export NetFlow records to the collector at 203.0.113.20 using NetFlow version 9. The exhibit shows what is currently configured. Apply the missing configuration.

Network Topology
G0/0203.0.113.1/24203.0.113.10linkR1Management Server

Hints

  • •Use the 'snmp-server host' command to specify the trap destination and community.
  • •For SNMPv3, you must first create a group with the appropriate security level before creating the user.
  • •NetFlow export version is configured globally with 'ip flow-export version'.
A.snmp-server enable traps snmp-server host 203.0.113.10 traps version 2c public snmp-server group MyGroup v3 priv snmp-server user admin MyGroup v3 auth sha cisco123 priv aes 128 cisco123 ip flow-export version 9
B.snmp-server host 203.0.113.10 traps version 2c public snmp-server group MyGroup v3 priv snmp-server user admin MyGroup v3 auth sha cisco123 priv aes 128 cisco123 ip flow-export version 9
C.snmp-server enable traps snmp-server host 203.0.113.10 traps version 2c public ip flow-export version 9
D.snmp-server enable traps snmp-server host 203.0.113.10 traps version 2c public snmp-server group MyGroup v3 priv snmp-server user admin MyGroup v3 auth sha cisco123 priv aes 128 cisco123 ip flow-export destination 203.0.113.20 2055
AnswerA
solution
! R1
snmp-server enable traps
snmp-server host 203.0.113.10 traps version 2c public
snmp-server group MyGroup v3 priv
snmp-server user admin MyGroup v3 auth sha cisco123 priv aes 128 cisco123
ip flow-export version 9

Why this answer

Traps require both a trap destination (snmp-server host ... traps version 2c public) and the global snmp-server enable traps command. SNMPv3 needs a group at the required security level (priv) and a user bound to it with SHA authentication and AES-128 privacy. NetFlow export already has a destination but runs the default version 1, so ip flow-export version 9 must be added.

Exam trap

Watch out for the SNMPv3 group keyword: 'priv' is required when using encryption (AES 128), not just 'auth'. Also, remember that the 'snmp-server user' command requires a group name. For NetFlow, the version is set with 'ip flow-export version 9', not 'ip flow-export destination'.

How to eliminate wrong answers

Option A is correct because it includes all required commands with proper syntax. Option B is wrong because the group uses 'auth' instead of 'priv', which is needed for AES encryption. Option C is wrong because it omits the group configuration entirely.

Option D is wrong because it uses 'ip flow-export destination' instead of 'ip flow-export version 9'.

16
MCQmedium

A team polls devices every five minutes but wants to learn about link failures sooner. What advantage do SNMP traps provide over polling alone?

A.The NMS is notified when the event occurs instead of waiting for the next poll.
B.Traps guarantee delivery through acknowledgments.
C.Traps encrypt all SNMPv2c traffic.
D.Traps let the NMS change device configuration.
AnswerA

Event-driven notification.

Why this answer

Traps are sent by the agent when an event occurs, so the NMS learns of it immediately rather than at the next poll interval. Polling remains useful for trend data.

Why the other options are wrong

B

Informs are the acknowledged type.

C

Encryption needs SNMPv3.

D

Traps are notifications only.

17
Multi-Selectmedium

An engineer wants a router to send SNMPv2c traps to the NMS at 10.1.1.9 using the community string TRAPS. Which two commands are required? (Choose two.)

Select 2 answers
A.snmp-server host 10.1.1.9 version 2c TRAPS
B.snmp-server enable traps
C.logging host 10.1.1.9
D.snmp-server contact 10.1.1.9
E.snmp-server community TRAPS RW
AnswersA, B

Defines the trap receiver.

Why this answer

snmp-server host 10.1.1.9 version 2c TRAPS defines the destination, version and community. snmp-server enable traps turns on the notification types that are sent.

Why the other options are wrong

C

Syslog is not SNMP.

D

It does not define a receiver.

E

It does not send traps and grants write access.

18
MCQmedium

An engineer configures an SNMPv3 user with authentication but no encryption. Which security level is in use?

A.noAuthNoPriv
B.authNoPriv
C.authPriv
D.community
AnswerB

Authentication without privacy.

Why this answer

authNoPriv provides authentication (HMAC-SHA or MD5) but no encryption, so message contents can be read in transit. authPriv adds encryption, and noAuthNoPriv uses only a username match.

Why the other options are wrong

A

Authentication is configured here.

C

No encryption is configured.

D

Not a v3 security level.

19
MCQeasy

An interface on a switch goes down and the switch immediately sends an unsolicited message to the NMS without being polled. What is this SNMP message called?

A.Get-Request
B.Set-Request
C.GetNext-Request
D.Trap
AnswerD

An unsolicited agent notification.

Why this answer

A trap is an unsolicited notification an SNMP agent sends to the manager when an event occurs. It is sent to UDP port 162 on the manager.

Why the other options are wrong

A

The NMS did not poll.

B

The switch is notifying, not being configured.

C

The message here is agent-initiated.

20
PBQhard

You are connected to R1. Configure SNMP v2c with a read-only community string 'monitorRO' and a read-write community string 'controlRW', and enable SNMP traps for link status to the management server at 203.0.113.100. Additionally, configure NetFlow to export version 9 flow records to the same server on UDP port 2055, and ensure that only traffic from the 10.10.10.0/24 network is monitored. Finally, verify your configurations with the appropriate show commands.

Network Topology
G0/010.0.0.1/30G0/010.0.0.2/30linkG0/110.10.10.1/2410.10.10.0/24linkR1R2Internal Network

Hints

  • •Remember to specify the SNMP version when configuring the trap receiver host.
  • •NetFlow version 9 must be explicitly configured; otherwise, version 5 is used by default.
  • •Apply the flow monitor to the interface that connects to the network you want to monitor (G0/1).
A.Configure SNMP community strings, enable link-status traps, set trap destination, configure NetFlow export version 9, and apply flow monitor to interface(s) carrying 10.10.10.0/24 traffic.
B.Configure SNMP community strings, enable link-status traps, set trap destination, and configure NetFlow export version 5. Apply flow monitor to all interfaces.
C.Configure SNMP community strings, enable all SNMP traps, set trap destination, and configure NetFlow export version 9. Apply flow monitor to interface with IP 10.10.10.0/24.
D.Configure SNMP community strings, enable link-status traps, set trap destination, and configure NetFlow export version 9. Do not apply any flow monitor; NetFlow automatically monitors all traffic.
AnswerA
solution
! R1
snmp-server community monitorRO RO
snmp-server community controlRW RW
snmp-server enable traps snmp linkdown linkup
snmp-server host 203.0.113.100 version 2c monitorRO
flow exporter EXPORTER-TO-SERVER
destination 203.0.113.100
transport udp 2055
source Loopback0
export-protocol netflow-v9
exit
flow monitor MONITOR-10NET
record netflow ipv4 original-input
exporter EXPORTER-TO-SERVER
exit
interface GigabitEthernet0/1
ip flow monitor MONITOR-10NET input
end

Why this answer

SNMP is configured with the two communities, link up/down traps, and the trap host 203.0.113.100 using version 2c. NetFlow version 9 is configured with Flexible NetFlow: an exporter (destination 203.0.113.100, UDP 2055, export-protocol netflow-v9), a flow monitor using a predefined record, and the monitor applied inbound on G0/1, the interface where traffic from 10.10.10.0/24 enters R1. Verify with show snmp, show flow exporter and show flow monitor MONITOR-10NET cache.

Exam trap

Common mistakes include mixing legacy and Flexible NetFlow commands (e.g., using the global `ip flow-export version` instead of setting it under the flow exporter), forgetting to apply the flow monitor to an interface, and enabling all SNMP traps rather than only link-status traps.

Why the other options are wrong

B

The question explicitly requires NetFlow version 9, and traffic monitoring must be limited to the 10.10.10.0/24 network.

C

Enabling all traps is unnecessary and may cause unwanted overhead; the flow monitor must be applied to the correct interface(s) based on traffic flow, not the network address.

D

NetFlow requires a flow monitor to be applied to an interface to capture traffic; it does not automatically monitor all traffic.

21
MCQhard

A monitoring system already collects Syslog and SNMP data. The network team now wants visibility into which applications or host conversations are driving link utilization. What is the strongest addition?

A.NetFlow
B.Another SSID
D.A larger wildcard mask
AnswerA

NetFlow is correct because it captures metadata about traffic flows — including source/destination IPs, ports, and protocol — and exports that data to a collector for analysis. This gives the monitoring system detailed, flow-level visibility into who is talking to whom and how much bandwidth each conversation uses, which syslog and SNMP alone cannot provide. NetFlow complements existing syslog and SNMP data by focusing on network traffic patterns rather than device logs or interface counters.

Why this answer

The strongest addition is NetFlow because it provides traffic-flow visibility. In practical terms, Syslog and SNMP are useful, but they do not directly answer detailed conversation-level questions such as which hosts, protocols, or flows are consuming the most bandwidth. NetFlow is designed to answer exactly that kind of question.

This is about choosing the right operational tool for the visibility gap.

Exam trap

A frequent exam trap is selecting options like PortFast or adding another SSID, which are unrelated to traffic flow monitoring. PortFast is an STP feature that speeds up port transitions but does not provide any insight into bandwidth usage or application-level traffic. Similarly, adding another SSID only affects wireless network segmentation and does not offer visibility into which hosts or applications consume bandwidth.

Another trap is thinking that changing ACL wildcard masks can help analyze traffic flows, but ACLs only filter traffic and do not provide analytics. Recognizing that only NetFlow delivers detailed flow-level data prevents these common mistakes.

Why the other options are wrong

B

Adding another SSID is incorrect because it only creates a new wireless network segment and does not provide any traffic flow or bandwidth usage information. It does not help identify which applications or hosts are using the link.

C

PortFast is an STP feature that speeds up port transitions on edge ports but does not monitor or analyze traffic flows. It has no relevance to identifying bandwidth usage or application-level visibility.

D

Using a larger wildcard mask in ACLs affects traffic filtering rules but does not provide analytics or visibility into traffic flows. ACLs do not report on bandwidth consumption or application usage.

22
MCQmedium

Which SNMP element is the structured, tree-organized collection of managed objects that a device exposes to the network management station?

A.Community string
B.Object identifier (OID)
C.Management Information Base (MIB)
D.Trap receiver
AnswerC

The hierarchical database of managed objects.

Why this answer

The Management Information Base (MIB) is the hierarchical database of managed objects. Each object in it is identified by an OID.

Why the other options are wrong

A

It is for access control, not a data store.

B

It identifies one object, not the collection.

D

It is a host, not a database.

23
PBQhard

You are connected to R1 via the console. SNMP v2c community strings (public RO, private RW) are already configured. The network has a management server at 10.1.1.100 and a NetFlow collector at 10.1.1.200. Configure SNMP traps to the management server for link status changes. Also configure NetFlow on interface GigabitEthernet0/0 to export version 9 to the collector, with a source interface of Loopback0 (10.255.255.1/32).

Network Topology
G0/0G0/010.1.1.10010.1.1.200R210.0.0.1/30R1MGMT_ServerNMS_Collector

Hints

  • •SNMP traps require both a host command and enabling specific trap types.
  • •NetFlow export needs destination, version, and source interface, plus flow ingress on the interface.
  • •Use 'show running-config | section snmp|flow' to verify your changes.
A.snmp-server host 10.1.1.100 version 2c public snmp-server enable traps snmp linkdown linkup ip flow-export destination 10.1.1.200 2055 ip flow-export version 9 ip flow-export source Loopback0 interface GigabitEthernet0/0 ip flow ingress
B.snmp-server host 10.1.1.200 version 2c private snmp-server enable traps ip flow-export destination 10.1.1.100 2055 version 9 ip flow-export source Loopback0 interface GigabitEthernet0/0 ip flow egress
C.snmp-server host 10.1.1.100 version 2c private snmp-server enable traps ip flow-export destination 10.1.1.200 2055 version 9 ip flow-export source Loopback0 interface GigabitEthernet0/0 ip flow ingress
D.snmp-server host 10.1.1.100 version 2c public snmp-server enable traps snmp linkdown linkup ip flow-export destination 10.1.1.200 2055 version 5 ip flow-export source Loopback0 interface GigabitEthernet0/0 ip flow ingress
AnswerA
solution
! R1
snmp-server host 10.1.1.100 version 2c public
snmp-server enable traps snmp linkdown linkup
ip flow-export destination 10.1.1.200 2055
ip flow-export version 9
ip flow-export source Loopback0
interface GigabitEthernet0/0
ip flow ingress

Why this answer

The current configuration has SNMP community strings but lacks trap destinations and NetFlow export. To fix, you must configure snmp-server host 10.1.1.100 version 2c public to send traps, and snmp-server enable traps snmp linkdown linkup is required to send link status changes. For NetFlow, you need ip flow-export destination 10.1.1.200 2055 and then ip flow-export version 9 to set the export version.

Also configure ip flow-export source Loopback0 and apply ip flow ingress on GigabitEthernet0/0. Verification commands confirm the settings.

Exam trap

Pay close attention to the IP addresses: the management server (10.1.1.100) is for SNMP traps, and the collector (10.1.1.200) is for NetFlow. Also, remember that SNMP traps use the read-only community, and NetFlow version must match the requirement (version 9).

Why the other options are wrong

B

The specific factual error: The SNMP trap destination and NetFlow export destination are swapped, and the flow direction is egress instead of ingress.

C

Enables every trap type instead of linkdown/linkup, and uses invalid NetFlow export syntax.

D

The specific factual error: NetFlow export version is set to 5, but the requirement is version 9.

24
MCQhard

A network administrator notices that syslog messages from a core router are arriving at the syslog server with timestamps that are hours behind other devices. The router’s NetFlow exports also show incorrect start and end times for flows, making traffic analysis unreliable. The administrator verifies that all router interfaces are up and that the SNMP community strings on the router match the NMS.

A.The logging trap level is set to informational, so only high-severity messages are sent with correct timestamps.
B.The router’s NTP client is configured with an incorrect authentication key.
C.The SNMP v3 user’s privacy password is incorrect, causing the NMS to reject syslog traps.
D.The IP flow cache timeout is set too low, causing NetFlow timestamps to appear skewed.
AnswerB

NTP can use authentication keys to verify server identity. If the client key does not match the server’s key, the router will not trust the time updates and will fail to synchronize. This leaves the router’s clock uncorrected, causing incorrect timestamps in syslog and NetFlow records.

Why this answer

The router's timestamps are incorrect for both syslog messages and NetFlow exports, which points to a system-wide time synchronization issue. NTP (Network Time Protocol) is responsible for maintaining accurate time on network devices, and if the NTP client is configured with an incorrect authentication key, it will fail to synchronize with the NTP server, causing the router's clock to drift. This explains why all time-stamped data (syslog and NetFlow) is consistently behind.

Exam trap

Cisco often tests the distinction between time synchronization issues (NTP) and logging/SNMP configuration issues, so candidates may incorrectly attribute timestamp problems to syslog or SNMP settings rather than the underlying system clock.

Why the other options are wrong

A

Logging trap level controls which severity messages are forwarded, not the accuracy of the timestamps.

C

SNMP v3 misconfiguration impacts SNMP traps, not syslog messages, which are sent independently via a different transport.

D

Cache timeout affects flow export frequency, not the accuracy of the timestamps inside the flow data.

Ready to test yourself?

Try a timed practice session using only Snmp questions.