8 Observability and Automation Testing Online Quiz Questions

Treat the successful API response as proof that the service is healthy.

Check device acknowledgements and operational state, then verify service behavior.

Skip post-deployment checks if configuration syntax passed validation.

Replace service checks with a larger rollout to gather more data.

Use subscriptions to receive selected datastore updates as they occur or at configured intervals.

Poll less frequently, because polling provides lower detection delay than push.

Avoid collecting telemetry until after a change is rolled back.

Use push only for external events, not datastore updates.

Define rollback only after a service objective has already been breached.

Use a successful configuration commit as the only rollback criterion.

Specify measurable acceptance criteria and explicit conditions for stopping or rolling back.

Allow the automation to continue unless every device becomes unreachable.

Interface error counts over time

A record of a routing adjacency change

A request path followed across an orchestrator, controller, and device

Packet-loss measurements over time

Limit which identities or systems are authorized to make changes.

Roll out changes in stages where practical.

Allow corrective actions to proceed without timeouts or limits.

Define explicit rollback criteria and retain audit logs.

True

False

True

False

Store every signal without identifiers so collection stays simple.

Correlate signals using device, service, change, and time identifiers.

Use only a single metric and discard event records.

Correlate signals only after deciding that the automation caused the symptom.

A metric showing interface error counts over time

A log recording a configuration commit

A record following an API request through an orchestrator, controller, and device

A periodic poll of a device's current configuration

To prove that a successful API response guarantees healthy service

To test interactions, failure cases, and platform-specific behavior before broad rollout

To avoid defining acceptance criteria for the change

To replace all post-deployment checks

Validate inputs and responses, check syntax and constraints, and review the intended diff

Rely on service telemetry after deployment and skip reviewing the intended changes

Treat a successful API response as proof that the configuration is correct

Run a rollback only after a service objective has already been breached

True

False

Deploy to every device at once and check only whether the API call returned successfully

Skip operational checks because the configuration was accepted

Use a small canary or staged rollout and check device acknowledgements and operational state

Wait until after the rollout to decide whether it should have been staged