Question 640
During a remote branch provisioning pilot at fictional Northshore Cloud, the change record states: A vendor-specific CLI string is applied unchanged to several network operating systems and fails on unsupported command syntax. Which explanation best matches the actual broken dependency?
Explanation
Correct Answer
Cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models. The corresponding repair is: Use inventory capability detection and platform-specific adapters behind a common validated intent model. Acceptance should show: Separate platform acceptance tests reach equivalent approved network intent on each supported operating system without invalid commands. Applied here, the relevant facts are: A vendor-specific CLI string is applied unchanged to several network operating systems and fails on unsupported command syntax. The question asks which explanation best matches the actual broken dependency.
Incorrect Answers
This alternative is a response to another technical cause: The corresponding repair is: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. The reported case instead depends on: The corresponding repair is: Use inventory capability detection and platform-specific adapters behind a common validated intent model. The action that directly addresses it is “Cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models”.
The offered action targets: The corresponding repair is: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. The case facts point instead to: The corresponding repair is: Use inventory capability detection and platform-specific adapters behind a common validated intent model. Implement “Cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models” to address that specific condition.
This alternative is a response to another technical cause: The corresponding repair is: Extract a versioned reusable Terraform module with validated input variables for site-specific network parameters. The reported case instead depends on: The corresponding repair is: Use inventory capability detection and platform-specific adapters behind a common validated intent model. The action that directly addresses it is “Cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models”.