Exam 350-901 topic 1 question 352 discussion

B E ansible can use netconf which uses ssh, SSH is also encrypted. Can you configure Nexus of https?

B & E I think the key to this questions is the requirement that Ansible be used. NX-API is a web based method of executing API request. Yes, they are asynchronous and it does use HTTPS but if you are using it you are not using Ansible. Ansible can use NETCONF and HTTPS and NETCONF does support asynchronous request.

C. HTTPS Analysis: HTTPS is an encrypted version of HTTP, using SSL/TLS to secure data in transit. It serves as the transport protocol for APIs like NX-API or RESTCONF on NX-OS switches. While not a standalone access mechanism, it’s a critical component enabling encrypted communication. Ansible can use HTTPS as the transport layer for NX-API or NETCONF, satisfying the encryption requirement. However, HTTPS alone doesn’t define asynchronous support—it depends on the underlying protocol (e.g., NX-API or NETCONF). Fit: Meets encrypted transport but is not a complete access mechanism; requires pairing with NX-API or NETCONF.

NETCONF supports encrypted transport using SSH and can handle asynchronous requests.

The correct answers are: B. NX-API and C. HTTPS Explanation: To meet the requirements of automating configurations on a Cisco NX-OS switch using Ansible, with encryption and support for asynchronous requests, the best options are: NX-API (B): NX-API (NXOS API) is Cisco's application programming interface for NX-OS based devices, which allows for commands to be sent to Cisco switches and responses to be received in a structured format such as JSON or XML. NX-API supports the use of HTTPS as its transport protocol, ensuring the encryption requirement is met. It also provides the capability to make calls and receive responses asynchronously. HTTPS (C): HTTPS is the secure version of HTTP, encrypting the data transmitted between the client and the server. Using HTTPS as the transport protocol for NX-API ensures that the communication is encrypted, addressing the security requirement specified in the scenario. HTTPS is commonly used with NX-API to secure the data in transit.

NX-API uses HTTP/HTTPS as its transport. CLIs are encoded into the HTTP/HTTPS POST body. Starting with Cisco NX-OS Release 9.2 (1), the NX-API feature is enabled by default on HTTPS port 443. HTTP port 80 is disabled. NX-API is also supported through UNIX Domain Sockets for applications running natively on the host or within Guest Shell. https://www.cisco.com/c/en/us/td/docs/dcn/nx-os/nexus9000/102x/programmability/cisco-nexus-9000-series-nx-os-programmability-guide-release-102x/m-n9k-nx-api-cli-101x.html#:~:text=NX-API%20uses%20HTTP%2FHTTPS%20as%20its%20transport.%20CLIs%20are,natively%20on%20the%20host%20or%20within%20Guest%20Shell.

The giving answer seems to be correct, regarding to following reference: https://docs.ansible.com/ansible/latest/collections/cisco/nxos/nxos_nxapi_module.html Because the ansible can access Cisco Nexus devices through NXAPI in https...