Question 59 — AZ-104 Practice Exam 13
For each Azure Monitor concept below, drag it to the correct definition.
Each item may be used once, more than once, or not at all.
| Option | Correct Match |
|---|---|
| Uses a fixed threshold that you specify | [Gap 1] |
| Uses machine learning; no hard threshold | [Gap 2] |
| Requires a look-back period and number of violations | [Gap 3] |
Apply one alert rule to multiple instances by naming instances or using * |
[Gap 4] |
| Monitors multiple resources in one Azure region (currently limited to VMs) | [Gap 5] |
| Alert is evaluated and fired individually for each triggering resource | [Gap 6] |
- Dynamic metric alert
- Severity level
- Dimensions
- Static metric alert
- Scaling metric alert
- Activity log alert
Correct answers
- Gap 1: Static metric alert
- Gap 2: Dynamic metric alert
- Gap 3: Dynamic metric alert
- Gap 4: Dimensions
- Gap 5: Scaling metric alert
- Gap 6: Scaling metric alert
Explanations
Correct Matches
Static metric alert — Uses a fixed threshold you define; the alert triggers when data exceeds that threshold.
Dynamic metric alert — Uses Azure ML to adjust thresholds automatically; it has no hard threshold and requires both a look-back period and a number of violations.
Dimensions — Lets one metric alert rule target many related instances by explicitly naming them or using the * wildcard.
Scaling metric alert — Allows monitoring multiple resources in a single Azure region (currently limited to Azure VMs); alerts are still evaluated per resource that breaches the condition.
Unused Item(s)
Activity log alert — Based on resource state changes, not metric thresholds.
Severity level — Part of alert details, not a concept that matches these definitions.