Question 620
Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A scripted provider-edge change is retried blindly after a timeout, duplicating a newly created service instance. Which continuing control best reduces recurrence of this problem?
Explanation
Correct Answer
For this scenario, the observed situation is: A scripted provider-edge change is retried blindly after a timeout, duplicating a newly created service instance. The most directly supported response is: Read current resource state and use a supported idempotent update or request identifier before repeating the operation. Technical basis: Remote writes can succeed before a client times out, making unconditional retries unsafe. Evidence of success: Repeated execution yields exactly one intended service instance and consistent configuration. Ongoing protection: Record operation IDs and reconcile uncertain request completion.
Incorrect Answers
That recurring practice manages a separate exposure: TLS encryption alone does not prove peer identity without certificate validation. The present case instead depends on: Remote writes can succeed before a client times out, making unconditional retries unsafe. The suitable ongoing safeguard is: Record operation IDs and reconcile uncertain request completion.
That recurring practice manages a separate exposure: RESTCONF authorization is distinct from TLS reachability and authentication success. The present case instead depends on: Remote writes can succeed before a client times out, making unconditional retries unsafe. The suitable ongoing safeguard is: Record operation IDs and reconcile uncertain request completion.
Automation concurrency must respect management-plane scale and fault domains. Maintaining that control would not track the failure described here. The relevant risk is: Remote writes can succeed before a client times out, making unconditional retries unsafe. Review this instead: Record operation IDs and reconcile uncertain request completion.