CCNA AI and Network Operations Questions

SNMP does not use YANG data models and typically operates over UDP, not SSH.

RESTCONF uses HTTP/HTTPS for transport, not SSH, so it does not meet the requirement of operating over SSH.

CLI scripting lacks a standardized data model like YANG and is not a protocol that operates over SSH in the same structured manner as NETCONF.

Requires agents and is pull‑based, failing both the agentless and push requirements.

Agents are mandatory, and the pull mechanism contradicts the push requirement.

Lacks built‑in push‑based orchestration, idempotency, and agentless design without significant custom development, making it less suitable than a purpose‑built tool.

The DELETE method is used to remove a resource from the server, which directly modifies the state of the device's configuration. Since the question specifies that the script must retrieve the configuration without making any modifications, DELETE is not appropriate.

The PUT method is used to update or replace a resource on a server, which contradicts the requirement of retrieving the current configuration state without making any modifications.

The POST method is used to send data to a server to create or update a resource, which contradicts the requirement of retrieving the current configuration state without modifying anything.

This option is incorrect because controllers do not eliminate the need for switches and routers; these devices still perform the actual packet forwarding in the network.

This option is incorrect since controllers are highly relevant to automation, providing APIs and centralized control that enable automated network management workflows.

This option is incorrect because controller communication is not universally based on Telnet; modern controllers use secure protocols and APIs rather than relying solely on Telnet.

The specific factual error is that RESTCONF requires the media type application/yang-data+json for YANG data, not generic application/json.

The specific factual error is that the duplex setting is defined in the ietf-interfaces YANG model, not in Cisco-IOS-XE-native. The URI path must match the data model.

The specific factual errors are: (1) The PATCH body must be structured as {"ietf-interfaces:interface":{"duplex":"full"}} to match the YANG data tree; (2) The success response for PATCH is 204 No Content, not 200 OK.

STP (Spanning Tree Protocol) is a network protocol used for preventing loops in Ethernet networks, and it is not a data format used with REST APIs. Therefore, it does not represent objects, arrays, or key-value pairs.

EIGRP (Enhanced Interior Gateway Routing Protocol) is a routing protocol used for exchanging routing information within an autonomous system, not a data format for representing objects or key-value pairs in APIs.

802.1Q is a networking standard used for VLAN tagging in Ethernet frames, not a data format for representing objects or key-value pairs in APIs. It does not relate to REST API data representation.

Option C is incorrect because JSON does not require closing tags like XML; it uses braces and brackets to delimit data structures, making this statement false.

Option D is incorrect as JSON supports a variety of data types beyond numeric values, including strings, booleans, arrays, objects, and null, so it is not limited to numbers.

Option A is incorrect because a 301 status code indicates that the requested resource has been moved permanently to a new URL, not an authentication issue. Confusing 301 with 401 can lead to misdiagnosing API errors.

Option B is incorrect since a 204 status code means the request was successful but no content was returned. It does not indicate any authentication problem, unlike 401 which specifically relates to authorization failures.

Option D is incorrect because a server's inability to parse JSON usually results in a 400 Bad Request error, not a 401 Unauthorized. The 401 code is strictly about authentication, not parsing or syntax errors.

This option is incorrect because JSON objects do contain fields; they are collections of key-value pairs representing attributes of a single entity, so the claim that objects cannot contain fields is false.

This option is wrong because JSON arrays are a general data structure used for any list of items, not exclusively for IPv6 interfaces; interface type does not dictate JSON structure.

This option is incorrect because the choice of JSON data structure (array vs. object) does not affect API authentication or security; these are separate concerns unrelated to data formatting.

Option A is incorrect because the POST method is not used for retrieving resources; instead, it is intended for creating new resources or submitting data for processing in a RESTful API context.

The POST method is used to create or submit data, not to delete resources. Option C incorrectly describes the function of the DELETE method in RESTful APIs, which is responsible for removing resources.

Option D is incorrect because the POST method is not idempotent and does not replace an existing resource; it is primarily used to create new resources or submit data.

The specific factual error is that the question asks about the error when the Content-Type header is wrong, not the URI path. The URI path error is a separate issue.

The specific factual error is that a wrong Content-Type header causes a rejection before any body parsing, so the request does not succeed.

The specific factual error is that RESTCONF does accept JSON; the issue is the exact media type string, not the format.

The request uses unencoded slashes in the interface name and the configuration container `interfaces`, not `interfaces-state`, so it will not retrieve operational state.

RESTCONF uses GET for retrieval; POST is used to create new resources or invoke operations, not to read operational data.

This uses a Cisco-IOS-XE-specific module and unencoded slashes, while the task expects the standard ietf-interfaces operational state path.

SNMP is limited to monitoring and basic sets, not suited for complex remediation workflows.

CLI scripting lacks structured programmability and is error-prone for automation.

Syslog is a logging protocol and cannot be used to push configuration changes.

The specific factual errors: MD5 and DES are not the required algorithms; 'priv' level requires encryption but the question specifies 'auth' level; NetFlow egress is not the default and not requested; version 5 is not version 9.

The specific factual error: The trap host command specifies 'priv' security level, which requires the user to have a privacy password and sends encrypted traps, but the requirement is for 'auth' only.

The specific factual error: NetFlow version 5 is an older version that does not support templates and is not the required version 9.

The NTP command syntax is incorrect; 'ntp server' does not accept a 'source' parameter. The correct approach is a separate 'ntp source' command.

The logging trap level 7 corresponds to debugging, which is the most verbose level. The requirement is for critical (severity 2) and higher, so this would send too many messages.

The commands listed are already configured and do not fix the synchronization issue or the syslog filtering. The NTP source interface is missing, and the logging trap level is still debugging.

RESTful APIs do not require SNMP traps; they use HTTP methods for communication, and SNMP traps are unrelated to REST API operations.

RESTful APIs are format-agnostic and commonly support both XML and JSON, with JSON being the more prevalent format due to its lightweight nature. The statement that RESTful APIs can only return XML is incorrect.

The group keyword 'auth' only enables authentication, not encryption. AES 128 requires the 'priv' keyword.

The 'snmp-server user' command requires a group name. Omitting the group will result in an error or incomplete configuration.

The command 'ip flow-export destination' sets the collector IP and port, not the export version. The version is set with 'ip flow-export version 9'.

Tokens do not eliminate security controls; they still require mechanisms like expiration, revocation, and secure storage.

Tokens are unrelated to VLAN creation; VLANs are configured via switch CLI or network management protocols, not API tokens.

Tokens do not replace routing protocols; routing protocols handle packet forwarding, while tokens handle API access authentication.

Syslog severity levels use inverse numbering: level 4 (warning) is more severe than level 5 (notice), so the statement is false.

Syslog level 0 (emergency) is the highest severity, indicating a catastrophic system failure, not a normal operational message.

NTP stratum 0 is the reference clock itself; devices synchronized directly to it are stratum 1, not stratum 0.

SDN controllers do not replace AI; AI can augment control and decision-making, making this statement false.

AI in SDN applies to security, compliance, and analytics, not only traffic engineering, so this statement is incorrect.

Intent-based networking requires continuous monitoring and feedback loops to ensure match with intent, so this statement is false.

The specific factual error is that the 'copy' command in Cisco IOS requires a confirmation (pressing Enter) when the destination filename is provided. The script must send an additional newline to complete the operation.

The specific factual error is that the 'copy' command generates an intermediate prompt ('[confirm]') before returning to the router prompt. The script should wait for that intermediate prompt, not the final prompt.

The specific factual error is that including a newline in the command string does not simulate an interactive response to a subsequent prompt. The script must send the newline separately after the command is issued.

Option C is incorrect because JSON does not use angle-bracket tags; that syntax belongs to XML. Confusing JSON with XML is a common mistake but not accurate for this question.

Option D is incorrect as JSON is not a routing protocol. It is a data format used for representing information, not for routing or control plane functions in networks.

Option E is incorrect because JSON can carry various data types beyond integers, including strings, booleans, arrays, objects, and null values. Limiting JSON to integers is a misunderstanding.

This option is incorrect because idempotency does not relate to the transport layer protocols like TCP or UDP; it focuses on the behavior of operations in terms of repeated execution leading to the same outcome.

Option C is incorrect because idempotency does not relate to the encryption of device credentials; it refers to the property of operations that can be applied multiple times without changing the result beyond the initial application.

Option D is incorrect because idempotency does not dictate the use of a single management protocol; rather, it refers to the property of operations yielding the same result regardless of how many times they are executed.

This option is wrong because the response is in JSON format, not XML. JSON uses curly braces and key-value pairs, while XML uses tags to define elements.

The hostname field is a string, not a list, as it contains a single value ('Dist-1') and does not represent multiple items or entries.

This option is wrong because the format shown in the response is JSON, not YAML. YAML uses indentation and a different syntax for data representation, which is not present here.

Option B is incorrect because POST does not always replace an existing resource completely; it usually creates new resources or triggers processing. PUT is the method associated with full resource replacement.

Option D is incorrect because REST APIs do not require SNMP as the transport mechanism; they typically use HTTP or HTTPS protocols for communication.

This is incorrect because spam classification is a supervised learning problem, not a reinforcement learning one.

This is incorrect because clustering groups data, it doesn't forecast numeric values like bandwidth usage.

This is incorrect because predictive analytics typically involves dynamic ML models, not just static thresholds.

POST is incorrect because it is used to create new resources or submit data that modifies the server state, not for retrieving existing data. Selecting POST would imply changing the resource, which contradicts the question's requirement for a non-modifying method.

PUT is incorrect as it replaces or updates an existing resource entirely. It modifies the resource state, which is not the intended action when simply retrieving data from a REST API.

DELETE is incorrect because it removes a resource from the server. Using DELETE would modify the resource by deleting it, which is the opposite of the question's intent to retrieve data without modification.

This option incorrectly describes a northbound API as a cable type, which is a physical concept unrelated to the logical API direction in controller architectures.

This option confuses northbound APIs with routing protocols like link-state protocols, which are unrelated to the software interface role of northbound APIs.

This option falsely claims that northbound APIs remove the need for authentication, ignoring that security controls remain essential for API access.

Missing the required SNMPv3 group and relies on the deprecated interface command 'ip flow export' instead of the modern flow monitor method.

Lacks the required global flow monitor definition block; the 'ip flow monitor' command on the interface refers to a nonexistent monitor.

Places the flow monitor definition commands inside the interface configuration context, where they would be rejected as invalid.

The specific factual error: The 'ntp server' command cannot specify a source interface; that is done with 'ntp source'. Additionally, 'warnings' (level 4) is more severe than 'notifications' (level 5), but the requirement is to send only notifications and above, which includes levels 0-5. 'warnings' includes levels 0-4, missing level 5 (notifications).

The specific factual error: 'logging trap debugging' sends all syslog messages (levels 0-7), which is the default and does not filter out lower-severity messages. The correct level for notifications and above is 'notifications' (level 5).

The specific factual error: The NTP client is not configured to source packets from Loopback0. The 'ntp server' command alone does not set the source interface; an additional 'ntp source' command is required.

Combines the NTP source directly in the server command, but the required configuration uses a separate 'ntp source Loopback0' command.

Sets logging trap to debugging (level 7), not the required notifications (level 5).

Missing the 'ntp source Loopback0' command, so NTP will not use the Loopback0 interface as source.

Option B is incorrect because HTTPS does not remove the need for tokens or credentials; it only secures the transport layer. Authentication is still required to control access to APIs.

Option C is incorrect since JSON can be transmitted over any protocol, including HTTP and HTTPS. The choice of HTTPS is about securing the transport, not the data format.

Option D is incorrect because HTTP can carry API requests; however, it does so without encryption, making it unsuitable for sensitive data transmission.

Option B is incorrect because an API response that returns a list of interface objects should be structured as an array, not as a single integer. A single integer does not represent a collection of objects.

A native VLAN field is not a valid representation of a list of interface objects in JSON; it typically refers to a specific VLAN configuration in networking, not an array structure.

Option D is incorrect because an STP root bridge ID is a specific identifier related to Spanning Tree Protocol, not a representation of a list of interface objects in JSON format.

The scenario specifies a protocol that uses XML-based RPCs over SSH, which is a characteristic of NETCONF, not RESTCONF.

The scenario specifically asks for a standard, vendor-neutral data modeling language, which CLI is not.

Neither the data modeling language (CLI) nor the protocol (RESTCONF) matches the specified requirements of vendor-neutral data modeling and XML-based RPCs over SSH.

Option C is incorrect because the token does not change the API protocol from REST to SNMP; authentication methods do not alter the underlying management protocol.

Option D is incorrect because tokens are managed dynamically by client applications and are not stored in router startup-config files, which hold static device configurations.

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

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.

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

Option B is incorrect because northbound APIs do not replace physical network devices; forwarding hardware remains essential for actual data transmission and network operation.

Option C is incorrect since northbound APIs are software interfaces, not physical cabling standards, and have no relation to data center uplink cabling specifications.

Option D is incorrect because northbound APIs still require security measures such as authentication and authorization; they do not eliminate the need for security controls.

The trap level should be set to 'notifications' (level 5) or higher severity to forward level 5 messages; 'informational' is lower severity and would not forward level 5 messages.

The trap level is currently 'informational' (6), not 'notifications'. Changing to 'debugging' would forward all messages, but the requirement is to forward level 5 and above, which is achieved by setting trap level to 'notifications' (5).

Setting the trap level to 'emergencies' would filter out all messages except level 0, so level 5 messages would not be forwarded.

The specific factual error is that Cisco IOS XE RESTCONF implementation does not support XML content type; it only supports JSON.

The specific factual error is that the admin status is not available under the native YANG model; it is under ietf-interfaces.

The specific factual error is that RESTCONF requires the media type application/yang-data+json, not generic application/json. Additionally, the module name prefix is required in the JSON body.

YANG is a data modeling language used to define the structure of network data but is not the actual data format used in REST API communication, making it an incorrect choice.

STP (Spanning Tree Protocol) is a Layer 2 protocol for preventing loops in Ethernet networks and has no relation to data formatting in REST APIs, so it is incorrect.

TFTP is a simple protocol used for file transfers, such as IOS images, and is not a data format used in REST APIs, making it an invalid choice.

The specific factual error: The crypto key and 'ip ssh' are necessary for SSH operation, but the VTY transport setting is the immediate cause of connection failure.

The specific factual error: There is no indication that SSH version 1 is in use; the issue is the VTY transport setting.

The specific factual error: A domain name is required for SSH key generation, but the VTY transport setting is the direct cause of the connection failure.

Direct manipulation of physical layer hardware is not a core AIOps capability; AIOps operates on data and software-based automation, not direct hardware control.

Guaranteed elimination of all false positive alarms is impossible because no AI system can achieve perfect accuracy; AIOps reduces but does not eliminate false positives.

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

The specific factual error: SNMP traps should use the read-only community string 'public', not the read-write 'private'.

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

The specific factual error is that a 400 Bad Request is not triggered by an incorrect Content-Type; it is triggered by malformed syntax or invalid data.

The specific factual error is that the Content-Type header does not affect resource discovery; it only affects how the server interprets the payload.

The specific factual error is that an unsupported media type results in a client error (4xx), not a success response (2xx).

Option A incorrectly pairs JSON with YANG modules as a data modeling language. JSON is a data interchange format used to represent data but does not define schemas or models. YANG is the actual modeling language used to define network data structures, so this pairing is false.

Option B wrongly describes YANG as a lightweight interchange format built from curly braces and arrays, which actually describes JSON syntax. YANG is a modeling language that defines network data hierarchies and constraints, not a data format with JSON-like syntax.

Option D falsely claims NETCONF is a spanning-tree enhancement for rapid convergence. NETCONF is a network configuration protocol using XML over SSH and has no relation to spanning-tree protocols or their convergence mechanisms, making this option incorrect.

This option is incorrect because HTTPS does not replace authentication; it enhances security by encrypting the transport layer, but authentication mechanisms still need to be implemented separately.

This option is incorrect because both HTTPS and HTTP can carry JSON data; JSON is a data format independent of the transport protocol used. Thus, HTTPS is not the only format capable of transmitting JSON.

This option is wrong because HTTP can indeed carry controller data; it is a fundamental protocol for transmitting data over the web. Both HTTP and HTTPS can be used to send and receive data, including JSON payloads, between clients and APIs.