{"id":23918,"date":"2026-09-28T11:08:53","date_gmt":"2026-09-28T11:08:53","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=23918"},"modified":"2026-09-28T11:08:53","modified_gmt":"2026-09-28T11:08:53","slug":"cisco-ccnp-data-center-300-635-practice-test-questions-and-exam-dumps-part17-q321-340","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/cisco-ccnp-data-center-300-635-practice-test-questions-and-exam-dumps-part17-q321-340\/","title":{"rendered":"Cisco CCNP Data Center 300-635 Practice Test Questions and Exam Dumps Part17 Q321-340"},"content":{"rendered":"<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/300-635-exam-dumps\"><b>Cisco CCNP Data Center 300-635 Exam Dumps<\/b><\/a><b> and Practice Test Dumps<\/b><\/h2>\n<p>&nbsp;<\/p>\n<p><b>Question 321.<\/b><\/p>\n<p><b>Which authentication approach is commonly used by Cisco Intersight APIs for programmatic access?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> API key-based request signing<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Anonymous HTTP access<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> SNMP community strings<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Telnet password exchange<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Cisco Intersight APIs commonly use API keys together with cryptographic request signing to authenticate programmatic clients. The client typically uses a key identifier and associated private key material to prove its identity when making API requests. This is more appropriate for automation than embedding normal interactive credentials in every request. API key material should be stored securely and protected with least-privilege access controls. Anonymous access, SNMP community strings, and Telnet authentication are not the normal mechanisms for authenticating Intersight REST API requests.<\/span><\/p>\n<p><b>Question 322.<\/b><\/p>\n<p><b>Which practice best protects an Intersight private API key used by a Python automation script?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Store it directly in the source code<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Retrieve it from a secure secret-management system at runtime<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Place it in a public Git repository<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Print it to the console before each request<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Sensitive API key material should be stored outside application source code and retrieved securely at runtime. A dedicated secret-management platform, protected environment mechanism, or approved credential vault provides better access control and reduces the chance of accidental exposure. Hardcoding keys in scripts or storing them in Git can expose them through repository history, backups, or code sharing. Printing keys to logs or consoles also creates unnecessary risk. Automation credentials should use only the privileges required for their intended tasks and should be rotated according to organizational policy.<\/span><\/p>\n<p><b>Question 323.<\/b><\/p>\n<p><b>An Intersight inventory API returns thousands of server objects, but an automation workflow needs only servers from one organization. Which technique should be used?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Retrieve all objects and restart the controller<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Disable pagination<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Apply server-side filtering<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Convert the request to ICMP<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Server-side filtering allows the client to request only objects matching the required organization or other attributes. This reduces network traffic, response size, memory usage, and processing time. Filtering is especially useful in large environments where retrieving every managed object would be inefficient. Pagination may still be required if many filtered objects remain. Disabling pagination or using unrelated protocols does not improve the query. Efficient API design generally combines filtering, field selection, and pagination when supported.<\/span><\/p>\n<p><b>Question 324.<\/b><\/p>\n<p><b>Which HTTP response code most commonly indicates that an API request was accepted and a resource was successfully created?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> 401<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> 403<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> 500<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> 201<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">HTTP 201 Created normally indicates that the server successfully processed a request that resulted in creation of a new resource. A 401 response typically indicates missing or invalid authentication, while 403 indicates insufficient authorization. A 500 response represents an internal server error. Automation should check both the status code and the returned body or resource identifier before assuming the new object is ready for later operations. Different APIs may have platform-specific behavior, so developers should still consult the relevant API documentation.<\/span><\/p>\n<p><b>Question 325.<\/b><\/p>\n<p><b>Which Python programming technique allows a developer to generate a new list by transforming or filtering items from another iterable in a concise expression?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> List comprehension<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Exception chaining<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Class inheritance only<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Module import<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A list comprehension provides a compact way to build a new Python list by iterating over an existing iterable and optionally applying filtering conditions. In infrastructure automation, it can be useful for extracting hostnames from API records, selecting interfaces in a particular state, or transforming returned objects into a simpler structure. Although concise, comprehensions should remain readable; complex logic is often better placed in a normal loop or function. Exception handling, inheritance, and imports serve different purposes.<\/span><\/p>\n<p><b>Question 326.<\/b><\/p>\n<p><b>Which Python data structure is most appropriate for removing duplicate VLAN IDs from a collection automatically?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> String<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Set<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Integer<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Tuple only<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A Python set stores unique values, making it useful when duplicate VLAN IDs, hostnames, addresses, or other identifiers must be removed. Converting a list to a set can eliminate duplicates without requiring manual comparison logic. Sets also support useful operations such as union, intersection, and difference. They are not the best choice when element order or duplicate preservation is important. Lists and tuples preserve sequence behavior, while a string and integer represent different data types entirely.<\/span><\/p>\n<p><b>Question 327.<\/b><\/p>\n<p><b>Which Python mechanism should be used when an automation script wants to catch a timeout separately from other exceptions?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Catch a specific exception type in an <\/span><span style=\"font-weight: 400;\">except<\/span><span style=\"font-weight: 400;\"> clause<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Use only <\/span><span style=\"font-weight: 400;\">pass<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Remove the <\/span><span style=\"font-weight: 400;\">try<\/span><span style=\"font-weight: 400;\"> block<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Catch every condition with <\/span><span style=\"font-weight: 400;\">continue<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Catching specific exception types allows an automation script to respond differently to different failures. A timeout might justify a limited retry with backoff, while an authentication failure might require credential review rather than another immediate attempt. Broad exception handling can hide the true cause of a failure and make troubleshooting difficult. Specific <\/span><span style=\"font-weight: 400;\">except<\/span><span style=\"font-weight: 400;\"> clauses improve clarity and make error handling more intentional. Infrastructure automation should distinguish temporary network failures, invalid responses, authentication problems, and logical validation failures whenever practical.<\/span><\/p>\n<p><b>Question 328.<\/b><\/p>\n<p><b>Which Python feature is best for ensuring that a file containing generated configuration is automatically closed after use?<\/b><\/p>\n<ol>\n<li><b><\/b> <span style=\"font-weight: 400;\">break<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b> <span style=\"font-weight: 400;\">continue<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b> <span style=\"font-weight: 400;\">lambda<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> A <\/span><span style=\"font-weight: 400;\">with<\/span><span style=\"font-weight: 400;\"> context manager<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The <\/span><span style=\"font-weight: 400;\">with<\/span><span style=\"font-weight: 400;\"> statement provides context management and is commonly used when working with files and other resources that need reliable cleanup. When a file is opened inside a <\/span><span style=\"font-weight: 400;\">with<\/span><span style=\"font-weight: 400;\"> block, Python closes it automatically when execution leaves the block, even if an exception occurs. This reduces the chance of leaked file handles or incomplete cleanup. Similar context-manager patterns can be used with locks, sessions, and temporary resources when supported. Loop-control and lambda constructs do not provide automatic resource cleanup.<\/span><\/p>\n<p><b>Question 329.<\/b><\/p>\n<p><b>Which Ansible capability packages modules, roles, and plugins into a distributable namespace for reuse?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Collection<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Handler<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Inventory host<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Registered variable<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">An Ansible collection is a distribution format that can package modules, roles, plugins, and related automation content under a namespace. Collections make it easier to organize and distribute vendor-specific or function-specific automation components. Cisco networking content is commonly delivered through collections that provide modules designed for particular platforms. Handlers run after notifications, inventory identifies managed hosts, and registered variables store task results. Collections help teams maintain reusable automation while avoiding large amounts of custom one-off scripting.<\/span><\/p>\n<p><b>Question 330.<\/b><\/p>\n<p><b>Which Ansible feature allows variables to be defined once for every host in a logical inventory group?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Callback plugin<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Group variables<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Handler notification<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Loop control only<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Group variables allow common values to be assigned to all hosts belonging to an inventory group. For example, every Nexus leaf switch might share connection parameters, NTP servers, or baseline configuration values. This reduces duplicated variable definitions and makes playbooks easier to reuse. Host-specific values can still override group values when necessary. Callback plugins affect output, handlers respond to changes, and loop controls affect task iteration. Proper variable organization is important in larger automation inventories.<\/span><\/p>\n<p><b>Question 331.<\/b><\/p>\n<p><b>Which Ansible practice best supports idempotent configuration management?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Use modules that compare current and desired state before changing resources<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Execute raw configuration commands repeatedly without state checks<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Delete and recreate every object during each run<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Disable change reporting<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Modules that understand current and desired state can determine whether a configuration change is actually required. When the system already matches the requested state, the module can report no change. This is the essence of idempotent automation. Repeated raw commands may create duplicates or unnecessary changes unless carefully designed. Deleting and recreating objects can introduce downtime and unintended side effects. Accurate change reporting is valuable because it allows operators and CI\/CD systems to understand what the automation actually modified.<\/span><\/p>\n<p><b>Question 332.<\/b><\/p>\n<p><b>Which Terraform construct can expose a value, such as a newly created resource identifier, for use by operators or other modules?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Provider block<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Output value<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Backend block<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> State lock<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Terraform outputs expose selected values after configuration evaluation or deployment. They can provide information such as resource identifiers, addresses, names, or values needed by another module or automation stage. Outputs improve module usability by defining a clear interface for information that callers need. Provider blocks configure API integrations, backends control state storage, and state locking prevents concurrent updates. Sensitive outputs should be treated carefully because even values hidden from normal terminal display may still exist in Terraform state.<\/span><\/p>\n<p><b>Question 333.<\/b><\/p>\n<p><b>Which Terraform concept allows one resource to use an attribute exported by another resource, creating an implicit dependency?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Resource reference<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Packet filter<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> State deletion<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> CLI alias<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Terraform resource references allow one resource to consume an attribute produced by another. Terraform uses these references to infer dependencies and determine the correct operation order automatically. For example, a resource may reference the identifier of another object that must exist first. This is preferable to manually sequencing independent commands because Terraform can build a dependency graph. Explicit <\/span><span style=\"font-weight: 400;\">depends_on<\/span><span style=\"font-weight: 400;\"> may be used when a dependency exists but cannot be inferred from attribute references.<\/span><\/p>\n<p><b>Question 334.<\/b><\/p>\n<p><b>Which Terraform meta-argument can be used when a dependency exists but Terraform cannot infer it from resource references?<\/b><\/p>\n<ol>\n<li><b><\/b> <span style=\"font-weight: 400;\">output<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b> <span style=\"font-weight: 400;\">depends_on<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b> <span style=\"font-weight: 400;\">backend<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b> <span style=\"font-weight: 400;\">provider<\/span><span style=\"font-weight: 400;\"> only<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The <\/span><span style=\"font-weight: 400;\">depends_on<\/span><span style=\"font-weight: 400;\"> meta-argument explicitly declares that one resource or module depends on another when the dependency is not already visible through attribute references. Terraform normally infers dependencies automatically, so <\/span><span style=\"font-weight: 400;\">depends_on<\/span><span style=\"font-weight: 400;\"> should be used only when necessary. Correct dependencies help Terraform order creation, modification, and destruction operations safely. Output, backend, and provider configuration serve other purposes. Overusing explicit dependencies can make configurations harder to understand, so natural references are generally preferred when possible.<\/span><\/p>\n<p><b>Question 335.<\/b><\/p>\n<p><b>Which Terraform lifecycle behavior is most appropriate when replacing a production resource must create the new instance before destroying the old one?<\/b><\/p>\n<ol>\n<li><b><\/b> <span style=\"font-weight: 400;\">create_before_destroy<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b> <span style=\"font-weight: 400;\">ignore_changes<\/span><span style=\"font-weight: 400;\"> only<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b> <span style=\"font-weight: 400;\">prevent_destroy<\/span><span style=\"font-weight: 400;\"> only<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b> <span style=\"font-weight: 400;\">count = 0<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The <\/span><span style=\"font-weight: 400;\">create_before_destroy<\/span><span style=\"font-weight: 400;\"> lifecycle behavior instructs Terraform to create the replacement resource before removing the existing one when the provider and resource relationships permit it. This can reduce disruption during replacement operations. It should still be tested because naming constraints, dependencies, or platform behavior may prevent both resources from existing simultaneously. <\/span><span style=\"font-weight: 400;\">prevent_destroy<\/span><span style=\"font-weight: 400;\"> blocks destruction, while <\/span><span style=\"font-weight: 400;\">ignore_changes<\/span><span style=\"font-weight: 400;\"> tells Terraform to disregard selected drift. Lifecycle settings can have significant operational effects and should be used deliberately.<\/span><\/p>\n<p><b>Question 336.<\/b><\/p>\n<p><b>Which Terraform lifecycle setting can protect a critical resource from accidental destruction through a normal plan and apply?<\/b><\/p>\n<ol>\n<li><b><\/b> <span style=\"font-weight: 400;\">replace_triggered_by<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b> <span style=\"font-weight: 400;\">create_before_destroy<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b> <span style=\"font-weight: 400;\">ignore_changes<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b> <span style=\"font-weight: 400;\">prevent_destroy<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The <\/span><span style=\"font-weight: 400;\">prevent_destroy<\/span><span style=\"font-weight: 400;\"> lifecycle setting causes Terraform to reject plans that would destroy the protected resource through normal configuration changes. This provides an additional safeguard for critical infrastructure. It is not an absolute security boundary because an engineer with sufficient access can remove the setting or manipulate state, but it helps prevent accidental deletion. <\/span><span style=\"font-weight: 400;\">create_before_destroy<\/span><span style=\"font-weight: 400;\"> changes replacement ordering, while <\/span><span style=\"font-weight: 400;\">ignore_changes<\/span><span style=\"font-weight: 400;\"> suppresses selected drift handling. Critical resources should also be protected through access controls, review, and CI\/CD policy gates.<\/span><\/p>\n<p><b>Question 337.<\/b><\/p>\n<p><b>Which NETCONF message is exchanged at the beginning of a session to advertise supported capabilities?<\/b><\/p>\n<ol>\n<li><b><\/b> <span style=\"font-weight: 400;\">&lt;hello&gt;<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b> <span style=\"font-weight: 400;\">&lt;commit&gt;<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b> <span style=\"font-weight: 400;\">&lt;edit-config&gt;<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b> <span style=\"font-weight: 400;\">&lt;close-session&gt;<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">NETCONF peers exchange <\/span><span style=\"font-weight: 400;\">&lt;hello&gt;<\/span><span style=\"font-weight: 400;\"> messages when a session begins. These messages advertise the capabilities each side supports, such as candidate configuration, writable-running behavior, validation, notification capabilities, or other extensions. Automation clients should examine these advertised capabilities before assuming a particular workflow is supported. <\/span><span style=\"font-weight: 400;\">&lt;edit-config&gt;<\/span><span style=\"font-weight: 400;\"> changes configuration, <\/span><span style=\"font-weight: 400;\">&lt;commit&gt;<\/span><span style=\"font-weight: 400;\"> activates candidate changes where supported, and <\/span><span style=\"font-weight: 400;\">&lt;close-session&gt;<\/span><span style=\"font-weight: 400;\"> terminates the session. Capability discovery helps automation adapt safely to different network platforms.<\/span><\/p>\n<p><b>Question 338.<\/b><\/p>\n<p><b>Which NETCONF operation can prevent another NETCONF session from modifying a datastore while a coordinated change is being prepared?<\/b><\/p>\n<ol>\n<li><b><\/b> <span style=\"font-weight: 400;\">&lt;get&gt;<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b> <span style=\"font-weight: 400;\">&lt;lock&gt;<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b> <span style=\"font-weight: 400;\">&lt;hello&gt;<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b> <span style=\"font-weight: 400;\">&lt;close-session&gt;<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The <\/span><span style=\"font-weight: 400;\">&lt;lock&gt;<\/span><span style=\"font-weight: 400;\"> operation can reserve a supported NETCONF datastore so other sessions cannot make conflicting modifications while a coordinated update is underway. This is valuable when several related configuration changes need to be applied consistently. After the operation is complete, the client should release the datastore with the corresponding unlock operation. Locking does not replace change control and should not be held longer than necessary because it can block other legitimate automation or administrators.<\/span><\/p>\n<p><b>Question 339.<\/b><\/p>\n<p><b>Which Git workflow is most appropriate when an engineer wants to combine an approved feature branch into the main branch?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Merge<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Clone only<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Tag only<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Reinitialize the repository<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A merge combines changes from one Git branch into another. In an infrastructure automation workflow, an engineer may develop changes on a feature branch, submit them for peer review and CI validation, and then merge the approved branch into the main or production branch. A clone creates a local copy of a repository, while a tag marks a specific revision. Branch-and-merge workflows provide separation between development and production code and support controlled review before deployment.<\/span><\/p>\n<p><b>Question 340.<\/b><\/p>\n<p><b>A CI\/CD pipeline detects that an automation change passes unit tests but fails an integration test against a lab controller. What should the pipeline do?<\/b><\/p>\n<ol>\n<li><b><\/b><span style=\"font-weight: 400;\"> Deploy to production because unit tests passed<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2.<\/b><span style=\"font-weight: 400;\"> Ignore the failed integration test<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3.<\/b><span style=\"font-weight: 400;\"> Stop promotion until the failure is corrected or explicitly handled according to policy<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4.<\/b><span style=\"font-weight: 400;\"> Disable integration testing for future runs<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">An integration-test failure means the complete workflow does not behave as expected when interacting with another component or platform, even if individual functions passed unit tests. A controlled CI\/CD pipeline should therefore stop promotion until the problem is understood and corrected or handled through an approved exception process. Deploying anyway could introduce failures into production infrastructure. Mature automation uses layered testing because syntax checks, unit tests, integration tests, plan reviews, and policy checks each detect different classes of problems.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Cisco CCNP Data Center 300-635 Exam Dumps and Practice Test Dumps &nbsp; Question 321. Which authentication approach is commonly used by Cisco Intersight APIs for programmatic access? API key-based request signing 2. Anonymous HTTP access 3. SNMP community strings 4. Telnet password exchange Correct Answer: 1 Explanation: Cisco Intersight APIs commonly use API [&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\/23918"}],"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=23918"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23918\/revisions"}],"predecessor-version":[{"id":23919,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23918\/revisions\/23919"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=23918"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=23918"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=23918"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}