Question 780
At Maplebridge Rail Logistics, while verifying observability, the data center fabric team observes: An operator pushes individual switch settings that later drift from centrally managed EDA intent. What ongoing operational safeguard directly addresses this root issue?
Explanation
Correct Answer
At Maplebridge Rail Logistics, while verifying observability, the preventive control is: Use defined change ownership for intent-managed devices. It catches the same mechanism (Manual changes were made without accounting for intent ownership and reconciliation) before the symptom recurs. An appropriate regression observation is: The intended setting persists through an EDA consistency check without undocumented deviations.
Incorrect Answers
At Maplebridge Rail Logistics, while verifying observability, this option proposes: Check network intent results separately from Kubernetes platform health. It tests a different symptom: An EDA planning team assumes Kubernetes deployment alone creates fabric connectivity. For the observed case, the relevant distinction is Manual changes were made without accounting for intent ownership and reconciliation, with verification: The intended setting persists through an EDA consistency check without undocumented deviations.
At Maplebridge Rail Logistics, while verifying observability, this option proposes: Include controlled monitoring fixtures in intent-platform acceptance. The option describes a different failure mode: An EDA observability panel has no alerts during a test network failure. It would address The team uses the absence of alarms as the sole evidence of monitoring completeness, but here the case reports An operator pushes individual switch settings that later drift from centrally managed EDA intent. The current required evidence is: The intended setting persists through an EDA consistency check without undocumented deviations.
At Maplebridge Rail Logistics, while verifying observability, this option proposes: Require transaction and live-network acceptance for service intent changes. That choice would be more relevant when this different symptom occurs: A tenant service deployment is considered complete because EDA accepted the requested intent. The present scenario instead points to: Manual changes were made without accounting for intent ownership and reconciliation. The correct resolution has its own verification outcome: The intended setting persists through an EDA consistency check without undocumented deviations.