Question 570
A blueprint raises a service anomaly for a virtual network even though all interfaces in its rack are administratively up. Which evidence most directly verifies the intended network outcome?
Explanation
Correct Answer
This directly tests the desired result: confirm the service anomaly clears and the affected workload network passes functional tests. The decisive investigation is to inspect the specific service anomaly, affected objects and intended virtual-network configuration and state. The governing principle is that an Apstra service anomaly indicates observed service state deviates from modeled intent and need not indicate a physical interface failure.
Incorrect Answers
“Confirm the corrective workflow resolves the specific anomaly class without hiding unrelated alarms” is associated with a distinct issue: A support engineer assumes every anomaly is a device-down alarm even when the affected rule is a tenant connectivity expectation. By contrast, the actual problem is: A blueprint raises a service anomaly for a virtual network even though all interfaces in its rack are administratively up. An Apstra service anomaly indicates observed service state deviates from modeled intent and need not indicate a physical interface failure. The direct acceptance evidence is “Confirm the service anomaly clears and the affected workload network passes functional tests”.
The option “Confirm live telemetry returns inside accepted bounds and the probe alert clears with supporting samples” is useful in a different setting: A custom telemetry probe flags a latency anomaly but the blueprint shows no service configuration errors. The case being tested is: A blueprint raises a service anomaly for a virtual network even though all interfaces in its rack are administratively up. An Apstra service anomaly indicates observed service state deviates from modeled intent and need not indicate a physical interface failure. The direct acceptance evidence is “Confirm the service anomaly clears and the affected workload network passes functional tests”.
“Confirm only intended device interfaces or nodes receive the supplemental settings without conflicting commands” is relevant to a different condition: A proprietary monitoring agent needs device-level CLI configuration not generated by standard Apstra intents. The stated question instead concerns: A blueprint raises a service anomaly for a virtual network even though all interfaces in its rack are administratively up. An Apstra service anomaly indicates observed service state deviates from modeled intent and need not indicate a physical interface failure. The direct acceptance evidence is “Confirm the service anomaly clears and the affected workload network passes functional tests”.