Question 580
At fictional Northshore Cloud, an acceptance review of an inventory reconciliation finds: A team selects a long bespoke Python script for static VLAN declarations that a supported idempotent provider can already manage reliably. Which explanation best matches the actual broken dependency?
Explanation
Correct Answer
Infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs. The corresponding repair is: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations. Acceptance should show: The design review shows the chosen approach fits the resource lifecycle, state ownership and change frequency without redundant infrastructure code. Applied here, the relevant facts are: A team selects a long bespoke Python script for static VLAN declarations that a supported idempotent provider can already manage reliably. The question asks which explanation best matches the actual broken dependency.
Incorrect Answers
The proposed action belongs to the mechanism: The corresponding repair is: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. Here the stated fault follows a different mechanism: The corresponding repair is: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations. The corrective choice is “Infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs”.
That action addresses another technical layer: An HTTP 202 response indicates accepted asynchronous work; a separate completion status is needed to prove the requested device change actually finished. It does not correct this specific failure, which is explained by: The corresponding repair is: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations. The case-matched action is “Infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs”.
This alternative is a response to another technical cause: The corresponding repair is: Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely. The reported case instead depends on: The corresponding repair is: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations. The action that directly addresses it is “Infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs”.