Question 310
During a change at Willow Data, engineers have selected Cisco Catalyst SD-WAN control-plane management because they need to manage distributed SD-WAN policy using the centralized controller API. Which concrete engineering action must be taken to implement the selected approach, rather than one of the nearby but different designs?
- POST to the documented token endpoint with allowed credentials and use returned token.
- Send GET to the documented /dna/intent/api/v1/network-device with valid X-Auth-Token.
- Address documented Catalyst SD-WAN Manager APIs for policy and inventory.
- Use the documented network-client collection API rather than a device configuration PUT.
Explanation
Correct Answer
C:This action implements Cisco Catalyst SD-WAN control-plane management in the stated environment. To manage distributed SD-WAN policy using the centralized controller API, engineers should address documented Catalyst SD-WAN Manager APIs for policy and inventory; the corresponding acceptance condition is that the manager exposes centrally tracked policy and device state.
Incorrect Answers
A:This engineering action belongs to Catalyst Center authentication, where the purpose is to obtain an API access token before issuing authenticated Intent API requests. Implementing it would not establish Cisco Catalyst SD-WAN control-plane management for the stated requirement to manage distributed SD-WAN policy using the centralized controller API.
B:This engineering action belongs to Catalyst Center inventory query, where the purpose is to collect the managed device list rather than configuring individual devices. Implementing it would not establish Cisco Catalyst SD-WAN control-plane management for the stated requirement to manage distributed SD-WAN policy using the centralized controller API.
D:This engineering action belongs to Meraki network clients listing, where the purpose is to find connected client records associated with one Meraki network. Implementing it would not establish Cisco Catalyst SD-WAN control-plane management for the stated requirement to manage distributed SD-WAN policy using the centralized controller API.
Question 311
Meridian Transit has implemented Cisco Catalyst SD-WAN control-plane management by taking this action: address documented Catalyst SD-WAN Manager APIs for policy and inventory. For the requirement to manage distributed SD-WAN policy using the centralized controller API, which actual observation most directly verifies the desired result?
- Later device-inventory calls include the expected X-Auth-Token header.
- The JSON response collection includes the managed device records.
- The response contains recently observed client identifiers and attributes.
- The manager exposes centrally tracked policy and device state.
Explanation
Correct Answer
D:The observation that the manager exposes centrally tracked policy and device state is tied to the stated implementation of Cisco Catalyst SD-WAN control-plane management. It tests the requested outcome of manage distributed SD-WAN policy using the centralized controller API instead of merely checking an unrelated component.
Incorrect Answers
A:This observation evaluates Catalyst Center authentication, which targets the distinct requirement to obtain an API access token before issuing authenticated Intent API requests. It therefore fails to validate the stated Cisco Catalyst SD-WAN control-plane management outcome: the manager exposes centrally tracked policy and device state.
B:This observation evaluates Catalyst Center inventory query, which targets the distinct requirement to collect the managed device list rather than configuring individual devices. It therefore fails to validate the stated Cisco Catalyst SD-WAN control-plane management outcome: the manager exposes centrally tracked policy and device state.
C:This observation evaluates Meraki network clients listing, which targets the distinct requirement to find connected client records associated with one Meraki network. It therefore fails to validate the stated Cisco Catalyst SD-WAN control-plane management outcome: the manager exposes centrally tracked policy and device state.
Question 312
In Atlas Retail's production-readiness review, Cisco Catalyst SD-WAN control-plane management was selected to manage distributed SD-WAN policy using the centralized controller API. Even if the expected outcome appears correct, which explicitly relevant limitation must the team include in its rollout and monitoring plan?
- Controller availability does not prove all edges have installed a change.
- Token generation is distinct from assuming each inventory call accepts raw username/password.
- An inventory endpoint does not directly apply new configuration to switches.
- Observed clients do not prove devices are currently reachable or authorized.
Explanation
Correct Answer
A:For Cisco Catalyst SD-WAN control-plane management, the pertinent residual constraint is that controller availability does not prove all edges have installed a change. The implementation may satisfy manage distributed SD-WAN policy using the centralized controller API, but this boundary must still be handled in operations.
Incorrect Answers
B:This limitation is associated with Catalyst Center authentication and its separate need to obtain an API access token before issuing authenticated Intent API requests. It is not the most direct operational boundary for the selected Cisco Catalyst SD-WAN control-plane management, whose relevant risk is that controller availability does not prove all edges have installed a change.
C:This limitation is associated with Catalyst Center inventory query and its separate need to collect the managed device list rather than configuring individual devices. It is not the most direct operational boundary for the selected Cisco Catalyst SD-WAN control-plane management, whose relevant risk is that controller availability does not prove all edges have installed a change.
D:This limitation is associated with Meraki network clients listing and its separate need to find connected client records associated with one Meraki network. It is not the most direct operational boundary for the selected Cisco Catalyst SD-WAN control-plane management, whose relevant risk is that controller availability does not prove all edges have installed a change.
Question 313
Metro Services needs to coordinate a service change across multiple vendor devices with rollback-aware transactions. The implementation team is comparing methods that address different problems in its Cisco-automation environment. Which technical approach directly satisfies the stated requirement?
- Catalyst Center authentication
- ACI model-driven policy
- NSO service orchestration
- Meraki network clients listing
Explanation
Correct Answer
C:NSO service orchestration is the suitable approach here: define the service in Cisco NSO with modeled device configuration dependencies. It addresses the requirement to coordinate a service change across multiple vendor devices with rollback-aware transactions; acceptance can be checked when the service configuration is produced consistently across managed devices.
Incorrect Answers
A:Catalyst Center authentication addresses another requirement, namely to obtain an API access token before issuing authenticated Intent API requests. A typical way to do this is to POST to the documented token endpoint with allowed credentials and use returned token; it does not directly address the stated need to coordinate a service change across multiple vendor devices with rollback-aware transactions.
B:ACI model-driven policy addresses another requirement, namely to apply endpoint-group policy through the ACI controller model rather than CLI on every switch. A typical way to do this is to use the APIC policy object model and its documented REST interface; it does not directly address the stated need to coordinate a service change across multiple vendor devices with rollback-aware transactions.
D:Meraki network clients listing addresses another requirement, namely to find connected client records associated with one Meraki network. A typical way to do this is to use the documented network-client collection API rather than a device configuration PUT; it does not directly address the stated need to coordinate a service change across multiple vendor devices with rollback-aware transactions.
Question 314
During a change at Highland Analytics, engineers have selected NSO service orchestration because they need to coordinate a service change across multiple vendor devices with rollback-aware transactions. Which concrete engineering action must be taken to implement the selected approach, rather than one of the nearby but different designs?
- POST to the documented token endpoint with allowed credentials and use returned token.
- Use the APIC policy object model and its documented REST interface.
- Use the documented network-client collection API rather than a device configuration PUT.
- Define the service in Cisco NSO with modeled device configuration dependencies.
Explanation
Correct Answer
D:This action implements NSO service orchestration in the stated environment. To coordinate a service change across multiple vendor devices with rollback-aware transactions, engineers should define the service in Cisco NSO with modeled device configuration dependencies; the corresponding acceptance condition is that the service configuration is produced consistently across managed devices.
Incorrect Answers
A:This engineering action belongs to Catalyst Center authentication, where the purpose is to obtain an API access token before issuing authenticated Intent API requests. Implementing it would not establish NSO service orchestration for the stated requirement to coordinate a service change across multiple vendor devices with rollback-aware transactions.
B:This engineering action belongs to ACI model-driven policy, where the purpose is to apply endpoint-group policy through the ACI controller model rather than CLI on every switch. Implementing it would not establish NSO service orchestration for the stated requirement to coordinate a service change across multiple vendor devices with rollback-aware transactions.
C:This engineering action belongs to Meraki network clients listing, where the purpose is to find connected client records associated with one Meraki network. Implementing it would not establish NSO service orchestration for the stated requirement to coordinate a service change across multiple vendor devices with rollback-aware transactions.
Question 315
Summit University has implemented NSO service orchestration by taking this action: define the service in Cisco NSO with modeled device configuration dependencies. For the requirement to coordinate a service change across multiple vendor devices with rollback-aware transactions, which actual observation most directly verifies the desired result?
- The service configuration is produced consistently across managed devices.
- Later device-inventory calls include the expected X-Auth-Token header.
- The APIC records a fabric policy object with a defined tenant and scope.
- The response contains recently observed client identifiers and attributes.
Explanation
Correct Answer
A:The observation that the service configuration is produced consistently across managed devices is tied to the stated implementation of NSO service orchestration. It tests the requested outcome of coordinate a service change across multiple vendor devices with rollback-aware transactions instead of merely checking an unrelated component.
Incorrect Answers
B:This observation evaluates Catalyst Center authentication, which targets the distinct requirement to obtain an API access token before issuing authenticated Intent API requests. It therefore fails to validate the stated NSO service orchestration outcome: the service configuration is produced consistently across managed devices.
C:This observation evaluates ACI model-driven policy, which targets the distinct requirement to apply endpoint-group policy through the ACI controller model rather than CLI on every switch. It therefore fails to validate the stated NSO service orchestration outcome: the service configuration is produced consistently across managed devices.
D:This observation evaluates Meraki network clients listing, which targets the distinct requirement to find connected client records associated with one Meraki network. It therefore fails to validate the stated NSO service orchestration outcome: the service configuration is produced consistently across managed devices.
Question 316
In Pioneer Energy's production-readiness review, NSO service orchestration was selected to coordinate a service change across multiple vendor devices with rollback-aware transactions. Even if the expected outcome appears correct, which explicitly relevant limitation must the team include in its rollout and monitoring plan?
- Token generation is distinct from assuming each inventory call accepts raw username/password.
- A service model still requires validation of device capabilities and commits.
- APIC policy intent must still be verified against deployed fabric operational state.
- Observed clients do not prove devices are currently reachable or authorized.
Explanation
Correct Answer
B:For NSO service orchestration, the pertinent residual constraint is that a service model still requires validation of device capabilities and commits. The implementation may satisfy coordinate a service change across multiple vendor devices with rollback-aware transactions, but this boundary must still be handled in operations.
Incorrect Answers
A:This limitation is associated with Catalyst Center authentication and its separate need to obtain an API access token before issuing authenticated Intent API requests. It is not the most direct operational boundary for the selected NSO service orchestration, whose relevant risk is that a service model still requires validation of device capabilities and commits.
C:This limitation is associated with ACI model-driven policy and its separate need to apply endpoint-group policy through the ACI controller model rather than CLI on every switch. It is not the most direct operational boundary for the selected NSO service orchestration, whose relevant risk is that a service model still requires validation of device capabilities and commits.
D:This limitation is associated with Meraki network clients listing and its separate need to find connected client records associated with one Meraki network. It is not the most direct operational boundary for the selected NSO service orchestration, whose relevant risk is that a service model still requires validation of device capabilities and commits.
Question 317
Evergreen Labs needs to view compute server inventory across connected UCS domains without logging into each domain. The implementation team is comparing methods that address different problems in its Cisco-automation environment. Which technical approach directly satisfies the stated requirement?
- UCS Manager domain-local operation
- Intersight declarative policy
- NX-OS programmatic interfaces
- Intersight server inventory
Explanation
Correct Answer
D:Intersight server inventory is the suitable approach here: query Cisco Intersight REST API inventory resources using authorized credentials. It addresses the requirement to view compute server inventory across connected UCS domains without logging into each domain; acceptance can be checked when the console returns compute inventory for connected targets.
Incorrect Answers
A:UCS Manager domain-local operation addresses another requirement, namely to apply policy to blade servers inside one UCS domain. A typical way to do this is to use UCS Manager APIs appropriate to the local UCS managed domain; it does not directly address the stated need to view compute server inventory across connected UCS domains without logging into each domain.
B:Intersight declarative policy addresses another requirement, namely to use a reusable server policy on multiple supported Intersight-managed profiles. A typical way to do this is to create the policy object and associate it with appropriate server profiles; it does not directly address the stated need to view compute server inventory across connected UCS domains without logging into each domain.
C:NX-OS programmatic interfaces addresses another requirement, namely to automate supported NX-OS operations without screen-scraping terminal output. A typical way to do this is to use the device's documented model-driven or NX-API interface with authentication; it does not directly address the stated need to view compute server inventory across connected UCS domains without logging into each domain.
Question 318
During a change at Cobalt Manufacturing, engineers have selected Intersight server inventory because they need to view compute server inventory across connected UCS domains without logging into each domain. Which concrete engineering action must be taken to implement the selected approach, rather than one of the nearby but different designs?
- Query Cisco Intersight REST API inventory resources using authorized credentials.
- Use UCS Manager APIs appropriate to the local UCS managed domain.
- Create the policy object and associate it with appropriate server profiles.
- Use the device's documented model-driven or NX-API interface with authentication.
Explanation
Correct Answer
A:This action implements Intersight server inventory in the stated environment. To view compute server inventory across connected UCS domains without logging into each domain, engineers should query Cisco Intersight REST API inventory resources using authorized credentials; the corresponding acceptance condition is that the console returns compute inventory for connected targets.
Incorrect Answers
B:This engineering action belongs to UCS Manager domain-local operation, where the purpose is to apply policy to blade servers inside one UCS domain. Implementing it would not establish Intersight server inventory for the stated requirement to view compute server inventory across connected UCS domains without logging into each domain.
C:This engineering action belongs to Intersight declarative policy, where the purpose is to use a reusable server policy on multiple supported Intersight-managed profiles. Implementing it would not establish Intersight server inventory for the stated requirement to view compute server inventory across connected UCS domains without logging into each domain.
D:This engineering action belongs to NX-OS programmatic interfaces, where the purpose is to automate supported NX-OS operations without screen-scraping terminal output. Implementing it would not establish Intersight server inventory for the stated requirement to view compute server inventory across connected UCS domains without logging into each domain.
Question 319
Northstar Logistics has implemented Intersight server inventory by taking this action: query Cisco Intersight REST API inventory resources using authorized credentials. For the requirement to view compute server inventory across connected UCS domains without logging into each domain, which actual observation most directly verifies the desired result?
- The desired service profile is associated with targeted UCS resources.
- The console returns compute inventory for connected targets.
- Policy associations can be inspected through the Intersight model.
- The API returns machine-readable operational or configuration results.
Explanation
Correct Answer
B:The observation that the console returns compute inventory for connected targets is tied to the stated implementation of Intersight server inventory. It tests the requested outcome of view compute server inventory across connected UCS domains without logging into each domain instead of merely checking an unrelated component.
Incorrect Answers
A:This observation evaluates UCS Manager domain-local operation, which targets the distinct requirement to apply policy to blade servers inside one UCS domain. It therefore fails to validate the stated Intersight server inventory outcome: the console returns compute inventory for connected targets.
C:This observation evaluates Intersight declarative policy, which targets the distinct requirement to use a reusable server policy on multiple supported Intersight-managed profiles. It therefore fails to validate the stated Intersight server inventory outcome: the console returns compute inventory for connected targets.
D:This observation evaluates NX-OS programmatic interfaces, which targets the distinct requirement to automate supported NX-OS operations without screen-scraping terminal output. It therefore fails to validate the stated Intersight server inventory outcome: the console returns compute inventory for connected targets.
Question 320
In Willow Data's production-readiness review, Intersight server inventory was selected to view compute server inventory across connected UCS domains without logging into each domain. Even if the expected outcome appears correct, which explicitly relevant limitation must the team include in its rollout and monitoring plan?
- Domain-local management is different from Intersight multi-domain orchestration.
- Profile deployment may require additional workflow and hardware compatibility checks.
- Unregistered or disconnected targets cannot be assumed visible to Intersight.
- Available NX-API methods depend on platform software and enabled services.
Explanation
Correct Answer
C:For Intersight server inventory, the pertinent residual constraint is that unregistered or disconnected targets cannot be assumed visible to Intersight. The implementation may satisfy view compute server inventory across connected UCS domains without logging into each domain, but this boundary must still be handled in operations.
Incorrect Answers
A:This limitation is associated with UCS Manager domain-local operation and its separate need to apply policy to blade servers inside one UCS domain. It is not the most direct operational boundary for the selected Intersight server inventory, whose relevant risk is that unregistered or disconnected targets cannot be assumed visible to Intersight.
B:This limitation is associated with Intersight declarative policy and its separate need to use a reusable server policy on multiple supported Intersight-managed profiles. It is not the most direct operational boundary for the selected Intersight server inventory, whose relevant risk is that unregistered or disconnected targets cannot be assumed visible to Intersight.
D:This limitation is associated with NX-OS programmatic interfaces and its separate need to automate supported NX-OS operations without screen-scraping terminal output. It is not the most direct operational boundary for the selected Intersight server inventory, whose relevant risk is that unregistered or disconnected targets cannot be assumed visible to Intersight.
DevNet Associate (DEVASC) (200-901) Practice Tests