{"id":15063,"date":"2026-09-17T08:58:02","date_gmt":"2026-09-17T08:58:02","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=15063"},"modified":"2026-09-17T08:58:02","modified_gmt":"2026-09-17T08:58:02","slug":"cisco-ccna-automation-200-901-practice-test-questions-and-exam-dumps-part17-q321-q340","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/cisco-ccna-automation-200-901-practice-test-questions-and-exam-dumps-part17-q321-q340\/","title":{"rendered":"Cisco CCNA Automation 200-901 Practice Test Questions and Exam Dumps Part17 Q321-Q340"},"content":{"rendered":"<h1><\/h1>\n<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/200-901-exam-dumps\"><b>Cisco CCNA Automation 200-901 Exam Dumps<\/b><\/a><b> and Practice Test Dumps.<\/b><\/h2>\n<p>&nbsp;<\/p>\n<h3><b>Question 321<\/b><\/h3>\n<p><b>Which HTTP method is commonly used to create a new resource through a REST API?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">PUT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">POST<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GET<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DELETE<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The HTTP <\/span><span style=\"font-weight: 400;\">POST<\/span><span style=\"font-weight: 400;\"> method is commonly used to create a new resource or submit data for processing through a REST API. In network automation, an application might use POST to create a device object, submit a job, or create a configuration resource. The exact behavior depends on the API design. <\/span><span style=\"font-weight: 400;\">GET<\/span><span style=\"font-weight: 400;\"> is primarily used for retrieving information, <\/span><span style=\"font-weight: 400;\">DELETE<\/span><span style=\"font-weight: 400;\"> removes resources, and <\/span><span style=\"font-weight: 400;\">PUT<\/span><span style=\"font-weight: 400;\"> is commonly associated with replacing or setting a resource representation. Therefore, POST is the appropriate choice when an API uses the method to create a new resource.<\/span><\/p>\n<h3><b>Question 322<\/b><\/h3>\n<p><b>Which HTTP method is commonly used to completely replace an existing resource representation?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">PATCH<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GET<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">PUT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">POST<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The HTTP <\/span><span style=\"font-weight: 400;\">PUT<\/span><span style=\"font-weight: 400;\"> method is commonly used to create or completely replace the representation of a resource at a specified location. In automation, a client may send a complete representation of a resource to ensure that the server reflects the desired data. This differs from PATCH, which is generally associated with partial modifications. GET retrieves information, while POST is commonly used for creating resources or triggering operations. The exact behavior depends on the API specification, but PUT is conventionally associated with complete replacement or setting a resource representation.<\/span><\/p>\n<h3><b>Question 323<\/b><\/h3>\n<p><b>Which REST API characteristic means that each request should contain the information necessary for the server to process it?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Stateful<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Stateless<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Persistent<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Synchronous<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A stateless REST interaction means that the server does not rely on stored client session state to understand each request. Each request should contain the information necessary for the server to process it, such as authentication credentials or tokens when required. Statelessness can simplify scaling because the server does not need to maintain application-specific session information for every client. It does not mean that the network connection itself can never persist. Stateful, persistent, and synchronous describe different concepts and do not define this REST architectural characteristic. Therefore, stateless is correct.<\/span><\/p>\n<h3><b>Question 324<\/b><\/h3>\n<p><b>Which HTTP method is generally used to remove an existing REST API resource?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DELETE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">PATCH<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GET<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">HEAD<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The HTTP <\/span><span style=\"font-weight: 400;\">DELETE<\/span><span style=\"font-weight: 400;\"> method is generally used to request removal of a specified resource. In network automation, an API may use DELETE to remove an object such as a policy, interface configuration object, or inventory entry. The actual permissions and behavior are determined by the API implementation. GET retrieves information, PATCH typically modifies part of a resource, and HEAD retrieves response metadata without the normal response body. Therefore, DELETE is the method generally associated with removing a REST resource.<\/span><\/p>\n<h3><b>Question 325<\/b><\/h3>\n<p><b>Which API parameter is normally placed directly within the URL path to identify a specific resource?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Header parameter<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Path parameter<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Cookie parameter<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Body parameter<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A path parameter is included directly within the URL path and is commonly used to identify a specific resource. For example, an API might use a URL structure such as <\/span><span style=\"font-weight: 400;\">\/devices\/123<\/span><span style=\"font-weight: 400;\"> where <\/span><span style=\"font-weight: 400;\">123<\/span><span style=\"font-weight: 400;\"> identifies a particular device. Query parameters are different because they are typically placed after a question mark and are often used for filtering, sorting, or pagination. Headers and request bodies carry information in other parts of the HTTP request. Therefore, a path parameter is the correct answer for identifying a resource within the URL path.<\/span><\/p>\n<h3><b>Question 326<\/b><\/h3>\n<p><b>Which API parameter is commonly used to filter or sort returned resources without changing the endpoint itself?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query parameter<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MAC parameter<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Ethernet parameter<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Frame parameter<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Query parameters are commonly used to provide optional information such as filtering, sorting, pagination, or field selection. They are normally included after a <\/span><span style=\"font-weight: 400;\">?<\/span><span style=\"font-weight: 400;\"> in a URL and may contain multiple key-value pairs. For example, an API might support a query parameter to return only devices with a particular status. This allows the client to customize the result while using the same endpoint. MAC, Ethernet, and frame parameters are not standard HTTP API parameter categories. Therefore, query parameter is correct.<\/span><\/p>\n<h3><b>Question 327<\/b><\/h3>\n<p><b>What is URL encoding primarily used for?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Representing special characters safely within URLs<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Encrypting API passwords<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Compressing JSON responses<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Creating VLAN tags<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">URL encoding represents characters in a format that can safely be transmitted as part of a URL. Certain characters have special meanings in URLs, so encoding prevents ambiguity when they appear as data. This is particularly important when automation scripts construct API URLs containing query parameters or values with spaces and special characters. URL encoding should not be confused with encryption because it does not protect sensitive information from being read. It also does not compress JSON or create VLAN tags. Therefore, safely representing special characters in URLs is the correct answer.<\/span><\/p>\n<h3><b>Question 328<\/b><\/h3>\n<p><b>Which HTTP header commonly carries authentication credentials such as a bearer token?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Accept<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Authorization<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Content-Length<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Host<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The HTTP <\/span><span style=\"font-weight: 400;\">Authorization<\/span><span style=\"font-weight: 400;\"> header is commonly used to carry authentication credentials. For example, an API may use a bearer token with a format such as <\/span><span style=\"font-weight: 400;\">Authorization: Bearer &lt;token&gt;<\/span><span style=\"font-weight: 400;\">. The exact authentication scheme depends on the API. The <\/span><span style=\"font-weight: 400;\">Accept<\/span><span style=\"font-weight: 400;\"> header indicates preferred response formats, <\/span><span style=\"font-weight: 400;\">Content-Length<\/span><span style=\"font-weight: 400;\"> describes the size of the request or response body, and <\/span><span style=\"font-weight: 400;\">Host<\/span><span style=\"font-weight: 400;\"> identifies the destination host. Proper handling of authorization headers is essential because tokens may provide access to protected network-management resources. Therefore, Authorization is correct.<\/span><\/p>\n<h3><b>Question 329<\/b><\/h3>\n<p><b>What is the purpose of an API version such as <\/b><b>\/v1\/<\/b><b> in an endpoint?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To identify a particular API version<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To specify a physical switch port<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To indicate a VLAN number<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To define a TCP port automatically<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">An API version identifier such as <\/span><span style=\"font-weight: 400;\">\/v1\/<\/span><span style=\"font-weight: 400;\"> commonly indicates which version of an API the client is using. API versioning helps providers introduce changes while maintaining compatibility with existing applications. An automation application can therefore target a specific version whose endpoints, fields, and behavior are known. API versions are not physical switch ports, VLAN identifiers, or automatic TCP port definitions. The exact versioning strategy varies between APIs, but version identifiers commonly help manage changes to API contracts. Therefore, identifying a particular API version is correct.<\/span><\/p>\n<h3><b>Question 330<\/b><\/h3>\n<p><b>Which feature of an API specification describes the expected structure of request and response data?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Schema<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Router<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Interface<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VLAN<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A schema describes the structure, fields, data types, and constraints of data exchanged by an API. In OpenAPI specifications, schemas can define the expected structure of JSON request bodies and responses. This allows developers to understand what fields are required, which values are allowed, and how nested objects are organized. A router, interface, or VLAN is a networking concept rather than an API data-model definition. Therefore, schema is the correct answer.<\/span><\/p>\n<h3><b>Question 331<\/b><\/h3>\n<p><b>Which data format uses key-value pairs enclosed in curly braces to represent an object?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CSV<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">XML<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">JSON<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Plain text<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">JSON represents objects using curly braces and key-value pairs. For example, a device object might contain fields such as hostname, IP address, and status. JSON is widely used by REST APIs because it is structured, relatively compact, and easily processed by programming languages such as Python. CSV represents tabular data using delimiters, XML uses tags and elements, and plain text has no required structured object syntax. Therefore, JSON is the correct data format for representing an object with key-value pairs inside curly braces.<\/span><\/p>\n<h3><b>Question 332<\/b><\/h3>\n<p><b>Which XML feature allows elements to be associated with a particular namespace?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">XML namespace declaration<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">JSON key<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">YAML anchor<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CSV header<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">An XML namespace declaration associates XML elements and attributes with a specific namespace, helping prevent naming conflicts between different XML vocabularies. Namespaces are especially important in technologies such as NETCONF and YANG because different YANG modules can define elements that need to be distinguished. JSON keys, YAML anchors, and CSV headers serve different purposes. Understanding XML namespaces is useful when working with structured network-management protocols that exchange XML documents. Therefore, an XML namespace declaration is the correct answer.<\/span><\/p>\n<h3><b>Question 333<\/b><\/h3>\n<p><b>Which NETCONF capability allows a client to determine supported protocol features on a server?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Capability exchange<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DNS discovery<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ARP inspection<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VLAN negotiation<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">NETCONF uses capability exchange to allow a client and server to advertise supported protocol capabilities. During session establishment, the endpoints exchange <\/span><span style=\"font-weight: 400;\">&lt;hello&gt;<\/span><span style=\"font-weight: 400;\"> messages containing capability information. This allows an automation application to determine which operations or features the NETCONF server supports before attempting to use them. This is useful because different devices or software versions may support different capabilities. DNS, ARP, and VLAN mechanisms do not perform NETCONF feature negotiation. Therefore, capability exchange is the correct answer.<\/span><\/p>\n<h3><b>Question 334<\/b><\/h3>\n<p><b>Which NETCONF message is exchanged when a session is initially established?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">&lt;hello&gt;<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">&lt;commit&gt;<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">&lt;get-config&gt;<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">&lt;lock&gt;<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">NETCONF endpoints exchange <\/span><span style=\"font-weight: 400;\">&lt;hello&gt;<\/span><span style=\"font-weight: 400;\"> messages when establishing a NETCONF session. These messages advertise protocol capabilities supported by the client and server and help establish the context for subsequent NETCONF operations. Operations such as <\/span><span style=\"font-weight: 400;\">&lt;get-config&gt;<\/span><span style=\"font-weight: 400;\">, <\/span><span style=\"font-weight: 400;\">&lt;commit&gt;<\/span><span style=\"font-weight: 400;\">, and <\/span><span style=\"font-weight: 400;\">&lt;lock&gt;<\/span><span style=\"font-weight: 400;\"> are performed after the session has been established. The hello exchange is therefore an important part of NETCONF session initialization. Consequently, <\/span><span style=\"font-weight: 400;\">&lt;hello&gt;<\/span><span style=\"font-weight: 400;\"> is the correct answer.<\/span><\/p>\n<h3><b>Question 335<\/b><\/h3>\n<p><b>Which NETCONF datastore generally represents the configuration currently active on a device?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Candidate<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Running<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Startup only<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Temporary<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The NETCONF <\/span><span style=\"font-weight: 400;\">running<\/span><span style=\"font-weight: 400;\"> datastore represents the configuration currently active on the device. Automation applications can retrieve or modify configuration according to the capabilities and supported operations of the device. A <\/span><span style=\"font-weight: 400;\">candidate<\/span><span style=\"font-weight: 400;\"> datastore can be used as a staging area for changes before they are committed when supported. Startup configuration is a separate concept and may represent configuration used during boot. Therefore, the running datastore is the one that generally represents the active configuration.<\/span><\/p>\n<h3><b>Question 336<\/b><\/h3>\n<p><b>What is the purpose of a NETCONF candidate datastore?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To stage configuration changes before they are committed<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To store DNS records<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To replace the operating system<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To capture packets<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A NETCONF candidate datastore provides a staging area where configuration changes can be prepared before they are committed to the running configuration. This allows an automation workflow to make several related changes and validate them before applying the final configuration, when the device supports the candidate capability. It can improve control over configuration transactions and reduce the risk of partially applied changes. Candidate configuration does not store DNS records, replace the operating system, or capture packets. Therefore, staging configuration changes before commitment is correct.<\/span><\/p>\n<h3><b>Question 337<\/b><\/h3>\n<p><b>Which YANG statement defines a single scalar data value?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">container<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">list<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">leaf<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">grouping<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The YANG <\/span><span style=\"font-weight: 400;\">leaf<\/span><span style=\"font-weight: 400;\"> statement defines a single scalar data value. A leaf can have a type such as string, integer, Boolean, enumeration, or another defined type. For example, a YANG model may define a leaf representing an interface description or administrative status. A container groups child nodes, a list represents repeated structured entries, and a grouping defines reusable schema structures. Understanding these YANG node types is important because NETCONF and RESTCONF use YANG models to structure network-management data. Therefore, leaf is correct.<\/span><\/p>\n<h3><b>Question 338<\/b><\/h3>\n<p><b>Which YANG statement is used to represent multiple instances of a structured data node?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">leaf<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">list<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">typedef<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">namespace<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The YANG <\/span><span style=\"font-weight: 400;\">list<\/span><span style=\"font-weight: 400;\"> statement represents multiple instances of a structured data node. Each list entry can contain multiple child nodes and can be identified using one or more key leaves when a key is defined. Lists are useful for modeling repeated objects such as interfaces, users, routes, or other collections. A leaf represents a single scalar value, typedef defines a reusable type, and namespace information identifies XML namespace context. Therefore, list is the correct YANG statement for representing multiple structured instances.<\/span><\/p>\n<h3><b>Question 339<\/b><\/h3>\n<p><b>What is the main purpose of a YANG list key?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To uniquely identify list entries<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To encrypt list data<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To define an IPsec tunnel<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To establish a NETCONF session<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A YANG list key identifies individual entries within a list and allows each entry to be uniquely distinguished. For example, an interface list may use an interface name as its key so that each interface entry can be addressed separately. Keys are important when automation applications retrieve, modify, or delete specific modeled objects through NETCONF or RESTCONF. A key does not encrypt data, establish IPsec tunnels, or create NETCONF sessions. Therefore, uniquely identifying list entries is the correct purpose.<\/span><\/p>\n<h3><b>Question 340<\/b><\/h3>\n<p><b>Which protocol provides a REST-like HTTP interface for interacting with YANG-modeled data?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">FTP<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">RESTCONF<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TFTP<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SMTP<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">RESTCONF provides an HTTP-based interface for interacting with YANG-modeled configuration and operational data. It combines REST-style concepts with structured data models defined using YANG, allowing automation applications to use familiar HTTP methods such as GET, POST, PUT, PATCH, and DELETE where supported. NETCONF provides another programmatic interface to YANG-modeled data but uses XML-based RPC operations rather than a REST-style HTTP interface. FTP and TFTP are file-transfer protocols, while SMTP is used for email. Therefore, RESTCONF is the correct answer.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Cisco CCNA Automation 200-901 Exam Dumps and Practice Test Dumps. &nbsp; Question 321 Which HTTP method is commonly used to create a new resource through a REST API? PUT POST GET DELETE Correct Answer: 2 Explanation The HTTP POST method is commonly used to create a new resource or submit data for processing [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15063"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=15063"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15063\/revisions"}],"predecessor-version":[{"id":15071,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15063\/revisions\/15071"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=15063"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=15063"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=15063"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}