nerdexam
Cisco

300-170 · Question #129

Which two statements about NX API REST are true? (Choose two)

The correct answer is A. NX-API REST uses HTTP/Hi VPS as its transport protocol. C. The NX-API REST backend uses the Nginx HTTP server. NX-API REST on Cisco Nexus devices utilizes HTTP/HTTPS for transport and is powered by the Nginx HTTP server on the backend.

Automation and Orchestration

Question

Which two statements about NX API REST are true? (Choose two)

Options

  • ANX-API REST uses HTTP/Hi VPS as its transport protocol.
  • BNX-API Kl SI is supported on Cisco Nexus 9000 and 3000 Series switches including switches
  • CThe NX-API REST backend uses the Nginx HTTP server.
  • DNX-API REST is best used when you have static network configurations, static workloads, and
  • ENX-API REST uses the Cisco APlC to provide a front end to developers.

How the community answered

(29 responses)
  • A
    93% (27)
  • B
    3% (1)
  • E
    3% (1)

Why each option

NX-API REST on Cisco Nexus devices utilizes HTTP/HTTPS for transport and is powered by the Nginx HTTP server on the backend.

ANX-API REST uses HTTP/Hi VPS as its transport protocol.Correct

NX-API REST, like most RESTful APIs, leverages standard web protocols such as HTTP and HTTPS for secure and unsecure communication with the network device. This enables programmatic interaction and configuration.

BNX-API Kl SI is supported on Cisco Nexus 9000 and 3000 Series switches including switches

The term 'NX-API Kl SI' appears to be a typo or incorrect acronym; while NX-API REST is broadly supported on Nexus 9000/3000, statements A and C are more definitively true and grammatically correct.

CThe NX-API REST backend uses the Nginx HTTP server.Correct

The Cisco NX-OS operating system, which runs on Nexus switches, uses the Nginx HTTP server as the underlying web server to serve the NX-API REST interface, handling requests and responses.

DNX-API REST is best used when you have static network configurations, static workloads, and

NX-API REST is designed for dynamic automation and programmability, making it suitable for environments with changing network configurations and workloads, not primarily for static ones.

ENX-API REST uses the Cisco APlC to provide a front end to developers.

NX-API REST is a direct interface to the Nexus switch itself and does not use the Cisco APIC as a front-end; the APIC is for ACI fabric management, while NX-API is for standalone Nexus device management.

Concept tested: Cisco NX-API REST fundamentals

Source: https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7x/prog_guide/b_Cisco_Nexus_9000_Series_NX-OS_Programmability_Guide_7x/b_Cisco_Nexus_9000_Series_NX-OS_Programmability_Guide_7x_chapter_0100.html

Topics

#NX-API REST#Cisco Nexus#API#programmability

Community Discussion

No community discussion yet for this question.

Full 300-170 Practice