Module: Requests & Media Servers Activity type: Quiz / retrieval practice Target: ≥80% Objective: Separate service reachability from application health state.
Learn
Questions
In plain words: Read this block, then try the next action. If you feel stuck, tap What this means.
What does arr_monitor_up measure, and which values may it emit?
What two metrics are emitted for a reachable service whose declared_health is critical?
List the warning conditions evaluated after critical conditions.
Do queue_depth=25 and free_space_percent=15 trigger warnings?
Why must HELP and TYPE lines be checked before samples in this lab?
How many sample lines must a successful render contain, and why?
Why is synthetic input preferable to a live ARR API for testing the classification rules?
What should a verifier do when reachable is the string "yes" instead of a Boolean?
In plain words: Big idea: 1.
Learn
After scoring
In plain words: Read this block, then try the next action. If you feel stuck, tap What this means.