AI and Network Operations practice questions

YAML can represent only arrays, while JSON can represent only strings

Why it fails: Both formats can represent far more than arrays or strings only.

JSON requires indentation but YAML requires curly braces

Why it fails: The description reverses the typical syntax characteristics.

YAML is a routing protocol and JSON is an access method

Why it fails: Neither YAML nor JSON is a routing protocol or an access method.

It uses angle brackets to define nested elements

Why it fails: Angle brackets are associated with XML, not JSON.

It is a routing protocol for controller communication

Why it fails: JSON is a data format, not a routing protocol.

It can be parsed only by Cisco devices

Why it fails: JSON is vendor-neutral and broadly supported.

It encrypts API payloads between a client and server

Why it fails: Encryption is handled by transport and security protocols, not by YANG itself.

It replaces JSON as a transport protocol

Why it fails: YANG is not a transport protocol and does not replace JSON directly.

It assigns VLAN IDs dynamically to trunks

Why it fails: YANG may describe data related to VLANs, but it does not dynamically assign VLAN IDs by itself.

It eliminates the need for IP addressing on managed devices.

Why it fails: YANG does not remove basic networking requirements.

It replaces TLS for secure API transport.

Why it fails: YANG is a data model, not a transport-security mechanism.

It forces all devices to run the same operating system.

Why it fails: YANG does not require identical NOS platforms.

To delete a resource permanently

Why it fails: DELETE is typically used for that action.

To create a new resource with a request body

Why it fails: POST is commonly used for creation.

To encrypt the API session automatically

Why it fails: Encryption is normally provided by HTTPS/TLS, not the GET verb itself.

YANG is the encrypted replacement for SSH

Why it fails: This is wrong because YANG is not a remote access protocol.

YANG is a trunk encapsulation method

Why it fails: This is wrong because trunk encapsulation belongs to VLAN transport, not data modeling.

YANG is an STP election field

Why it fails: This is wrong because YANG is unrelated to spanning-tree elections.

A special OSPF metric for controller traffic

Why it fails: This is wrong because API tokens are unrelated to OSPF metrics.

A trunking field used to carry multiple VLANs

Why it fails: This is wrong because VLAN trunking and token-based API access are unrelated concepts.

A duplex mode required for REST APIs

Why it fails: This is wrong because duplex settings apply to Ethernet links, not API security.

REST requires every request to use only TFTP

Why it fails: This is wrong because TFTP is unrelated to the standard REST model.

GET and POST are OSPF packet types

Why it fails: This is wrong because GET and POST are HTTP methods, not OSPF packet types.

REST replaces all need for authentication

Why it fails: This is wrong because REST APIs often still require authentication and authorization.

Because JSON automatically encrypts every API response

Why it fails: This is wrong because JSON is a data format, not encryption.

Because JSON replaces the need for HTTP methods

Why it fails: This is wrong because JSON often travels inside HTTP-based APIs.

Because JSON is required only for spanning-tree calculations

Why it fails: This is wrong because JSON is unrelated to STP calculations.

They replace all need for forwarding devices

Why it fails: This is wrong because forwarding devices are still needed.

They are used only for Ethernet duplex negotiation

Why it fails: This is wrong because APIs are software interfaces, not duplex mechanisms.

They make authentication unnecessary

Why it fails: This is wrong because APIs usually still require authentication and authorization.

HTTPS is a structured data format like JSON

Why it fails: This is wrong because HTTPS is transport, not a data format.

HTTPS is the default metric used by OSPF

Why it fails: This is wrong because HTTPS has nothing to do with routing metrics.

HTTPS is the VLAN used for secure management traffic

Why it fails: This is wrong because HTTPS is not a VLAN concept.

A token is the IPv4 subnet mask for controller traffic.

Why it fails: This is wrong because a token is not a subnetting concept.

A token is the STP root bridge identifier.

Why it fails: This is wrong because tokens are unrelated to STP root election.

A token forces the API to use Telnet.

Why it fails: This is wrong because tokens are not tied to Telnet usage.

They are the same thing and can always be used interchangeably.

Why it fails: This is wrong because the controller and its APIs are related but not identical.

A northbound API is the physical cable used between two controllers.

Why it fails: This is wrong because northbound API is a logical software concept, not a cable type.

A controller exists only to replace IPv6 addressing.

Why it fails: This is wrong because controller-based networking is not a replacement for IPv6 addressing.

Because JSON automatically supplies IP addressing to hosts

Why it fails: This is wrong because JSON is a data format, not an addressing service.

Because JSON replaces all authentication requirements

Why it fails: This is wrong because JSON does not eliminate access-control needs.

Because JSON is required for STP convergence

Why it fails: This is wrong because STP convergence is unrelated to JSON formatting.

Because JSON automatically configures the router’s default gateway.

Why it fails: This is wrong because JSON is not a host-configuration protocol.

Because JSON replaces HTTPS completely.

Why it fails: This is wrong because JSON is a data format, not a transport replacement.

Because JSON is required for STP to elect a root bridge.

Why it fails: This is wrong because STP has nothing to do with JSON data formatting.

A token is the OSPF cost of the controller link.

Why it fails: This is wrong because tokens are not routing metrics.

A token is the native VLAN for secure traffic.

Why it fails: This is wrong because tokens are unrelated to VLAN configuration.

A token replaces the need for HTTPS.

Why it fails: This is wrong because transport security and API credentials are different concerns.

It is the data format used inside every API payload.

Why it fails: This is wrong because HTTPS is transport, not the data format itself.

It replaces authentication and authorization entirely.

Why it fails: This is wrong because encryption in transit does not remove the need for access control.

It is the routing protocol used by the controller.

Why it fails: This is wrong because HTTPS is not a routing protocol.

They replace all forwarding devices in the network.

Why it fails: This is wrong because controllers and APIs do not eliminate the need for actual network devices.

They remove the need for authentication and authorization.

Why it fails: This is wrong because secure API access still depends on access-control mechanisms.

They are the same thing as switch trunks.

Why it fails: This is wrong because APIs are software interfaces, not Layer 2 link types.

They eliminate the need for HTTPS entirely.

Why it fails: This is wrong because token use does not replace transport security.

They are the same thing as router metrics.

Why it fails: This is wrong because tokens are unrelated to routing metrics.

They turn API data into VLAN tags.

Why it fails: This is wrong because tokens are not VLAN mechanisms.

Because JSON automatically authenticates the API client.

Why it fails: This is wrong because JSON is a data format, not an authentication mechanism.

Because free-form text cannot be read by humans.

Why it fails: This is wrong because human readability is often where free-form text is strongest.

Because JSON replaces HTTPS.

Why it fails: This is wrong because JSON is a format and HTTPS is a secure transport.