CCNA Practice Exam 62 — 20 Questions

Question 1

You are connected to R1. Use RESTCONF to retrieve all operational interface statistics from the ietf-interfaces YANG module, then modify the description of GigabitEthernet0/1 to 'Link to R2 via RESTCONF' using a PATCH request. The device is reachable at 203.0.113.1 with port 443, username 'admin', password 'cisco123'. Identify the error that would occur if you used a PATCH with Content-Type: application/json instead of application/yang-data+json.

Accepted Answer

The server returns a 415 Unsupported Media Type error because RESTCONF requires the Content-Type header to be application/yang-data+json.. The correct base URI for RESTCONF is https://203.0.113.1/restconf. To retrieve operational interface statistics, use GET with the path /data/ietf-interfaces:interfaces-state/interface. For the PATCH to modify the description, the URI must target /data/ietf-interfaces:interfaces/interface=GigabitEthernet0/1 with a JSON payload containing the 'description' leaf. The required Content-Type and Accept headers must be 'application/yang-data+json'. Using 'application/json' will result in a 415 Unsupported Media Type error because RESTCONF requires the specific YANG media type.

Answer

The server returns a 400 Bad Request error because the JSON payload is malformed when using application/json.

Answer

The server returns a 404 Not Found error because the URI is incorrect when using application/json.

Answer

The server returns a 204 No Content response but ignores the description change because application/json is not supported.

Question 2

You are connected to the multilayer switch MLS1 in a branch network. The DHCP server on router R1 is supposed to serve the 192.168.20.0/24 VLAN 20, but clients in VLAN 20 are not receiving IP addresses. Additionally, a rogue DHCP server has been detected on VLAN 20. Configure MLS1 to enable DHCP snooping on VLAN 20, set the trust state on the uplink port to R1, and limit the rate of DHCP packets on access ports. Then, on R1, correct the DHCP configuration so that the pool for VLAN 20 uses the correct default-router (192.168.20.1) and DNS server (8.8.8.8), and ensure that the excluded-address range is not too large (exclude only the first 10 addresses). Verify the solution.

Accepted Answer

On MLS1: ip dhcp snooping, ip dhcp snooping vlan 20, interface Gig0/0 ip dhcp snooping trust, interface Gig0/1 ip dhcp snooping limit rate 10. On R1: ip dhcp excluded-address 192.168.20.1 192.168.20.10, ip dhcp pool VLAN20 network 192.168.20.0 255.255.255.0 default-router 192.168.20.1 dns-server 8.8.8.8. The problem had three faults: First, the DHCP pool on R1 had a wrong default-router (192.168.10.1 instead of 192.168.20.1) and an incorrect DNS server (4.4.4.4 instead of 8.8.8.8). Second, the excluded-address range was too large (excluding all addresses from .1 to .254 effectively blocked all dynamic assignments; corrected to exclude only .1 through .10). Third, DHCP snooping was disabled on MLS1, allowing a rogue DHCP server. To enable DHCP snooping, both the global `ip dhcp snooping` command and the VLAN-specific `ip dhcp snooping vlan 20` command are required. With snooping enabled, the uplink port Gig0/0 was set as trusted and the access port Gig0/1 was configured with rate limiting to prevent DHCP starvation attacks.

Answer

On MLS1: ip dhcp snooping vlan 20, interface Gig0/0 ip dhcp snooping trust, interface Gig0/1 ip dhcp snooping limit rate 10. On R1: ip dhcp excluded-address 192.168.20.1 192.168.20.254, ip dhcp pool VLAN20 network 192.168.20.0 255.255.255.0 default-router 192.168.20.1 dns-server 8.8.8.8

Answer

On MLS1: ip dhcp snooping vlan 20, interface Gig0/0 ip dhcp snooping trust, interface Gig0/1 ip dhcp snooping limit rate 10. On R1: ip dhcp excluded-address 192.168.20.1 192.168.20.10, ip dhcp pool VLAN20 network 192.168.20.0 255.255.255.0 default-router 192.168.10.1 dns-server 4.4.4.4

Answer

On MLS1: ip dhcp snooping vlan 20, interface Gig0/0 ip dhcp snooping trust, interface Gig0/1 ip dhcp snooping limit rate 10. On R1: ip dhcp excluded-address 192.168.20.1 192.168.20.10, ip dhcp pool VLAN20 network 192.168.20.0 255.255.255.0 default-router 192.168.20.1 dns-server 8.8.8.8, but no ip dhcp snooping enabled globally on MLS1

Question 3

You are connected to R1 (192.168.1.1). Using RESTCONF, you need to retrieve the current operational status of GigabitEthernet0/0 using the ietf-interfaces YANG module, then change its description to 'WAN Link to R2' via a PATCH request. The device is reachable via HTTPS on port 443, with credentials admin/admin. Identify the correct base URI, YANG path, HTTP headers, and interpret the JSON response. Also, diagnose the error when an incorrect Content-Type or YANG path is used.

Accepted Answer

Base URI: https://192.168.1.1/restconf, YANG path: /data/ietf-interfaces:interfaces/interface=GigabitEthernet0/0, Accept: application/yang-data+json, PATCH body: {"ietf-interfaces:description": "WAN Link to R2"}. The correct RESTCONF base URI is https://192.168.1.1/restconf. For the ietf-interfaces module, the YANG path for an interface is /data/ietf-interfaces:interfaces/interface=GigabitEthernet0/0. The required Accept header is application/yang-data+json. A PATCH request to change just the description must include the module prefix in the JSON key: {"ietf-interfaces:description": "WAN Link to R2"}. Using application/json for Content-Type returns a 415 Unsupported Media Type error. Using the wrong YANG path (e.g., /data/ietf-interfaces:interfaces-state) returns a 404 Not Found because that path is for operational state, not configurable data.

Answer

Base URI: https://192.168.1.1/restconf, YANG path: /data/ietf-interfaces:interfaces-state/interface=GigabitEthernet0/0, Accept: application/yang-data+json, PATCH body: {"description": "WAN Link to R2"}

Answer

Base URI: https://192.168.1.1/restconf, YANG path: /data/ietf-interfaces:interfaces/interface=GigabitEthernet0/0, Accept: application/json, PATCH body: {"description": "WAN Link to R2"}

Answer

Base URI: https://192.168.1.1/restconf, YANG path: /data/ietf-interfaces:interfaces/interface=GigabitEthernet0/0, Accept: application/yang-data+json, PATCH body: {"description": "WAN Link to R2"}

Question 4

You are connected to R1. Using RESTCONF, you need to retrieve the current IP address of interface GigabitEthernet0/0 using the ietf-interfaces YANG model, then change it to 192.0.2.1/24 using a PATCH request. The device is reachable at 10.1.1.1 with port 443 and credentials admin/cisco. Identify the correct URIs and required HTTP headers, and explain why a GET with Accept: application/json would fail.

Accepted Answer

GET https://10.1.1.1:443/restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet0/0 with Accept: application/yang-data+json; PATCH same URI with Content-Type: application/yang-data+json and body {"ietf-interfaces:interface":{"name":"GigabitEthernet0/0","ipv4":{"address":[{"ip":"192.0.2.1","netmask":"255.255.255.0"}]}}}. The correct base URI for RESTCONF is /restconf/data. The YANG path uses /ietf-interfaces:interfaces/interface=GigabitEthernet0/0. The Accept header must specify application/yang-data+json; generic application/json causes a 406 error. For PATCH, the same URI is used with Content-Type: application/yang-data+json. Crucially, the PATCH body must contain the key leaf 'name' ('GigabitEthernet0/0') inside the container to identify the list instance per RFC 8040; omitting it can cause failure. A wrong YANG path like Cisco-IOS-XE-native would yield 404.

Answer

GET https://10.1.1.1/restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet0/0 with Accept: application/json; PATCH same URI with Content-Type: application/json and body {"interface":{"ip":"192.0.2.1","mask":"255.255.255.0"}}

Answer

GET https://10.1.1.1:443/restconf/data/Cisco-IOS-XE-native:native/interface/GigabitEthernet=0/0/ip/address with Accept: application/yang-data+json; PATCH same URI with Content-Type: application/yang-data+json and body {"address":{"primary":{"address":"192.0.2.1","mask":"255.255.255.0"}}}

Answer

GET https://10.1.1.1:443/restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet0/0 with Accept: application/xml; PATCH same URI with Content-Type: application/xml and body

192.0.2.1255.255.255.0

Question 5

You are connected to R1, a Cisco ISR 4321 running IOS-XE. Configure SNMPv2c with a read-only community string 'public' and SNMPv3 with user 'admin' using SHA authentication and AES encryption. Ensure SNMP traps are sent to the management server at 203.0.113.10. Additionally, configure NetFlow export to destination 203.0.113.20 on UDP port 2055 using version 9. Verify your configuration with appropriate show commands. The current running-config is incomplete; you must add the missing commands.

Accepted Answer

snmp-server community public ro
snmp-server user admin snmp-group v3 auth sha cisco priv aes 128 cisco
snmp-server host 203.0.113.10 traps version 2c public
ip flow-export destination 203.0.113.20 2055
ip flow-export version 9. The initial config has only a basic SNMPv2c community string. To meet requirements: enable SNMPv3 with a user 'admin' using SHA authentication and AES 128-bit encryption. The correct command requires a group name and the 'v3' keyword, e.g., 'snmp-server user admin snmp-group v3 auth sha cisco priv aes 128 cisco'. Configure SNMP trap destination with 'snmp-server host 203.0.113.10 traps version 2c public'. For NetFlow, use 'ip flow-export destination 203.0.113.20 2055' and 'ip flow-export version 9'. Verify with 'show snmp' and 'show ip cache flow'. Option B incorrectly uses version 3 traps with a community string; version 3 requires a security name. Option C uses insecure MD5/DES56 instead of SHA/AES. Option D uses NetFlow version 5 instead of version 9.

Answer

snmp-server community public ro
snmp-server user admin snmp-group v3 auth sha cisco priv aes 128 cisco
snmp-server host 203.0.113.10 traps version 3 auth public
ip flow-export destination 203.0.113.20 2055
ip flow-export version 9

Answer

snmp-server community public ro
snmp-server user admin snmp-group v3 auth md5 cisco priv des56 cisco
snmp-server host 203.0.113.10 traps version 2c public
ip flow-export destination 203.0.113.20 2055
ip flow-export version 9

Answer

snmp-server community public ro
snmp-server user admin snmp-group v3 auth sha cisco priv aes 128 cisco
snmp-server host 203.0.113.10 traps version 2c public
ip flow-export destination 203.0.113.20 2055
ip flow-export version 5

Question 6

You are connected to R1 (10.0.0.1/30). You need to use RESTCONF to verify the current administrative status of interface GigabitEthernet0/1 on R1, then change it to 'down'. The YANG data model is ietf-interfaces, and the base URI is https://10.0.0.1/restconf. Provide the correct GET and PATCH request URIs with appropriate HTTP headers. Also identify what error would occur if you used 'application/xml' as the Accept header or if you used the path 'Cisco-IOS-XE-native:native/interface/GigabitEthernet' instead of the correct ietf-interfaces path.

Accepted Answer

GET https://10.0.0.1/restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet0/1 with Accept: application/yang-data+json; PATCH same URI with Content-Type: application/yang-data+json and body {"ietf-interfaces:interface": {"enabled": false}}; using Accept: application/xml gives 406 Not Acceptable; using Cisco-IOS-XE-native path gives 404 or incorrect data.. The correct GET request URI is: GET https://10.0.0.1/restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet0/1 with Accept: application/yang-data+json. The correct PATCH request URI is the same, with Content-Type: application/yang-data+json and a JSON body {"ietf-interfaces:interface": {"enabled": false}}. Using Accept: application/xml would result in a 406 Not Acceptable error because the server only supports yang-data+json. Using the Cisco-IOS-XE-native path would return a 404 or incorrect data because the operational state of the interface (admin status) is modeled under ietf-interfaces, not under the native YANG model which is used for configuration only.

Answer

GET https://10.0.0.1/restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet0/1 with Accept: application/xml; PATCH same URI with Content-Type: application/xml and body false; using Accept: application/xml is fine; using Cisco-IOS-XE-native path gives same data.

Answer

GET https://10.0.0.1/restconf/data/Cisco-IOS-XE-native:native/interface/GigabitEthernet0/1 with Accept: application/yang-data+json; PATCH same URI with Content-Type: application/yang-data+json and body {"Cisco-IOS-XE-native:interface": {"enabled": false}}; using Accept: application/xml gives 406; using ietf-interfaces path gives 404.

Answer

GET https://10.0.0.1/restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet0/1 with Accept: application/json; PATCH same URI with Content-Type: application/json and body {"interface": {"enabled": false}}; using Accept: application/xml gives 406; using Cisco-IOS-XE-native path gives 404.

Question 7

Which option performs the RESTCONF operations correctly?

Accepted Answer

GET /restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet0/0 with Accept: application/yang-data+json; then PATCH same URI with Content-Type: application/yang-data+json and body {"ietf-interfaces:interface":{"duplex":"full"}}; expect 204 No Content.. The correct base URI for RESTCONF is /restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet0/0. The Accept header must be application/yang-data+json. If the Content-Type header is incorrect (e.g., application/json), the router will return a 415 Unsupported Media Type error. Using the wrong YANG module path, such as Cisco-IOS-XE-native:interface/GigabitEthernet0/0, will result in a 404 Not Found because the data model does not match. After a successful GET, the PATCH request must include the same URI with Content-Type: application/yang-data+json and a JSON body specifying "duplex": "full". The response should be a 204 No Content if successful.

Answer

GET /restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet0/0 with Accept: application/json; then PATCH same URI with Content-Type: application/json and body {"duplex":"full"}; expect 204 No Content.

Answer

GET /restconf/data/Cisco-IOS-XE-native:interface/GigabitEthernet0/0 with Accept: application/yang-data+json; then PATCH same URI with Content-Type: application/yang-data+json and body {"Cisco-IOS-XE-native:interface":{"duplex":"full"}}; expect 204 No Content.

Answer

GET /restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet0/0 with Accept: application/yang-data+json; then PATCH same URI with Content-Type: application/yang-data+json and body {"duplex":"full"}; expect 200 OK.

Question 8

You are connected to R1 (198.51.100.1/24). Using RESTCONF, you need to retrieve the current operational status of GigabitEthernet0/0/0 via the ietf-interfaces YANG model, then update its description to 'WAN-Link-to-R2' using a PATCH request with the Cisco-IOS-XE-native YANG model. The candidate must identify the correct base URI, YANG module path, HTTP headers (Accept: application/yang-data+json), interpret the JSON response, and recognize the error that occurs when an incorrect Content-Type header or wrong YANG path is used.

Accepted Answer

GET request to /restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet0/0/0 with Accept: application/yang-data+json; PATCH request to /restconf/data/Cisco-IOS-XE-native:native/interface/GigabitEthernet=0/0/0 with Content-Type: application/yang-data+json and body {"Cisco-IOS-XE-native:description": "WAN-Link-to-R2"}. The GET request correctly uses the ietf-interfaces YANG path and Accept header to retrieve the interface operational data. The PATCH request fails because it attempts to modify 'description' under the ietf-interfaces model, which is read-only for operational data; the writable 'description' is under Cisco-IOS-XE-native:native/interface/GigabitEthernet. The correct PATCH URI targets the Cisco-IOS-XE-native YANG module path, and the Content-Type must be application/yang-data+json. The 400 error indicates a mismatch between the YANG path in the URI and the data payload.

Answer

GET request to /restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet0/0/0 with Accept: application/json; PATCH request to /restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet0/0/0 with Content-Type: application/yang-data+json and body {"description": "WAN-Link-to-R2"}

Answer

GET request to /restconf/data/Cisco-IOS-XE-native:native/interface/GigabitEthernet=0/0/0 with Accept: application/yang-data+json; PATCH request to /restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet0/0/0 with Content-Type: application/json and body {"description": "WAN-Link-to-R2"}

Answer

GET request to /restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet0/0/0 with Accept: application/yang-data+json; PATCH request to /restconf/data/Cisco-IOS-XE-native:native/interface/GigabitEthernet=0/0/0 with Content-Type: application/json and body {"Cisco-IOS-XE-native:description": "WAN-Link-to-R2"}

Question 9

Drag and drop the following steps into the correct order to configure an LACP EtherChannel on two Cisco switches.

Accepted Answer

Enter global configuration mode on both switches.. To configure LACP EtherChannel, start by entering global configuration mode on both switches. Then create the port-channel interface using 'interface port-channel' (optional but good practice). Finally, assign physical interfaces to the port-channel with LACP active mode using the 'channel-group' command, which handles both port binding and mode setting in one step. Verify with 'show etherchannel summary'.

Question 10

Drag and drop the following OSPFv2 neighbor state transitions and DR/BDR election steps into the correct order for a multi-access network with default priority values.

Accepted Answer

Down, Init, 2-Way (DR/BDR election), ExStart, Exchange, Loading, Full. The correct OSPF neighbor state progression on a multi-access network is: Down, Init, 2-Way (with DR/BDR election), ExStart (master/slave negotiation), Exchange (DBD exchange), Loading (link-state request and update), and Full. Each option missing the Loading state or placing it incorrectly fails to represent the complete adjacency process.

Answer

Down, Init, ExStart, Exchange, Loading, 2-Way (DR/BDR election), Full

Answer

Down, Init, 2-Way (DR/BDR election), Loading, Exchange, ExStart, Full

Answer

Down, Init, 2-Way (DR/BDR election), ExStart, Exchange, Full

Question 11

Drag and drop the following OSPFv2 DR/BDR election steps into the correct order for a multiaccess network where a new router is added after the DR and BDR have already been elected.

Accepted Answer

The new router sends Hello packets, becomes the new DR after election, and then forms adjacencies with all other routers.. When a new router joins a multiaccess network that already has DR/BDR, it goes through the ExStart state with both the DR and BDR, then forms full adjacencies with both, regardless of its OSPF priority. Options A, B, and C are incorrect because they either describe adjacencies with only the DR, or claim the new router becomes DR/BDR, which cannot happen when DR/BDR are already elected.

Answer

The new router sends Hello packets with priority 0, remains in 2-Way state with DR and BDR, then forms full adjacency with the DR.

Question 12

Drag and drop the following steps into the correct order to configure OSPFv3 for IPv6 on a Cisco router.

Accepted Answer

1. Enter global configuration mode. 2. Create the OSPFv3 process and assign a process ID. 3. Configure a router ID. 4. Enter interface configuration mode. 5. Enable OSPFv3 on the interface.. After entering global config, create the OSPFv3 process, set a router ID, then enable OSPFv3 on the desired interfaces under interface configuration.

Answer

1. Enter global configuration mode. 2. Enter interface configuration mode. 3. Enable OSPFv3 on the interface. 4. Create the OSPFv3 process and assign a process ID. 5. Configure a router ID.

Answer

1. Enter global configuration mode. 2. Create the OSPFv3 process and assign a process ID. 3. Enter interface configuration mode. 4. Enable OSPFv3 on the interface. 5. Configure a router ID.

Answer

1. Enter global configuration mode. 2. Configure a router ID. 3. Enter interface configuration mode. 4. Enable OSPFv3 on the interface. 5. Create the OSPFv3 process and assign a process ID.

Question 13

You are connected to R1, a Cisco IOS-XE router that provides connectivity for the 192.168.10.0/24 network. The network operations team uses a Python script with netmiko to push configuration changes. However, the script fails to connect to R1. You need to verify the SSH configuration on R1.

Accepted Answer

The VTY lines are configured for telnet only; SSH requires 'transport input ssh'.. The VTY lines are configured for telnet only. SSH requires 'transport input ssh' (or 'transport input all'). Additionally, the SSH server may not be enabled if the crypto key is missing or the ip ssh command is not present. The commands show that transport input is telnet, so the script cannot connect via SSH. Changing to 'transport input ssh' resolves the issue.

Answer

The SSH server is not enabled because the crypto key is missing or 'ip ssh' is not configured.

Answer

The SSH version is set to version 1, which is not supported by the Python script.

Answer

The domain name is not configured, which is required for SSH key generation.

Question 14

Drag and drop the following steps into the correct order to configure and verify HSRP active/standby election, including priority, preempt, virtual IP, and failover verification.

Accepted Answer

1. Configure interface with IP address and no shutdown
2. Set HSRP priority and preempt
3. Configure HSRP virtual IP
4. Verify HSRP state and failover with 'show standby'. The order ensures the interface is ready, then priority and preempt are set to influence the election, followed by the virtual IP and verification of failover behavior.

Answer

1. Configure HSRP virtual IP
2. Set HSRP priority and preempt
3. Configure interface with IP address and no shutdown
4. Verify HSRP state and failover with 'show standby'

Answer

1. Set HSRP priority and preempt
2. Configure HSRP virtual IP
3. Configure interface with IP address and no shutdown
4. Verify HSRP state and failover with 'show standby'

Answer

1. Configure HSRP virtual IP
2. Configure interface with IP address and no shutdown
3. Set HSRP priority and preempt
4. Verify HSRP state and failover with 'show standby'

Question 15

You are connected to R1 via the console. R1 is a Cisco ISR 4321 router running IOS-XE. The network team has recently changed the routing protocol from EIGRP to OSPF, but some routes are missing from the routing table. You need to analyze the OSPF neighbor states and LSDB to identify the issue.

Accepted Answer

Use 'show ip ospf neighbor' to check neighbor state; if not FULL, examine 'show ip ospf interface' for mismatched hello/dead intervals or network type.. OSPF requires consistent hello/dead intervals and network types to form adjacency. If the neighbor is not in FULL state, routes will not be exchanged. Checking 'show ip ospf neighbor' reveals the state; mismatched parameters can be corrected by adjusting interface configuration.

Answer

Use 'show ip route ospf' to verify OSPF routes; if missing, re-enter the OSPF process and redistribute connected routes.

Answer

Use 'debug ip ospf events' to monitor OSPF packets; if no packets are seen, reconfigure OSPF router ID and clear the OSPF process.

Answer

Use 'show ip protocols' to verify OSPF process configuration; if incorrect, delete and recreate the OSPF process with the correct network statements.

Question 16

Match each security term to its most accurate meaning.

Accepted Answer

Phishing: An attack that uses deceptive emails or websites to trick users into revealing sensitive information.. These are common security threats. Phishing, ransomware, DDoS, man-in-the-middle, zero-day, and social engineering each have distinct meanings as described.

Answer

Phishing: An attack that encrypts a victim's data and demands payment for the decryption key.

Answer

Phishing: An attack that overwhelms a server with traffic to make it unavailable to users.

Answer

Phishing: An attack that intercepts communication between two parties to eavesdrop or alter data.

Question 17

Match each wireless concept to its description.

Accepted Answer

BSS: A single AP and its associated clients, forming the basic building block of a WLAN.. SSID is the Service Set Identifier, the network name that clients see when scanning for Wi-Fi. WPA2 is a Wi-Fi Protected Access 2 security standard that commonly uses AES encryption to secure traffic. An AP (Access Point) is a device that bridges wired and wireless networks, providing connectivity to clients. A controller-based WLAN uses a centralized controller to manage configuration, roaming, and security across multiple APs.

Answer

BSS: A wireless network with multiple APs connected by a distribution system, providing extended coverage.

Answer

BSS: A peer-to-peer wireless network without an AP, where stations communicate directly.

Answer

BSS: The MAC address of the access point, used to uniquely identify the BSS.

Question 18

Match each IP service to its primary function.

Accepted Answer

DHCP: Automatically assigns IP addresses to hosts. DHCP automatically assigns IP configuration (IP address, subnet mask, default gateway) to clients. DNS resolves human-readable hostnames (e.g., www.example.com) into IP addresses. NTP synchronizes device clocks over a network to ensure accurate time-stamping. Syslog provides a centralized collection of event and log messages from network devices.

Question 19

Match each network-assurance item to its most accurate role.

Accepted Answer

Uptime: Measures the percentage of time a network device or link has been operational without failure.. Syslog provides a centralized mechanism for collecting and storing event logs and system messages from network devices, making it ideal for event and message reporting. SNMP allows network management systems to query devices and receive traps, enabling monitoring and management data exchange. NetFlow captures traffic flow details such as source, destination, and volume, offering visibility into how traffic moves through the network. NTP synchronizes device clocks to a reference source, ensuring accurate timestamps in logs and flow data for reliable correlation and troubleshooting.

Answer

Uptime: Measures the amount of data successfully transmitted over a network link in a given time period.

Answer

Uptime: Measures the variation in delay (jitter) experienced by packets traversing a network.

Answer

Uptime: Measures the average time it takes for a packet to travel from source to destination.

Question 20

Match each JSON term to its most accurate meaning.

Accepted Answer

Object: a collection of key/value pairs. JSON terms: Object is a collection of key/value pairs; Array is an ordered list; Key is the name; Value is the data; String is text in quotes; Boolean is true/false.

Answer

Object: an ordered list of values

Answer

Object: a single text value enclosed in double quotes

Answer

Object: a true/false value

CCNA Practice Exam 62 — 20 Questions

Exhibit

CCNA Practice Exam 62 — 20 Questions

Exhibit