Question 530
During a change at Meridian Transit, engineers have selected Declarative device intent because they need to keep configuration automation consistent across multiple supported vendor targets. Which concrete engineering action must be taken to implement the selected approach, rather than one of the nearby but different designs?
- Normalize modeled operational state before comparing it with the desired policy.
- Model the desired outcome and let a controller reconcile supported device configuration.
- Consume the supported YANG model to build a typed configuration payload.
- Use NSO's service model with explicit service parameters.
Explanation
Correct Answer
B:This action implements Declarative device intent in the stated environment. To keep configuration automation consistent across multiple supported vendor targets, engineers should model the desired outcome and let a controller reconcile supported device configuration; the corresponding acceptance condition is that repeat execution converges toward the same intended configuration.
Incorrect Answers
A:This engineering action belongs to Structured network state comparison, where the purpose is to compare desired and observed interface state across supported devices. Implementing it would not establish Declarative device intent for the stated requirement to keep configuration automation consistent across multiple supported vendor targets.
C:This engineering action belongs to Schema-driven automation, where the purpose is to generate device configuration from defined YANG objects rather than arbitrary screen-scraping. Implementing it would not establish Declarative device intent for the stated requirement to keep configuration automation consistent across multiple supported vendor targets.
D:This engineering action belongs to Cisco NSO multi-device service, where the purpose is to deploy a modeled VPN service across several routers consistently. Implementing it would not establish Declarative device intent for the stated requirement to keep configuration automation consistent across multiple supported vendor targets.
Question 531
Atlas Retail has implemented Declarative device intent by taking this action: model the desired outcome and let a controller reconcile supported device configuration. For the requirement to keep configuration automation consistent across multiple supported vendor targets, which actual observation most directly verifies the desired result?
- Differences show specific leaves rather than ambiguous CLI text changes.
- The candidate configuration validates against the expected schema.
- Repeat execution converges toward the same intended configuration.
- Device configurations are derived consistently from one service request.
Explanation
Correct Answer
C:The observation that repeat execution converges toward the same intended configuration is tied to the stated implementation of Declarative device intent. It tests the requested outcome of keep configuration automation consistent across multiple supported vendor targets instead of merely checking an unrelated component.
Incorrect Answers
A:This observation evaluates Structured network state comparison, which targets the distinct requirement to compare desired and observed interface state across supported devices. It therefore fails to validate the stated Declarative device intent outcome: repeat execution converges toward the same intended configuration.
B:This observation evaluates Schema-driven automation, which targets the distinct requirement to generate device configuration from defined YANG objects rather than arbitrary screen-scraping. It therefore fails to validate the stated Declarative device intent outcome: repeat execution converges toward the same intended configuration.
D:This observation evaluates Cisco NSO multi-device service, which targets the distinct requirement to deploy a modeled VPN service across several routers consistently. It therefore fails to validate the stated Declarative device intent outcome: repeat execution converges toward the same intended configuration.
Question 532
In Coastal Operations's production-readiness review, Declarative device intent was selected to keep configuration automation consistent across multiple supported vendor targets. Even if the expected outcome appears correct, which explicitly relevant limitation must the team include in its rollout and monitoring plan?
- State can change while being observed, so capture timing matters.
- Models can differ across IOS XE releases and optional feature support.
- NSO service logic still needs reconciliation when a device rejects its config.
- A model cannot make unsupported device features available.
Explanation
Correct Answer
D:For Declarative device intent, the pertinent residual constraint is that a model cannot make unsupported device features available. The implementation may satisfy keep configuration automation consistent across multiple supported vendor targets, but this boundary must still be handled in operations.
Incorrect Answers
A:This limitation is associated with Structured network state comparison and its separate need to compare desired and observed interface state across supported devices. It is not the most direct operational boundary for the selected Declarative device intent, whose relevant risk is that a model cannot make unsupported device features available.
B:This limitation is associated with Schema-driven automation and its separate need to generate device configuration from defined YANG objects rather than arbitrary screen-scraping. It is not the most direct operational boundary for the selected Declarative device intent, whose relevant risk is that a model cannot make unsupported device features available.
C:This limitation is associated with Cisco NSO multi-device service and its separate need to deploy a modeled VPN service across several routers consistently. It is not the most direct operational boundary for the selected Declarative device intent, whose relevant risk is that a model cannot make unsupported device features available.
Question 533
Highland Analytics needs to apply a consistent network intent across many managed switches. The implementation team is comparing methods that address different problems in its Cisco-automation environment. Which technical approach directly satisfies the stated requirement?
- Controller versus device state mismatch
- Controller-level policy change
- Direct device-level troubleshooting
- Idempotent configuration
Explanation
Correct Answer
B:Controller-level policy change is the suitable approach here: submit the change to the authorized management controller API. It addresses the requirement to apply a consistent network intent across many managed switches; acceptance can be checked when the controller tracks the intended policy and deployment jobs.
Incorrect Answers
A:Controller versus device state mismatch addresses another requirement, namely to investigate a controller showing compliant intent while a switch reports stale configuration. A typical way to do this is to compare controller desired state with device operational/configuration data; it does not directly address the stated need to apply a consistent network intent across many managed switches.
C:Direct device-level troubleshooting addresses another requirement, namely to inspect one router's operational interface state during a targeted outage. A typical way to do this is to query the router's supported device API for that interface; it does not directly address the stated need to apply a consistent network intent across many managed switches.
D:Idempotent configuration addresses another requirement, namely to rerun an automation after an interrupted deployment without unintended repeated changes. A typical way to do this is to use declarative modules that report unchanged when desired state already holds; it does not directly address the stated need to apply a consistent network intent across many managed switches.
Question 534
During a change at Summit University, engineers have selected Controller-level policy change because they need to apply a consistent network intent across many managed switches. Which concrete engineering action must be taken to implement the selected approach, rather than one of the nearby but different designs?
- Compare controller desired state with device operational/configuration data.
- Query the router's supported device API for that interface.
- Submit the change to the authorized management controller API.
- Use declarative modules that report unchanged when desired state already holds.
Explanation
Correct Answer
C:This action implements Controller-level policy change in the stated environment. To apply a consistent network intent across many managed switches, engineers should submit the change to the authorized management controller API; the corresponding acceptance condition is that the controller tracks the intended policy and deployment jobs.
Incorrect Answers
A:This engineering action belongs to Controller versus device state mismatch, where the purpose is to investigate a controller showing compliant intent while a switch reports stale configuration. Implementing it would not establish Controller-level policy change for the stated requirement to apply a consistent network intent across many managed switches.
B:This engineering action belongs to Direct device-level troubleshooting, where the purpose is to inspect one router's operational interface state during a targeted outage. Implementing it would not establish Controller-level policy change for the stated requirement to apply a consistent network intent across many managed switches.
D:This engineering action belongs to Idempotent configuration, where the purpose is to rerun an automation after an interrupted deployment without unintended repeated changes. Implementing it would not establish Controller-level policy change for the stated requirement to apply a consistent network intent across many managed switches.
Question 535
Pioneer Energy has implemented Controller-level policy change by taking this action: submit the change to the authorized management controller API. For the requirement to apply a consistent network intent across many managed switches, which actual observation most directly verifies the desired result?
- The discrepancy reveals an unapplied or failed deployment.
- The output reflects the target device's own state instead of only controller inventory.
- A second execution has no unnecessary actions on already-correct resources.
- The controller tracks the intended policy and deployment jobs.
Explanation
Correct Answer
D:The observation that the controller tracks the intended policy and deployment jobs is tied to the stated implementation of Controller-level policy change. It tests the requested outcome of apply a consistent network intent across many managed switches instead of merely checking an unrelated component.
Incorrect Answers
A:This observation evaluates Controller versus device state mismatch, which targets the distinct requirement to investigate a controller showing compliant intent while a switch reports stale configuration. It therefore fails to validate the stated Controller-level policy change outcome: the controller tracks the intended policy and deployment jobs.
B:This observation evaluates Direct device-level troubleshooting, which targets the distinct requirement to inspect one router's operational interface state during a targeted outage. It therefore fails to validate the stated Controller-level policy change outcome: the controller tracks the intended policy and deployment jobs.
C:This observation evaluates Idempotent configuration, which targets the distinct requirement to rerun an automation after an interrupted deployment without unintended repeated changes. It therefore fails to validate the stated Controller-level policy change outcome: the controller tracks the intended policy and deployment jobs.
Question 536
In Brookfield Systems's production-readiness review, Controller-level policy change was selected to apply a consistent network intent across many managed switches. Even if the expected outcome appears correct, which explicitly relevant limitation must the team include in its rollout and monitoring plan?
- Controller acceptance alone does not prove every switch has applied the policy.
- Reissuing intent without root-cause checks can repeatedly fail.
- A device query should not bypass controller change-control rules for writes.
- Idempotence must be verified with modules and external side effects.
Explanation
Correct Answer
A:For Controller-level policy change, the pertinent residual constraint is that controller acceptance alone does not prove every switch has applied the policy. The implementation may satisfy apply a consistent network intent across many managed switches, but this boundary must still be handled in operations.
Incorrect Answers
B:This limitation is associated with Controller versus device state mismatch and its separate need to investigate a controller showing compliant intent while a switch reports stale configuration. It is not the most direct operational boundary for the selected Controller-level policy change, whose relevant risk is that controller acceptance alone does not prove every switch has applied the policy.
C:This limitation is associated with Direct device-level troubleshooting and its separate need to inspect one router's operational interface state during a targeted outage. It is not the most direct operational boundary for the selected Controller-level policy change, whose relevant risk is that controller acceptance alone does not prove every switch has applied the policy.
D:This limitation is associated with Idempotent configuration and its separate need to rerun an automation after an interrupted deployment without unintended repeated changes. It is not the most direct operational boundary for the selected Controller-level policy change, whose relevant risk is that controller acceptance alone does not prove every switch has applied the policy.
Question 537
Cobalt Manufacturing needs to inspect one router's operational interface state during a targeted outage. The implementation team is comparing methods that address different problems in its Cisco-automation environment. Which technical approach directly satisfies the stated requirement?
- Controller-level policy change
- Controller versus device state mismatch
- Direct device-level troubleshooting
- Terraform resource graph
Explanation
Correct Answer
C:Direct device-level troubleshooting is the suitable approach here: query the router's supported device API for that interface. It addresses the requirement to inspect one router's operational interface state during a targeted outage; acceptance can be checked when the output reflects the target device's own state instead of only controller inventory.
Incorrect Answers
A:Controller-level policy change addresses another requirement, namely to apply a consistent network intent across many managed switches. A typical way to do this is to submit the change to the authorized management controller API; it does not directly address the stated need to inspect one router's operational interface state during a targeted outage.
B:Controller versus device state mismatch addresses another requirement, namely to investigate a controller showing compliant intent while a switch reports stale configuration. A typical way to do this is to compare controller desired state with device operational/configuration data; it does not directly address the stated need to inspect one router's operational interface state during a targeted outage.
D:Terraform resource graph addresses another requirement, namely to provision dependent resources in an order consistent with references. A typical way to do this is to use Terraform resource attributes and dependencies to build its execution graph; it does not directly address the stated need to inspect one router's operational interface state during a targeted outage.
Question 538
During a change at Northstar Logistics, engineers have selected Direct device-level troubleshooting because they need to inspect one router's operational interface state during a targeted outage. Which concrete engineering action must be taken to implement the selected approach, rather than one of the nearby but different designs?
- Submit the change to the authorized management controller API.
- Compare controller desired state with device operational/configuration data.
- Use Terraform resource attributes and dependencies to build its execution graph.
- Query the router's supported device API for that interface.
Explanation
Correct Answer
D:This action implements Direct device-level troubleshooting in the stated environment. To inspect one router's operational interface state during a targeted outage, engineers should query the router's supported device API for that interface; the corresponding acceptance condition is that the output reflects the target device's own state instead of only controller inventory.
Incorrect Answers
A:This engineering action belongs to Controller-level policy change, where the purpose is to apply a consistent network intent across many managed switches. Implementing it would not establish Direct device-level troubleshooting for the stated requirement to inspect one router's operational interface state during a targeted outage.
B:This engineering action belongs to Controller versus device state mismatch, where the purpose is to investigate a controller showing compliant intent while a switch reports stale configuration. Implementing it would not establish Direct device-level troubleshooting for the stated requirement to inspect one router's operational interface state during a targeted outage.
C:This engineering action belongs to Terraform resource graph, where the purpose is to provision dependent resources in an order consistent with references. Implementing it would not establish Direct device-level troubleshooting for the stated requirement to inspect one router's operational interface state during a targeted outage.
Question 539
Willow Data has implemented Direct device-level troubleshooting by taking this action: query the router's supported device API for that interface. For the requirement to inspect one router's operational interface state during a targeted outage, which actual observation most directly verifies the desired result?
- The output reflects the target device's own state instead of only controller inventory.
- The controller tracks the intended policy and deployment jobs.
- The discrepancy reveals an unapplied or failed deployment.
- Dependent resources wait for prerequisite resource creation.
Explanation
Correct Answer
A:The observation that the output reflects the target device's own state instead of only controller inventory is tied to the stated implementation of Direct device-level troubleshooting. It tests the requested outcome of inspect one router's operational interface state during a targeted outage instead of merely checking an unrelated component.
Incorrect Answers
B:This observation evaluates Controller-level policy change, which targets the distinct requirement to apply a consistent network intent across many managed switches. It therefore fails to validate the stated Direct device-level troubleshooting outcome: the output reflects the target device's own state instead of only controller inventory.
C:This observation evaluates Controller versus device state mismatch, which targets the distinct requirement to investigate a controller showing compliant intent while a switch reports stale configuration. It therefore fails to validate the stated Direct device-level troubleshooting outcome: the output reflects the target device's own state instead of only controller inventory.
D:This observation evaluates Terraform resource graph, which targets the distinct requirement to provision dependent resources in an order consistent with references. It therefore fails to validate the stated Direct device-level troubleshooting outcome: the output reflects the target device's own state instead of only controller inventory.
Question 540
In Meridian Transit's production-readiness review, Direct device-level troubleshooting was selected to inspect one router's operational interface state during a targeted outage. Even if the expected outcome appears correct, which explicitly relevant limitation must the team include in its rollout and monitoring plan?
- Controller acceptance alone does not prove every switch has applied the policy.
- A device query should not bypass controller change-control rules for writes.
- Reissuing intent without root-cause checks can repeatedly fail.
- Implicit dependencies cannot be inferred if references are hidden in arbitrary shell scripts.
Explanation
Correct Answer
B:For Direct device-level troubleshooting, the pertinent residual constraint is that a device query should not bypass controller change-control rules for writes. The implementation may satisfy inspect one router's operational interface state during a targeted outage, but this boundary must still be handled in operations.
Incorrect Answers
A:This limitation is associated with Controller-level policy change and its separate need to apply a consistent network intent across many managed switches. It is not the most direct operational boundary for the selected Direct device-level troubleshooting, whose relevant risk is that a device query should not bypass controller change-control rules for writes.
C:This limitation is associated with Controller versus device state mismatch and its separate need to investigate a controller showing compliant intent while a switch reports stale configuration. It is not the most direct operational boundary for the selected Direct device-level troubleshooting, whose relevant risk is that a device query should not bypass controller change-control rules for writes.
D:This limitation is associated with Terraform resource graph and its separate need to provision dependent resources in an order consistent with references. It is not the most direct operational boundary for the selected Direct device-level troubleshooting, whose relevant risk is that a device query should not bypass controller change-control rules for writes.
DevNet Associate (DEVASC) (200-901) Practice Tests