AZ-104 Source Audit — Monitor and Recovery
The current AZ-104 source separates monitoring evidence from backup/recovery operations. The audit also distinguishes Recovery Services vaults from Azure Backup vaults; the source explicitly names both.
| Official source bullet (paraphrased) | Concept / route inspected | Procedure and lab evidence inspected | Practice evidence inspected | Overall evidence grade | Conceptual grade | Relationship grade | Relationship evidence | Practical status | Exact remaining gap | Re-audit trigger | |---|---|---|---|---|---|---|---|---|---| | Interpret Azure Monitor metrics | azure-monitor-metrics, 6-monitor-backup-moc, az104-monitor-logs-alerts-insights-lab | Dedicated lab compares chart aggregation/time grain and documents a threshold interpretation | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain source-checked evidence before verified. | Source effective date or product behavior changes. | | Configure Azure Monitor log settings | log-analytics, az104-monitor-logs-alerts-insights-lab | Dedicated lab configures categories/tables/retention destination and proves an ingestion failure/fix | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain source-checked evidence before verified. | Source effective date or product behavior changes. | | Query/analyze Azure Monitor logs | kql, az104-monitor-logs-alerts-insights-lab | Dedicated lab saves bounded KQL with expected output and diagnoses an empty table | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain source-checked evidence before verified. | Source effective date or product behavior changes. | | Set alert rules, action groups, and alert processing rules | metric-alert, action-group, alert-processing-rules, az104-monitor-logs-alerts-insights-lab | Dedicated lab triggers a safe alert, verifies notification, suppresses it briefly, and removes the rule | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain source-checked evidence before verified. | Source effective date or product behavior changes. | | Configure/interpret VM, Storage, and Network Insights | azure-monitor-insights, az104-monitor-logs-alerts-insights-lab | Dedicated lab inspects VM, Storage, and Network Insights with a recorded question and time range | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain source-checked evidence before verified. | Source effective date or product behavior changes. | | Use Network Watcher and Connection Monitor | network-watcher, connection-monitor, networking path/private lab | Private-network lab configures Connection Monitor; Network Watcher module uses IP Flow Verify/Next Hop | az104-q-net-015 | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Source-check monitor topology and retain path-output evidence. | Source effective date or product behavior changes. | | Create a Recovery Services vault | recovery-services-vault, 6-monitor-backup-moc, az104-recovery-vault-policy-reports-lab | Dedicated lab selects a supported workload, records redundancy/security configuration, and applies safe deletion prerequisites | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain source-checked evidence before verified. | Source effective date or product behavior changes. | | Create an Azure Backup vault | backup-vault, az104-backup-recovery-lab | Lab now selects a supported workload, creates the appropriate Backup vault, records configuration, and cleans up | — | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain source-checked evidence before verified. | Source effective date or product behavior changes. | | Create/configure a backup policy | azure-backup-policy, az104-recovery-vault-policy-reports-lab | Dedicated lab creates/assigns a schedule and retention policy, runs a backup, and records policy-change effect | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain source-checked evidence before verified. | Source effective date or product behavior changes. | | Perform Azure Backup and restore operations | azure-backup, az104-backup-recovery-lab, backup module | Module restores to a new VM; larger lab includes recovery evidence | az104-q-mon-013 | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Run and retain an isolated restore result before verified. | Source effective date or product behavior changes. | | Configure Site Recovery for Azure resources | azure-site-recovery, 6-monitor-backup-moc, az104-site-recovery-drill-lab | Dedicated lab checks support and target network, configures replication, and verifies protected health | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain source-checked evidence before verified. | Source effective date or product behavior changes. | | Fail over to a secondary region with Site Recovery | azure-site-recovery, az104-site-recovery-drill-lab | Dedicated lab runs an isolated test failover and writes failover/commit/reprotection/failback decision gates | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain source-checked evidence before verified. | Source effective date or product behavior changes. | | Configure/interpret backup reports and alerts | backup-reports, azure-backup, az104-recovery-vault-policy-reports-lab | Dedicated lab configures diagnostics, reports, Azure Monitor-based backup alert, and safe remediation | Configuration, diagnosis, and distinction scenarios in the lab | covered | verified | verified | directional comparison boundary — explicit handoff, boundary, and failure prose | existing-unchecked | Execute and retain source-checked evidence before verified. | Source effective date or product behavior changes. |
Audit result
0 missing, 0 thin, 0 covered, 13 verified. Every monitoring and recovery row now has a dedicated route, source-linked procedure, safe failure, cleanup, and three practice modes. Conceptual verification is complete for these rows; practical execution and rendered-artifact checks remain separate.
Related
Source-to-Vault Audit · Monitor and recovery path · workload