mcAfee Secure Website
23

Microsoft AZ-104 Bundle

Exam Code: AZ-104

Exam Name Microsoft Azure Administrator

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Azure Administrator Associate

AZ-104 Training Materials $44.99

Reliable & Actual Study Materials for AZ-104 Exam Success

The Latest AZ-104 Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    AZ-104 Questions & Answers

    606 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • 25
    AZ-104 Video Course

    AZ-104 Training Course

    132 Video Lectures

    Based on Real Life Scenarios which you will encounter in exam and learn by working with real equipment.

  • exam =30
    Study Guide

    AZ-104 Study Guide

    458 PDF Pages

    Study Guide developed by industry experts who have written exams in the past. They are technology-specific IT certification researchers with at least a decade of experience at Fortune 500 companies.

exam =32

Microsoft Azure Administrator (AZ-104) Practice Tests

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Microsoft Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    606 Questions

    $124.99
    exam =35
  • exam =37
    AZ-104 Video Course

    Training Course

    132 Video Lectures

    $39.99
  • exam =36
    Study Guide

    Study Guide

    458 PDF Pages

    $29.99

Microsoft AZ-104 Practice Test 82

Question 810

An Azure Monitor metric alert covers CPU utilization for twelve application VMs in one resource group. Only vm-app03 is undergoing approved patching tonight from 22:00 to 23:00. Operations must silence notifications for that VM during this hour but continue evaluating the alert and notifying on failures from the other eleven VMs. What should be configured?

  1. Disable the shared metric alert rule for the hour and re-enable it after patching.
  2. Remove the email action group from the shared metric alert rule for all VMs during patching.
  3. Change the CPU threshold to 100% for every VM so alert notifications are unlikely during maintenance.
  4. Create a scheduled alert processing rule scoped or filtered to vm-app03 that suppresses notifications during the maintenance interval.

Explanation

Correct Answer

D:

Azure Monitor alert processing rules can apply a Suppress notifications action to matching alerts and can be scheduled for a maintenance window. Scope or filter the rule to vm-app03 and set the 22:00–23:00 interval. The metric alert can still fire and record alert instances for all VMs; notifications for unaffected targets remain available.

Incorrect Answers

A:

Disabling the shared rule would stop alert evaluation for all twelve VMs. Operations explicitly needs unaffected VMs monitored and notified throughout the patch, so turning off the common alert rule is too broad.

B:

Changing the shared action group would remove notifications for production VMs that are not under maintenance. An alert processing rule can suppress actions for just the target resource without changing the shared rule’s normal routing.

C:

Changing the CPU threshold for all VMs weakens detection and still does not implement the narrow one-hour maintenance exception. Monitoring thresholds and action-group notification handling are separate controls.

Question 811

A team wants to add an emergency notification action group to existing fired alerts at scale. Which Azure configuration or procedure is the best fit?

  1. Create an alert processing rule with schedule and suppression action.
  2. Verify alert firing, action group configuration and alert processing suppression before raising thresholds.
  3. Configure a separate metric alert rule; action groups only deliver actions/notifications.
  4. Apply an alert processing rule that adds action groups for matched resources.

Explanation

Correct Answer

D:

An Azure Monitor alert processing rule of type Add Action Groups can attach an emergency action group to alerts matching specified scopes and filters. This changes alert notifications without individually editing every underlying alert rule.

Incorrect Answers

A:

Alert processing rules that suppress actions are useful for maintenance windows, but suppression would prevent rather than add emergency notifications. To attach an extra action group across matched fired alerts, configure the processing rule action to add the designated group and scope it to the intended resources.

B:

Verify alert firing, action group configuration and alert processing suppression before raising thresholds is pertinent when an alert has fired but no one received mail after new rule deployment. This case instead states a team wants to add an emergency notification action group to existing fired alerts at scale. That alternate change addresses a different operational condition and does not directly achieve the needed resolution: apply an alert processing rule that adds action groups for matched resources.

C:

A separate metric alert changes the alert trigger, whereas an alert processing rule can add groups to existing fired alerts without recreating every rule.

Question 812

An Azure VM has more than three weeks of CPU metric history. CPU routinely reaches 80% during business hours but remains much lower overnight, making a single static percentage threshold noisy. Operations wants alerts for abnormal departures from the learned daily/weekly usage pattern, delivered to an existing email action group. Which configuration is appropriate?

  1. Use a permanently fixed 80% static metric threshold with no consideration of the normal hourly pattern.
  2. Attach the action group directly to the VM without any alert rule that evaluates the CPU metric.
  3. Create an Azure Monitor CPU metric alert with a dynamic threshold, suitable sensitivity/evaluation settings, and the existing email action group.
  4. Collect the same CPU metric in a different storage account and assume the storage firewall will calculate seasonal alert thresholds.

Explanation

Correct Answer

C:

Azure Monitor dynamic thresholds learn the historical metric baseline and account for recurring daily or weekly patterns when sufficient samples are present. With more than three weeks of CPU history, a suitable sensitivity and violation window can detect abnormal values and send results through the existing action group.

Incorrect Answers

A:

A fixed threshold can be useful for an absolute business limit, but it will fire on routine daytime CPU activity and fail to adapt to the described hourly and weekly baselines. The requirement is anomaly detection relative to normal historical patterns, not a static 80% limit.

B:

An action group defines receivers/actions to invoke when an alert fires, but does not independently evaluate VM CPU. A metric alert rule with a defined condition is still required for detection.

D:

Storage account location or firewall settings govern data storage and network access; they do not replace an Azure Monitor alert rule or compute learned seasonal metric thresholds. Moving CPU data to another storage account would not solve the monitoring behavior.

Question 813

A security workspace already receives Microsoft Entra `SigninLogs` through an existing diagnostic export. Security operations wants a notification whenever more than ten failed interactive sign-ins are observed in a rolling 15-minute query window. The signal is rows in Log Analytics, not a platform metric. Which alert rule type and query approach meets this requirement?

  1. Create an Azure Monitor CPU-percentage metric alert on a VM and attach an email action group.
  2. Create an alert processing rule that suppresses all notifications when an existing sign-in alert fires.
  3. Create a scheduled log-search alert that queries `SigninLogs` for `IsInteractive == true` and `ResultType != "0"`, counts failures in the window, and triggers an action group when the threshold is exceeded.
  4. Configure an Activity Log administrative-operation alert for VM restart events instead of querying workspace sign-in records.

Explanation

Correct Answer

C:

A scheduled query alert evaluates KQL results in the workspace. Restricting SigninLogs to interactive unsuccessful results and applying a count threshold for the window directly tests the documented security signal.

Incorrect Answers

A:

A VM CPU metric is not the Entra authentication result dataset and cannot evaluate ten failed SigninLogs events, regardless of which action group receives it.

B:

Alert processing rules act on fired alerts, often changing action groups or suppressing notifications. They do not create the KQL evaluation of the existing sign-in table.

D:

Resource administrative operations in the Azure Activity Log do not enumerate the requested interactive Entra sign-in failures in SigninLogs. This alert would monitor unrelated control-plane events.

Question 814

An Azure Monitor CPU metric alert is firing and its action group is attached correctly. The newly added individual email receiver has not completed the verification code sent when the action group was saved; the 30-minute code has expired. Other verified receivers receive alerts. What should the operator do for the affected receiver?

  1. Disable the CPU metric alert rule and recreate the VM, because the existing metric signal cannot use email receivers.
  2. Apply an alert-processing rule that suppresses notifications for the affected VM throughout the week.
  3. Increase the CPU threshold and remove the action group to make email delivery more reliable.
  4. Use the action group to resend the email verification code, complete the receiver OTP validation, and test notification delivery.

Explanation

Correct Answer

D:

Microsoft documents action-group individual email receivers requiring one-time passcode verification, with a limited validity window and a Resend action for expired codes. Completing verification and testing the saved action group addresses the missing receiver while preserving the already working metric alert.

Incorrect Answers

A:

The CPU metric alert already fires and other receivers are notified, so its signal and VM resource are working. Disabling the alert or rebuilding the VM cannot validate the new email recipient and would interrupt required detection.

B:

Alert processing rules that suppress notifications intentionally silence matching alerts. Suppression would reduce delivery further and has no ability to verify an individual action-group email address.

C:

Changing the CPU threshold changes detection criteria, and removing the action group disconnects notifications. Neither operation addresses the explicit unverified email receiver or expired code.

Question 815

An SRE team operates Azure SQL Database in West Europe. They want email and incident-platform notifications when Microsoft issues a Service Health service-issue notice affecting the production subscription, this Azure service and region. They do not want CPU threshold alerts or alerts for routine customer-initiated resource updates. What should they create?

  1. Configure only an action-group webhook with no alert rule or Service Health condition.
  2. Create an administrative Activity Log alert on `Microsoft.Sql/servers/write`; that operation specifically detects Microsoft regional service incidents.
  3. Create an Azure Service Health alert scoped to the affected subscription, Azure SQL Database, West Europe and service-issue event type, with an appropriate action group.
  4. Create a metric alert on the database DTU/CPU threshold and classify every threshold breach as a Microsoft Service Health incident.

Explanation

Correct Answer

C:

Service Health alert rules filter Microsoft-provided notifications by affected subscription, services, regions and event types. Linking an action group delivers the alerts to the desired channels.

Incorrect Answers

A:

An action group delivers notifications but does not decide when a Microsoft Service Health issue is relevant to the production subscription and region.

B:

A resource write event reports an administrative operation, not a service incident generated by Microsoft for that regional Azure service.

D:

SQL resource performance metrics can indicate workload pressure but cannot by themselves establish that Microsoft published a regional Azure Service Health incident.

Question 816

A team receives two separate Azure Monitor incidents because two different alert rules evaluate the same application error condition and share one action group. Which change addresses the duplicate alerts at their source?

  1. Review and consolidate the duplicate alert-rule conditions/scopes or implement supported alert correlation, rather than adding another notification destination.
  2. Add a second email receiver to the same action group; that merges duplicate alert instances.
  3. Widen an alert-processing suppression rule to every unrelated subscription to hide duplicate incidents.
  4. Change every alert rule threshold to zero so alerts no longer fire.

Explanation

Correct Answer

A:

Separate rules may independently fire for the same signal; consolidating overlapping rule scopes/conditions or applying appropriate correlation targets the duplicate production incidents.

Incorrect Answers

B:

More action-group receivers create additional notifications but do not merge separately firing alert instances.

C:

A blanket suppression conceals important alerts beyond the affected application and does not resolve why redundant rules fire.

D:

Zero thresholds can make alerts fire more often and do not implement legitimate deduplication or correlation.

Question 817

A governance team needs an email whenever an administrator successfully deletes an Azure resource group in subscription `Prod-A`. The evidence is an Azure Resource Manager control-plane event, and the alert should identify the administrative deletion regardless of application CPU usage. Which alert is appropriate?

  1. Create an alert processing rule that only suppresses notifications from existing metric alerts; it will automatically create the deletion event trigger.
  2. Set a VM CPU metric threshold to zero and expect it to fire when any resource group is deleted.
  3. Configure an Azure Service Health alert for regional platform outage events.
  4. Create an Activity Log alert for the subscription’s Administrative event category, operation `Microsoft.Resources/subscriptions/resourceGroups/delete`, successful status, and attach the email action group.

Explanation

Correct Answer

D:

Azure Activity Log administrative events identify control-plane actions by operation name and status. The matching delete-operation alert can notify the team regardless of workload metrics.

Incorrect Answers

A:

An alert processing rule adjusts downstream notification treatment but does not observe a resource-group deletion unless a matching alert rule already fires.

B:

VM CPU is a measurement of a compute resource; deleting a resource group is an ARM management-plane action and is not encoded as a CPU threshold.

C:

Service Health alerts describe Microsoft platform incidents and maintenance; they do not alert on customer-initiated Azure resource-group deletion operations.

Question 818

A static Azure Monitor Percentage CPU alert on VM vm-ledger evaluates every five minutes and has a verified email action group. CPU has remained above the threshold for 40 minutes. The alert fired once, then sent no new firing while the condition stayed active; its Automatically resolve alerts setting is enabled. No alert processing rule suppresses notifications. Compliance explicitly requires repeated alert firings during a sustained violation and accepts that the instances will not automatically resolve. What setting change addresses that requirement?

  1. Turn off Automatically resolve alerts on the metric alert (or set autoMitigate to false programmatically) to make it stateless, while accounting for the documented notification cadence.
  2. Increase the alert severity to Sev 0 but retain Automatically resolve alerts; severity alone makes repeated threshold violations fire on every evaluation.
  3. Add a second email action group to the unchanged stateful alert; two action groups force a new firing on every subsequent metric evaluation.
  4. Create an alert processing rule with Suppress notifications for the VM; suppressing an action group causes the existing stateful alert to refire.

Explanation

Correct Answer

A:

Azure Monitor metric alerts are stateful by default when Automatically resolve alerts is selected: they fire once for a given active condition and do not fire again until resolved. Clearing that setting, or using autoMitigate=false in the alert definition, makes the metric alert stateless so further qualifying evaluations can generate new firings. Microsoft documents cadence limits for repeated notifications; stateless alerts also do not automatically resolve after the metric recovers.

Incorrect Answers

B:

Alert severity classifies operational impact but does not control whether a metric rule is stateful or stateless. With Automatically resolve alerts still selected, a sustained threshold violation retains one fired condition until it resolves, regardless of whether it is tagged Sev 0 or Sev 3. Change the statefulness setting, not just the severity, to meet the repeat-firing requirement.

C:

Action groups specify notification and automation recipients; adding an additional action group does not alter the rule's stateful evaluation behavior. A stateful metric alert stays in the fired condition and will not create a fresh firing merely because it has two email destinations. Repeated firings require the stateless metric alert setting where supported.

D:

Alert processing rules with Suppress notifications prevent eligible actions from being delivered after alerts fire, and do not convert a stateful metric rule into a stateless one. Suppressing notifications is the opposite of the compliance request. The case confirms there is no erroneous suppression and asks for repeated firings rather than routing changes, so update the metric alert statefulness setting instead.

Question 819

An audit team investigates an environment that already used VM Insights Map and Dependency Agent for process-to-process connections. The Map experience and Dependency Agent are deprecated and will cease to be supported after June 30, 2028. The team wants to know whether previously ingested Log Analytics process/connection records will be erased at retirement and whether the old agent will continue producing new connection data. Which assessment matches Microsoft guidance?

  1. All previously collected VMProcess and VMConnection records are deleted automatically on June 30, 2028, regardless of Log Analytics retention settings.
  2. Existing Dependency Agents will continue sending process and connection data indefinitely, and new VMs should be onboarded through the old portal Map flow.
  3. Historical records in VMComputer, VMProcess, VMConnection and VMBoundPort remain subject to Log Analytics workspace retention; future Dependency Agent ingestion and the Map/Service Map experience end as documented, so a supported replacement is needed for new topology data.
  4. Azure Monitor Agent automatically reconstructs historical process-level network connections and preserves the old Map API without a dependency data source.

Explanation

Correct Answer

C:

Microsoft's retirement FAQ explicitly names VMComputer, VMProcess, VMConnection and VMBoundPort as tables whose previously ingested data remains accessible subject to workspace retention. It separately announces retirement of the Map experience, Service Map API, and new Dependency Agent ingestion. Retain and query existing records as permitted, but select supported replacement instrumentation for future process/dependency discovery; Azure Monitor Agent-based VM performance monitoring may continue.

Incorrect Answers

A:

Microsoft distinguishes the retiring VM Insights Map capability from historical records already written to Log Analytics tables. Those records are not automatically destroyed by the Map shutdown; the workspace's normal data-retention configuration determines how long they remain queryable. Retiring the Map feature does not override the previously chosen workspace retention period.

B:

The Dependency Agent and Map are deprecated; Microsoft says not to initiate further Dependency Agent onboarding, and new portal onboarding was restricted after September 30, 2025. New process/connection ingestion and the legacy Service Map API are not an indefinite supported source of future telemetry. Continuing the old flow would leave the incident team without a maintained dependency data path.

D:

Azure Monitor Agent supports modern VM performance and log collection, but it does not retroactively generate historical process connections that were never collected, nor guarantee the legacy Service Map API after its retirement. The historic tables stay available only to the extent workspace retention allows; future dependency topology requires an independently supported collection method.

Question 820

A company still runs the legacy VM Insights Map and Dependency Agent to visualize connections between processes on Azure virtual machines and external services. The team needs ongoing process-dependency discovery after the June 30, 2028 retirement, while retaining currently supported VM performance monitoring. Which transition follows Microsoft guidance?

  1. Keep onboarding new VMs to the Dependency Agent and assume the Map REST API will remain supported indefinitely.
  2. Stop using Azure Monitor Agent and disable all VM Insights performance monitoring because the Map feature is retiring.
  3. Replace process-connection topology with Azure Storage Insights availability and transaction charts.
  4. Offboard the Dependency Agent/Map, evaluate a supported monitoring and diagnostics replacement for process dependencies, and continue Azure Monitor Agent-based VM performance monitoring.

Explanation

Correct Answer

D:

Microsoft specifically recommends offboarding VM Insights Map and the Dependency Agent before June 30, 2028. For process and external-service dependency discovery, it directs customers to evaluate replacement solutions in the Azure Marketplace monitoring and diagnostics category. VM Insights performance monitoring using Azure Monitor Agent is not affected and can continue. This plan replaces only the retiring dependency capability while retaining the supported performance-monitoring channel.

Incorrect Answers

A:

Microsoft is retiring the Dependency Agent and VM Insights Map, including the Map view, Connections Overview workbook, new data ingestion, and Service Map API support. Continuing to onboard additional virtual machines is not a supported long-term plan. The old data remains subject to workspace retention, but cannot be treated as a substitute for ongoing process-dependency collection after retirement. This option leaves the team dependent on technology Microsoft has explicitly deprecated.

B:

VM Insights performance monitoring uses Azure Monitor Agent, not the retired Dependency Agent. Microsoft says that performance monitoring remains supported when VM Insights Map retires. Disabling the agent would remove useful host performance telemetry without solving process-dependency discovery. The retirement announcement concerns Map and its dependency collection path, not all performance workbooks or VM Insights metrics.

C:

Azure Storage Insights reports storage-account activity such as availability, latency, and transactions. It does not discover process relationships on virtual machines or provide the connection topology previously collected by Dependency Agent. A storage dashboard can complement a broader monitoring strategy, but it cannot replace the missing process and external-service dependency graph for the stated requirement.