{"id":15060,"date":"2026-09-17T08:58:32","date_gmt":"2026-09-17T08:58:32","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=15060"},"modified":"2026-09-17T08:58:32","modified_gmt":"2026-09-17T08:58:32","slug":"cisco-ccna-automation-200-901-practice-test-questions-and-exam-dumps-part14-q261-q280","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/cisco-ccna-automation-200-901-practice-test-questions-and-exam-dumps-part14-q261-q280\/","title":{"rendered":"Cisco CCNA Automation 200-901 Practice Test Questions and Exam Dumps Part14 Q261-Q280"},"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 261<\/b><\/h3>\n<p><b>Which HTTP method is generally used to partially modify an existing resource?<\/b><\/p>\n<ol>\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;\">POST<\/span><\/li>\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<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The HTTP <\/span><span style=\"font-weight: 400;\">PATCH<\/span><span style=\"font-weight: 400;\"> method is generally used to partially modify an existing resource. In network automation, an API may use PATCH when only selected attributes of a device, interface, policy, or other object need to be changed. This differs from <\/span><span style=\"font-weight: 400;\">PUT<\/span><span style=\"font-weight: 400;\">, which is commonly associated with replacing the complete representation of a resource. <\/span><span style=\"font-weight: 400;\">GET<\/span><span style=\"font-weight: 400;\"> retrieves information, <\/span><span style=\"font-weight: 400;\">POST<\/span><span style=\"font-weight: 400;\"> commonly creates a resource or triggers an operation, and <\/span><span style=\"font-weight: 400;\">DELETE<\/span><span style=\"font-weight: 400;\"> removes a resource. The exact behavior depends on the API implementation, but PATCH is conventionally associated with partial updates.<\/span><\/p>\n<h3><b>Question 262<\/b><\/h3>\n<p><b>What does HTTP status code 401 normally indicate?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Unauthorized or missing valid authentication<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Resource successfully created<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Server temporarily unavailable<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Request completed with no content<\/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;\">HTTP status code <\/span><span style=\"font-weight: 400;\">401<\/span><span style=\"font-weight: 400;\"> normally indicates that the request lacks valid authentication credentials or that the supplied credentials are not acceptable. In API automation, this can occur when a token is missing, expired, invalid, or incorrectly supplied. It is important to distinguish 401 from 403. A 403 response generally indicates that the client is authenticated but does not have permission to perform the requested operation. A successful creation commonly returns 201, while 204 indicates successful processing with no response content. Therefore, 401 relates primarily to authentication.<\/span><\/p>\n<h3><b>Question 263<\/b><\/h3>\n<p><b>Which HTTP status code commonly indicates that a request was successful but the server has no content to return?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">200<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">201<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">204<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">301<\/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;\">HTTP status code <\/span><span style=\"font-weight: 400;\">204 No Content<\/span><span style=\"font-weight: 400;\"> indicates that the request was successfully processed but there is no content in the response body. In network automation, this response may be encountered after operations such as successfully deleting a resource or updating a resource where the API does not return a representation. HTTP 200 generally indicates successful processing with a response, while 201 commonly indicates that a resource was created. HTTP 301 represents a redirect. Therefore, 204 is the appropriate status code for a successful response without content.<\/span><\/p>\n<h3><b>Question 264<\/b><\/h3>\n<p><b>Which HTTP method is considered idempotent when repeated requests have the same intended effect on the resource?<\/b><\/p>\n<ol>\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;\">PUT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CONNECT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">PATCH<\/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;\">HTTP <\/span><span style=\"font-weight: 400;\">PUT<\/span><span style=\"font-weight: 400;\"> is generally considered idempotent because sending the same PUT request multiple times should result in the same intended final state of the resource. This characteristic is useful in automation because retrying an operation after a temporary communication failure is less likely to create repeated changes. For example, repeatedly setting a resource to a specific configuration should leave it in the same intended state. POST is generally not considered idempotent because repeated requests may create multiple resources or trigger repeated actions. Therefore, PUT is the correct answer.<\/span><\/p>\n<h3><b>Question 265<\/b><\/h3>\n<p><b>What is the primary purpose of API pagination?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To encrypt API traffic<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To authenticate users<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To divide large result sets into manageable responses<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To change an HTTP method<\/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;\">API pagination divides a large collection of results into smaller groups or pages. This prevents an API from having to return thousands or millions of objects in a single response. Automation scripts can request one page at a time and continue until all required results have been processed. Pagination can improve performance, reduce memory consumption, and make API interactions more manageable. Pagination does not provide encryption or authentication, and it does not change the HTTP method being used. Therefore, dividing large result sets into manageable responses is the correct purpose.<\/span><\/p>\n<h3><b>Question 266<\/b><\/h3>\n<p><b>Which approach is commonly recommended when an API temporarily responds with a rate-limit condition?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Retry immediately in an unlimited loop<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Use controlled retry and backoff<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Disable authentication<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Delete the API endpoint<\/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;\">Controlled retry with backoff is a common approach when an API temporarily limits requests. A backoff strategy causes the automation program to wait before trying again, reducing the possibility of continuously sending requests while the service is overloaded or enforcing rate limits. Some APIs provide headers indicating when a client should retry. An unlimited immediate retry loop can make the problem worse and may cause additional rate limiting. Authentication should not be disabled as a workaround. Therefore, controlled retry and backoff is the appropriate approach.<\/span><\/p>\n<h3><b>Question 267<\/b><\/h3>\n<p><b>Which HTTP header commonly identifies the format of data being sent in the request body?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Content-Type<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Hostname-Type<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Request-Format<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data-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;\">The <\/span><span style=\"font-weight: 400;\">Content-Type<\/span><span style=\"font-weight: 400;\"> HTTP header indicates the media type of the data contained in the request body. For example, an API request containing JSON commonly uses <\/span><span style=\"font-weight: 400;\">Content-Type: application\/json<\/span><span style=\"font-weight: 400;\">. This allows the receiving application to understand how the request body should be interpreted. Other headers have different purposes, such as <\/span><span style=\"font-weight: 400;\">Authorization<\/span><span style=\"font-weight: 400;\"> for authentication information and <\/span><span style=\"font-weight: 400;\">Accept<\/span><span style=\"font-weight: 400;\"> for indicating preferred response formats. <\/span><span style=\"font-weight: 400;\">Hostname-Type<\/span><span style=\"font-weight: 400;\">, <\/span><span style=\"font-weight: 400;\">Request-Format<\/span><span style=\"font-weight: 400;\">, and <\/span><span style=\"font-weight: 400;\">Data-Header<\/span><span style=\"font-weight: 400;\"> are not standard HTTP headers serving this purpose. Therefore, Content-Type is the correct answer.<\/span><\/p>\n<h3><b>Question 268<\/b><\/h3>\n<p><b>Which HTTP header is commonly used to indicate the response formats an API client can accept?<\/b><\/p>\n<ol>\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;\">Authorization<\/span><\/li>\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;\">User-Agent<\/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;\">Accept<\/span><span style=\"font-weight: 400;\"> header allows a client to indicate which response media types it can process. For example, an automation application may send <\/span><span style=\"font-weight: 400;\">Accept: application\/json<\/span><span style=\"font-weight: 400;\"> when it expects a JSON response from a REST API. This differs from <\/span><span style=\"font-weight: 400;\">Content-Type<\/span><span style=\"font-weight: 400;\">, which describes the media type of the request or response body itself. <\/span><span style=\"font-weight: 400;\">Authorization<\/span><span style=\"font-weight: 400;\"> is associated with credentials, <\/span><span style=\"font-weight: 400;\">Content-Length<\/span><span style=\"font-weight: 400;\"> describes body size, and <\/span><span style=\"font-weight: 400;\">User-Agent<\/span><span style=\"font-weight: 400;\"> identifies the client software. Therefore, Accept is the correct header for expressing preferred response formats.<\/span><\/p>\n<h3><b>Question 269<\/b><\/h3>\n<p><b>What is the main purpose of OpenAPI in API development?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To physically configure network interfaces<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To describe and document an API<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To replace TCP<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To encrypt API credentials<\/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;\">OpenAPI provides a standardized way to describe and document HTTP APIs. An OpenAPI document can describe endpoints, supported HTTP methods, parameters, request bodies, responses, authentication schemes, and data structures. This information can be used by developers and automation engineers to understand how an API should be consumed. Tools can also use OpenAPI specifications to generate documentation, client libraries, or testing interfaces. OpenAPI does not physically configure interfaces, replace TCP, or provide encryption for credentials. Therefore, describing and documenting an API is its primary purpose.<\/span><\/p>\n<h3><b>Question 270<\/b><\/h3>\n<p><b>Which format is commonly used to represent an OpenAPI specification?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">JSON or YAML<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">JPEG only<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CSV only<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Binary executable only<\/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;\">OpenAPI specifications are commonly represented using either JSON or YAML. YAML is frequently preferred because it can be easier for humans to read and maintain, while JSON is also fully capable of representing the structured specification. An OpenAPI document describes API paths, operations, parameters, schemas, responses, and other details. JPEG, CSV, and executable binary files are not standard formats for OpenAPI specifications. Understanding OpenAPI is useful in automation because it provides structured documentation that helps developers interact with APIs correctly.<\/span><\/p>\n<h3><b>Question 271<\/b><\/h3>\n<p><b>What does TLS primarily provide for HTTPS communication?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Network address translation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Encryption and secure communication<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Automatic IP addressing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DNS resolution<\/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;\">TLS, or Transport Layer Security, provides security for HTTPS communications by helping protect data exchanged between a client and server. It provides encryption and supports authentication of the server through certificates. This is important when automation scripts communicate with APIs because credentials, tokens, configuration data, and responses may contain sensitive information. TLS does not perform network address translation, assign IP addresses, or resolve DNS names. HTTPS commonly uses HTTP over TLS, providing a protected communication channel for web and API traffic. Therefore, encryption and secure communication is the correct answer.<\/span><\/p>\n<h3><b>Question 272<\/b><\/h3>\n<p><b>Why should an automation script validate a server&#8217;s TLS certificate when connecting securely to an API?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To verify the server&#8217;s identity and help prevent interception<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To increase the device&#8217;s CPU speed<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To assign VLANs automatically<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To create a Git repository<\/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;\">Validating a TLS certificate helps an automation client verify that it is communicating with the intended server and that the certificate can be trusted according to the configured trust chain. This helps protect against certain man-in-the-middle attacks. Disabling certificate validation may make testing easier in some environments, but it reduces security and should not normally be used as a production solution. TLS certificate validation has no relationship to CPU speed, VLAN assignment, or Git repository creation. Therefore, verifying server identity and trust is the correct purpose.<\/span><\/p>\n<h3><b>Question 273<\/b><\/h3>\n<p><b>Which YANG statement is commonly used to define a reusable data type?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">namespace<\/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;\">notification<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">container<\/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;\">typedef<\/span><span style=\"font-weight: 400;\"> statement is used to define a reusable type based on an existing type. This allows a model designer to create a custom type that can be reused throughout a YANG model. For example, a custom type can define restrictions or characteristics that are relevant to a particular configuration value. A <\/span><span style=\"font-weight: 400;\">container<\/span><span style=\"font-weight: 400;\"> organizes related data nodes, while <\/span><span style=\"font-weight: 400;\">notification<\/span><span style=\"font-weight: 400;\"> defines event information. Namespace information identifies the XML namespace associated with a module. Therefore, typedef is the correct YANG statement for defining reusable data types.<\/span><\/p>\n<h3><b>Question 274<\/b><\/h3>\n<p><b>In YANG, what is the primary purpose of a <\/b><b>must<\/b><b> statement?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To define an additional validation constraint<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To create a Git branch<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To establish an SSH connection<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To define an API endpoint<\/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 <\/span><span style=\"font-weight: 400;\">must<\/span><span style=\"font-weight: 400;\"> statement defines a constraint that must be satisfied for the associated data to be considered valid. It uses an XPath expression to evaluate a condition based on the data tree. This allows a YANG model to enforce relationships or validation rules beyond basic data types. For example, a model can require one value to satisfy a condition based on another value. A <\/span><span style=\"font-weight: 400;\">must<\/span><span style=\"font-weight: 400;\"> statement does not create API endpoints, Git branches, or SSH sessions. Therefore, defining an additional validation constraint is the correct answer.<\/span><\/p>\n<h3><b>Question 275<\/b><\/h3>\n<p><b>Which YANG node type is used to organize related child data nodes?<\/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;\">leaf-list<\/span><\/li>\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;\">typedef<\/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;\">A YANG <\/span><span style=\"font-weight: 400;\">container<\/span><span style=\"font-weight: 400;\"> is used to group related child data nodes into a logical structure. Containers help organize configuration and operational data within a YANG model. A <\/span><span style=\"font-weight: 400;\">leaf<\/span><span style=\"font-weight: 400;\"> represents a single value, while a <\/span><span style=\"font-weight: 400;\">leaf-list<\/span><span style=\"font-weight: 400;\"> represents a collection of scalar values. A <\/span><span style=\"font-weight: 400;\">typedef<\/span><span style=\"font-weight: 400;\"> defines a reusable data type rather than a hierarchical data container. In network automation, understanding YANG hierarchy is important because protocols such as NETCONF and RESTCONF use modeled data structures based on YANG. Therefore, container is the correct answer.<\/span><\/p>\n<h3><b>Question 276<\/b><\/h3>\n<p><b>Which NETCONF operation is commonly used to retrieve configuration and state information from a device?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">&lt;get&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;lock&gt;<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">&lt;close-session&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;\">The NETCONF <\/span><span style=\"font-weight: 400;\">&lt;get&gt;<\/span><span style=\"font-weight: 400;\"> operation is used to retrieve configuration and state information from a device, depending on the datastore or filter involved. Automation applications can use NETCONF to request structured information instead of relying on CLI screen scraping. <\/span><span style=\"font-weight: 400;\">&lt;commit&gt;<\/span><span style=\"font-weight: 400;\"> applies candidate configuration changes, while <\/span><span style=\"font-weight: 400;\">&lt;lock&gt;<\/span><span style=\"font-weight: 400;\"> controls access to a datastore. <\/span><span style=\"font-weight: 400;\">&lt;close-session&gt;<\/span><span style=\"font-weight: 400;\"> terminates a NETCONF session. NETCONF operations are exchanged using XML-based RPC messages. Therefore, <\/span><span style=\"font-weight: 400;\">&lt;get&gt;<\/span><span style=\"font-weight: 400;\"> is the correct operation for retrieving information.<\/span><\/p>\n<h3><b>Question 277<\/b><\/h3>\n<p><b>What is the purpose of a NETCONF datastore lock?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To prevent conflicting changes by multiple clients<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To restart the network device<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To change the device hostname<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To encrypt XML messages<\/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 datastore lock helps prevent conflicting configuration changes by multiple clients accessing the same datastore. Locking is useful when an automation workflow needs exclusive access while making a sequence of changes. This can reduce the possibility that another client modifies the same configuration during the operation. A datastore lock does not restart the device, change its hostname, or encrypt XML messages. NETCONF security and transport protection are handled through other mechanisms, such as secure transport. Therefore, preventing conflicting concurrent changes is the correct answer.<\/span><\/p>\n<h3><b>Question 278<\/b><\/h3>\n<p><b>Which technology is commonly associated with streaming structured network telemetry using a model-driven approach?<\/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;\">gNMI<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Telnet<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TFTP<\/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;\">gNMI, or gRPC Network Management Interface, is commonly associated with modern model-driven network management and telemetry. It can be used to retrieve and subscribe to structured data modeled using technologies such as YANG. Streaming telemetry allows devices to continuously send selected operational data to a monitoring or automation system rather than requiring the system to repeatedly poll every value. FTP, Telnet, and TFTP serve different purposes and are not the primary technologies associated with modern model-driven streaming telemetry. Therefore, gNMI is the correct answer.<\/span><\/p>\n<h3><b>Question 279<\/b><\/h3>\n<p><b>What is a major characteristic of model-driven telemetry compared with traditional periodic polling?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It can stream selected operational data to a collector<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It requires manual CLI commands for every update<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It only transfers configuration files<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It disables network monitoring<\/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;\">Model-driven telemetry can stream selected operational data from network devices to a telemetry collector or monitoring system. Instead of repeatedly requesting each metric through traditional polling, a consumer can subscribe to specific modeled data and receive updates as they are produced. This can provide more timely visibility into network conditions and can reduce unnecessary repeated polling. Model-driven telemetry is not limited to configuration files and does not require manually entering CLI commands for every update. Therefore, streaming selected operational data to a collector is the correct characteristic.<\/span><\/p>\n<h3><b>Question 280<\/b><\/h3>\n<p><b>Which Git command downloads changes from a remote repository and integrates them into the current branch?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">git clone<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">git status<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">git pull<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">git branch<\/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 <\/span><span style=\"font-weight: 400;\">git pull<\/span><span style=\"font-weight: 400;\"> command retrieves changes from a remote repository and integrates them into the current local branch, typically by performing a fetch followed by a merge or another configured integration strategy. This is useful in collaborative automation projects where multiple engineers update infrastructure code. <\/span><span style=\"font-weight: 400;\">git clone<\/span><span style=\"font-weight: 400;\"> creates a local copy of a repository, <\/span><span style=\"font-weight: 400;\">git status<\/span><span style=\"font-weight: 400;\"> displays the working-tree state, and <\/span><span style=\"font-weight: 400;\">git branch<\/span><span style=\"font-weight: 400;\"> manages or displays branches. Therefore, <\/span><span style=\"font-weight: 400;\">git pull<\/span><span style=\"font-weight: 400;\"> is the correct command for downloading and integrating remote changes into the current branch.<\/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 261 Which HTTP method is generally used to partially modify an existing resource? GET POST DELETE PATCH Correct Answer: 4 Explanation The HTTP PATCH method is generally used to partially modify an existing resource. In network automation, an API may use [&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\/15060"}],"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=15060"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15060\/revisions"}],"predecessor-version":[{"id":15074,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15060\/revisions\/15074"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=15060"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=15060"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=15060"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}