5.0 Monitor and maintain Azure resources AZ-104 Practice Quiz

• A. Review the metric namespace, aggregation, time range, and dimensions before deciding whether the resource is unhealthy
• B. Use the Azure Pricing Calculator as a real-time billing alarm system
• C. Use Application Insights only for production and skip dev/test environments
• D. Invite a B2B guest by creating a new Entra ID user with a temporary password

Metric interpretation depends on what is being measured, how it is aggregated, and over which time window.

• A. Correlate platform metrics with logs when a metric indicates a possible service issue
• B. Use Activity Log alerts to monitor application performance metrics
• C. Use a security group as a distribution list for external mail
• D. Treat tenant root group ownership as the default scope for all role assignments

Metrics show trends and thresholds, while logs can provide event-level details.

• A. Use Azure Blueprints as a real-time monitoring solution
• B. Compare CPU, memory, disk, and network metrics against the workload baseline before resizing a resource
• C. Move resources between subscriptions without checking resource-type support
• D. Configure backup reports without delegating ownership to a recipient

A baseline helps distinguish normal workload variation from a real capacity issue.

• A. Use a CanNotDelete lock on every resource by default
• B. Review availability and latency metrics for services that have user-facing performance requirements
• C. Assume resource health proves application endpoint connectivity
• D. Use dynamic membership rules without enabling the required Microsoft Entra license

User-facing services should be monitored for health and responsiveness, not only resource usage.

• A. Disable soft delete in the vault to reduce storage costs
• B. Create a diagnostic setting that sends resource logs and metrics to a Log Analytics workspace, storage account, or event hub
• C. Apply tags and expect them to block noncompliant deployments by themselves
• D. Use Azure Hybrid Benefit on free Linux distributions that have no commercial license

Diagnostic settings control where Azure resource logs and metrics are exported.

• A. Use a single shared admin account for all team members to simplify access
• B. Assign licenses by editing CSV files instead of using group-based licensing
• C. Use dimensions to separate metric values by instance, disk, endpoint, or other resource-specific labels when available
• D. Configure Self-Service Password Reset (SSPR) only for global administrators

Dimensions help identify which part of a resource is causing the metric change.

• A. Pay full PAYG rates for stable production VMs running 24/7 for years
• B. Use email alone for critical backup failure notifications without escalation
• C. Use Azure Monitor metrics to build dashboards and alerts for critical resource health indicators
• D. Create a Recovery Services vault in a different geography from the resources you protect

Metrics provide near-real-time numerical telemetry for monitoring and alerting.

• A. Set every alert severity to Sev0 (critical) regardless of business impact
• B. Skip cross-region restore for critical workloads to reduce vault complexity
• C. Use SSPR without registering authentication methods for users
• D. Check metric granularity and aggregation when a chart does not match the expected spike

Averages, totals, minimums, and maximums can show different views of the same telemetry.