Timedora
Free Online Flashcard Deck

8 Observability and Automation Testing Free Online FlashCards

Study 8 Observability and Automation Testing with 12 free online flashcards. Review key terms, definitions, and concepts with this interactive flashcard deck.

12 cards
01
Front

What is network telemetry?

Back

Telemetry is network data and the methods used to generate, export, collect, correlate, and use it.

02
Front

How do push telemetry and polling differ?

Back

Push sends updates when changes occur or at configured intervals, reducing detection delay. Polling supports periodic checks and simple queries.

03
Front

How do metrics, logs, and traces differ?

Back

Metrics are numeric measurements over time; logs record events; traces follow an operation across components.

04
Front

What does monitoring do, and what is an SLI?

Back

Monitoring interprets observations against expected behavior. An SLI is a measurable service property, such as reachability, latency, or loss.

05
Front

What should automation tests check before deployment?

Back

Before deployment, validate inputs and API responses, check syntax, schemas, and policy constraints, and review the intended changes.

06
Front

What is idempotency in network automation?

Back

Idempotency means repeating the same desired-state automation causes no unintended additional change. It makes retries safer and can expose drift or faulty state handling.

07
Front

What are the main steps in a network automation feedback loop?

Back

A feedback loop specifies measurable criteria, applies a change, observes telemetry, compares outcomes with criteria, responds to failures, and uses results to improve future automation.

08
Front

What can telemetry reveal about the three network planes?

Back

Management-plane data describes configuration and device health; control-plane data describes routing state; forwarding-plane data includes traffic, loss, and queue statistics.

09
Front

Why correlate telemetry signals with device, service, change, and time?

Back

Correlating signals by device, service, change, and time helps connect a symptom to the automation that preceded it.

10
Front

What makes an alert useful?

Back

Alerts should generally identify service-affecting symptoms, include useful context, and provide a route to diagnostic information—not report every low-level fluctuation.

11
Front

Why must the monitoring pipeline itself be monitored?

Back

Monitoring its own collectors and alert paths helps reveal when missing observations or broken alerts make a dashboard misleading.

12
Front

Why test changes in a lab or representative environment?

Back

Testing in a lab or representative environment can expose interactions, failure cases, and platform-specific behavior before broad rollout.