Question 100
A core network change board wants to avoid: An external Python script posts interface descriptions to a router API but uses an incorrect content type and receives 415 Unsupported Media Type. Which ongoing safeguard fits best?
Explanation
Correct Answer
Contract-test request headers and payload formats against each platform API version. This helps prevent recurrence of the issue: An external Python script posts interface descriptions to a router API but uses an incorrect content type and receives 415 Unsupported Media Type. Acceptance evidence should be: A sandbox edit returns the expected successful response and a readback shows only the intended interface description changed.
Incorrect Answers
Define task completion and readback gates for asynchronous API mutations. That is a sensible control for ANOTHER scenario: A controller automation receives HTTP 202 from an IOS XR change job and records completion even though the backend still reports pending work. It is less targeted to this issue than: Contract-test request headers and payload formats against each platform API version.
Require read-before-write or idempotency controls on mutating API workflows. That is a sensible control for ANOTHER scenario: A script uses an unscoped POST endpoint and accidentally creates multiple static routes when its retry logic repeats a successful but slow request. It is less targeted to this issue than: Contract-test request headers and payload formats against each platform API version.
Include hostname, expiry and certificate chain tests in gNMI collector deployment. That is a sensible control for ANOTHER scenario: A router publishes gNMI dial-out telemetry to a collector whose TLS certificate hostname does not match the configured endpoint and fails the handshake. It is less targeted to this issue than: Contract-test request headers and payload formats against each platform API version.