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 90

Question 890

After a genuine and committed Azure-to-Azure Site Recovery failover, billing services have run in West US for four days. East US is healthy again. The team has already completed Re-protect from West US back to East US, and reverse replication is Healthy with current data. The owner approves returning production to East US with a controlled cutover. Which operation should follow?

  1. Perform the supported planned failback/failover toward East US using synchronized reverse replication, validate the original-region service and redirect client traffic; then re-establish DR protection.
  2. Start Re-protect from West US again and assume it switches production clients to East US without a separate failover operation.
  3. Update public DNS to the old East US address immediately and skip bringing up or validating the recovered primary VMs.
  4. Run only a Test failover into an isolated East US test VNet and call the test-copy deployment the permanent production failback.

Explanation

Correct Answer

A:

Once reverse replication is healthy and authorized, a controlled planned failover/failback brings up the recovered original-region workload. Verify applications and client networking before traffic cutover, commit as supported and re-establish ongoing secondary-region protection.

Incorrect Answers

B:

Re-protect is already complete in the scenario; it prepares replication direction and does not by itself initiate the operational return to the original production region. The next step is a supported planned recovery cutover.

C:

DNS changes alone cannot create or validate the target-region machines or their application state. Sending users to an old endpoint before failback would risk downtime or stale data even when reverse replication is healthy.

D:

Test failover creates an isolated rehearsal workload and is cleaned up later. It doesn't commit the real primary-region return or restore the intended production replication direction.

Question 891

After a Site Recovery failover, an application VM uses a new private IP in the secondary region. A client application has a DNS name that still resolves to the former primary IP. The business can tolerate a short switchover. What is the best connectivity remediation?

  1. Update the planned target-region DNS/traffic routing and load-balancer configuration to point clients at validated recovered endpoints, accounting for cached DNS TTL and switchover time.
  2. Reprotect the VM to the old region without changing any service endpoint; this automatically changes every client cached DNS record.
  3. Claim zero client disruption and no IP-dependent application changes because Site Recovery preserves every source private IP across regions.
  4. Set the Azure VM backup retention to one hour; the endpoint will then update automatically.

Explanation

Correct Answer

A:

Endpoint resolution and routing must reflect the recovered application; DNS caching and application cutover should be planned instead of promising instantaneous propagation.

Incorrect Answers

B:

Reprotecting is needed for future reverse replication but does not by itself change every client DNS cache or load-balancer endpoint.

C:

Site Recovery failover can change IPs and routes; asserting universal private-IP preservation or zero interruption contradicts the scenario.

D:

Backup retention changes historical recovery-point lifespan rather than service DNS and failover network reachability.

Question 892

During an unplanned regional Azure Site Recovery recovery, the newest usable replica recovery point for a payment VM is 90 minutes old. The approved business RPO is 30 minutes, and newer writes are not known to exist in a recoverable point. Availability is urgent, but the incident commander requires an explicit statement of potential data loss before approving cutover. What should the operator report and do?

  1. Select the existing 90-minute-old point and label its RPO as zero because Site Recovery is an asynchronous replication service.
  2. Increase the Azure VM Backup policy retention and assume it instantaneously creates a new Site Recovery recovery point containing the missing 60 minutes.
  3. Report that the newest usable point currently exceeds the 30-minute RPO by 60 minutes, seek the incident decision on that potential loss, and select a supported available recovery point with validation.
  4. Choose Latest app-consistent without checking its timestamp; an app-consistent point always contains all primary writes up to the outage.

Explanation

Correct Answer

C:

The available recovery-point age is 90 minutes, which is 60 minutes older than the 30-minute contractual target. Disclose that gap for an informed incident decision, use only a real eligible recovery point, and verify application consistency and resulting data.

Incorrect Answers

A:

Asynchronous replication does not guarantee zero data loss during a source-region failure. The known 90-minute timestamp exceeds the approved 30-minute RPO, so describing the gap as zero would materially misrepresent recoverability.

B:

Changing backup retention controls retention of Azure Backup points, not the age of a Site Recovery replicated point. It cannot reconstruct writes that were never processed or create a newer recovery point during the outage.

D:

App-consistent points can be older than crash-consistent or processed points. Selecting a consistency label without verifying the timestamp does not demonstrate the required RPO or recreate unreplicated transactions.

Question 893

A Recovery Services vault already produces built-in Azure Monitor job-failure alerts that the operations team can see in Resiliency. Nobody receives an on-call email because no notification route was configured. They want email for those existing alerts without inventing a second custom failure condition. What should the administrator configure?

  1. Create an Azure Monitor alert processing rule that routes matching built-in Azure Backup failure alerts to an action group containing the approved on-call email receiver.
  2. Create only a subscription Activity Log alert for VM write operations and assume it includes Azure Backup job failures.
  3. Disable built-in backup job-failure alerts so Resiliency stops showing them and rely on manual vault reviews.
  4. Add an Application Insights SDK to the protected VM and assume Azure Backup automatically forwards vault failure alerts to its email receiver.

Explanation

Correct Answer

A:

Azure Backup built-in job-failure alerts already fire by default. To notify responders, match those fired alerts using an alert processing rule and add an action group with an email channel; no duplicate metric or log failure detector is required.

Incorrect Answers

B:

A VM resource write event is not equivalent to a failed Azure Backup job. An Activity Log alert for that event will neither select the built-in Backup failure alert nor create the required notification routing.

C:

Turning off the existing job-failure signal eliminates information that operations already sees and does not add the missing email channel. Preserve alert generation and configure notification routing.

D:

Application Insights instruments application telemetry; it does not automatically route Azure Backup vault alerts to responders. Alert processing rules and action groups provide the documented Azure Monitor notification path.

Question 894

The Resiliency experience in Azure monitors supported Azure VMs across several subscriptions. Administrators can see already backed-up VMs under Protection inventory > Protected items, but must locate Azure VMs that have NO Backup or Site Recovery protection and configure protection for them. Which documented Resiliency view directly identifies those unprotected resources before remediation?

  1. Use only Protection inventory > Protected items, because this list includes all Azure VMs with no backup or replication as protected entries.
  2. Use only Backup Reports storage-consumption trends and classify any VM with low storage costs as unprotected without checking resource-level protection status.
  3. Create an alert processing rule to suppress Azure Backup job-failure notifications, because suppressing alerts automatically enrolls previously unprotected VMs.
  4. Open Resiliency > Protection inventory > Protectable resources, filter eligible subscriptions/resource groups/resource types, inspect the unprotected VMs and configure supported protection for them.

Explanation

Correct Answer

D:

Microsoft Learn calls the Resiliency > Protection inventory > Protectable resources list the view for supported resources not currently protected by Backup or disaster recovery. Filter by scope and resource type, inspect resource details, then enable appropriate supported protection. Protected items instead shows already protected inventory; the distinction identifies the missing coverage rather than only job failures.

Incorrect Answers

A:

The Protected items view shows resources that are ALREADY protected and their protection state. It does not enumerate otherwise eligible resources with no backup or replication. Microsoft directs administrators to Protectable resources to inventory not-protected Azure assets and then configure the required solution; relying only on Protected items would omit the coverage gap.

B:

Backup Reports can help analyze capacity, cost and job history for configured protection. They do not turn missing backup/replication into a reliable inventory derived merely from storage expenses. Protectable resources shows the actual supported unprotected VM/resource inventory for a chosen scope, so assess that list before enabling protection.

C:

An Azure Monitor alert processing rule controls notification delivery for existing alerts; it neither detects all never-protected VMs nor enables Azure Backup/Site Recovery policies. Suppressing alerts would hide operational signals and would not fix the absence of disaster recovery protection. Identify the resources in the protection inventory first.

Question 895

A compliance report must show the count of successful and failed Azure VM backup jobs for EACH of the last three calendar months across four Recovery Services vaults. The vaults already export backup diagnostic data to a supported Log Analytics workspace; a portal's recent-job grid shows only the newest few days. Which approach produces the required historical outcome trend?

  1. Use Azure Backup Reports' Jobs analysis over the selected three-month range with the relevant Log Analytics-backed data, grouping completed jobs by outcome and month.
  2. Count only the backup items currently protected in each vault, assuming a protected-item count is the number of successful backup jobs in each prior month.
  3. Review the latest one-day Azure Monitor Backup Health Events metric without setting a historical query window and infer last quarter's completed jobs from it.
  4. Aggregate received on-call failure notification emails and treat missing emails as proof that every backup succeeded in that month.

Explanation

Correct Answer

A:

Azure Backup Reports uses collected Azure Monitor logs and workbooks to analyze job trends over historical ranges across supported vaults. Select the Jobs view and the three-month period, counting actual successful and failed completed operations rather than relying on alert traffic.

Incorrect Answers

B:

Protected-item inventory describes current coverage, not how many scheduled backup jobs succeeded or failed historically. One protected VM can have dozens of jobs, and items removed in the period might no longer appear in current inventory.

C:

A current operational health signal is not a three-month job-by-job history. It cannot replace the historical completed-job telemetry already captured and queryable through the reporting workspace.

D:

Notification email delivery depends on action groups, suppression, severity and routing configuration. The absence of an email is not proof that a scheduled backup succeeded, so email counts are not reliable job-outcome evidence.

Question 896

An Azure VM enhanced backup job is marked `Completed with warnings`. The operator sees a recovery point recorded for that job, but its detailed status includes a guest VSS/application-consistency warning. An incident ticket describes it as a hard failure and claims there is no usable restore point. Which verification should the operator perform before accepting that claim?

  1. Treat every warning as a failed job with no recovery point and immediately delete the existing recorded point to avoid using it.
  2. Suppress the Azure Monitor backup-failure email action group so the warning disappears from all recovery and compliance reports.
  3. Inspect the actual job result, warning/error details and recovery-point existence and consistency type; distinguish a possibly crash-consistent usable point from a failed job with no point.
  4. Increase the Recovery Services vault retention duration, assuming this retroactively converts the stored warning-associated recovery point to app-consistent.

Explanation

Correct Answer

C:

Inspect the job's diagnostic warning, the protected item's recovery-point record and the point's reported crash/application consistency. A present point may be restorable yet fail an application-consistency objective; explain the difference before declaring a hard failure.

Incorrect Answers

A:

Azure Backup job status and recovery-point inventory are separate facts. A completed-with-warnings result can have a recovery point, so treating it as universally absent would discard potentially recoverable data without reviewing the actual point.

B:

Alert processing changes notification delivery, not whether a backup job produced a recovery point or its consistency class. Silencing an email cannot answer the incident's disputed restore-availability claim.

D:

Retention determines how long points are kept, not the consistency of an already completed guest snapshot. Increasing it cannot repair a failed VSS operation or transform the recorded recovery point's status.

Question 897

A Backup vault already emits the Azure Monitor Backup Health Events metric for many protected data sources. Operations wants a CUSTOM metric alert that fires when a source has more than zero unhealthy health events over the last 24 hours, with a separately identifiable alert for each existing or future data source. Which metric-alert design meets that requirement?

  1. Create a subscription Activity Log alert for successful role assignments and treat it as a backup health alert for every protected item.
  2. Create one vault-total Backup Health Events metric alert without a DatasourceId dimension, assuming it identifies which protected data source failed.
  3. Create an alert processing rule that suppresses every Backup Health Events notification indefinitely rather than evaluating unhealthy health events.
  4. Create a Backup Health Events metric alert with a greater-than-zero threshold for 24 hours, filter HealthStatus to supported unhealthy states and split DatasourceId by all current and future values.

Explanation

Correct Answer

D:

Azure Backup documents Backup Health Events metric alerts with HealthStatus filters for persistent/transient unhealthy events and DatasourceId dimension values selected as all current and future. A threshold above zero over the 24-hour window generates source-scoped alerts; attach an action group separately if notifications are required.

Incorrect Answers

A:

Azure role-assignment Activity Log events describe management operations, not unhealthy backup/restore health events emitted for protected data sources. They do not provide the requested Backup Health Events metric alert.

B:

A vault-wide metric aggregation can detect general health, but without the DatasourceId dimension it does not generate separately identifiable alert instances per protected data source. The case requires source-specific alert attribution.

C:

An alert processing suppression rule changes notification delivery after an alert exists; it does not create the requested unhealthy-event metric condition. Indefinite suppression would also conceal the failures operations wants to detect.

Question 898

A finance team needs the monthly trend of Azure Backup protected-instance size, backup storage consumption and associated cost drivers across vaults. Which Azure reporting approach best matches?

  1. Use only an alert processing rule to suppress job-failure emails, then treat the reduced email count as billed storage.
  2. Use Azure Backup Reports and supported Log Analytics or related cost/storage metrics to analyze protected data, backup storage usage, retention and monthly trends.
  3. Count the number of currently running virtual machines and assume it equals retained backup data volume.
  4. Read one vault’s latest failure status only; it reports historical monthly backup storage cost across the organization.

Explanation

Correct Answer

B:

Backup Reports and associated monitoring/billing data can compare historical protected-instance usage, vault consumption and retention trends as requested.

Incorrect Answers

A:

Notification suppression alters delivery of alert actions but has no bearing on the size or cost of retained backup data.

C:

VM count ignores backup storage duplication, incremental changes, retention and tier, so it is not sufficient cost evidence.

D:

Latest one-vault job status is an operational signal, not organization-wide monthly storage usage or cost history.

Question 899

Security is investigating who stopped protection and deleted a VM backup item from a Recovery Services vault yesterday. The vault has soft delete enabled and diagnostic/event monitoring configured. Investigators need the time and identity of the destructive operation and must learn whether the affected backup data can still be recovered. What should they do first?

  1. Rely only on the protected VM's current CPU chart and infer the deleting user's identity from the last CPU spike.
  2. Count current protected items in a backup storage cost workbook; assume missing items have no audit trail or recoverability status.
  3. Query Windows Event Viewer on the original VM as the sole record of Azure vault management operations and assume host logs cannot be deleted.
  4. Correlate the relevant Azure Activity Log/vault security or backup audit events with the soft-deleted item's retention state, then consider an authorized restore/undelete if it remains recoverable.

Explanation

Correct Answer

D:

Azure Backup security monitoring and Azure Activity Log can document destructive protection actions, while supported soft delete retains eligible backup data temporarily. Correlate actor/time with the protected item's state, preserve evidence, and restore only under incident approval and applicable retention.

Incorrect Answers

A:

A VM CPU chart measures guest or platform utilization. It does not authenticate the operator who performed a vault control-plane deletion or establish whether its backup item is in soft-delete retention.

B:

A cost/inventory view can expose protection gaps but often omits historical deleted item details. It isn't sufficient evidence of deletion actor/time, and absence from active inventory doesn't prove the protected data cannot be undeleted.

C:

Vault protection changes are Azure management events. Guest logs might be unavailable or unrelated, so investigators need the identity-linked Azure audit and backup-security records rather than relying only on OS events.

Question 900

During a planned SQL-in-VM backup maintenance window, a Recovery Services vault used an alert processing rule with Suppress notifications. Maintenance has ended, and Resiliency now shows a new backup-failure alert, but the on-call email action group still receives nothing. The suppression rule is enabled without an ending schedule and matches the vault. Which action restores notifications while keeping the backup alerts active?

  1. Permanently disable built-in backup-failure alerts on the vault because suppression cannot be changed.
  2. Delete and recreate the Recovery Services vault to clear the retained alert processing rules.
  3. Add a second subscription-wide alert processing rule that suppresses all action groups for backup alerts.
  4. Disable or correct the stale suppression rule and verify that the existing alert-processing notification rule still adds the on-call action group.

Explanation

Correct Answer

D:

Azure Backup documents separate alert-processing rules for routing notifications and suppressing them during maintenance. A matching Suppress notifications rule can override the usual action-group notification. Once maintenance ends, disable the no-longer-needed rule or correct its schedule and scope, then confirm that the normal notification rule adds the on-call action group for future failed-job alerts.

Incorrect Answers

A:

Disabling built-in failure alerts would eliminate the monitoring signal rather than restore email notification. The failed backup job is already producing an alert; the failure occurs in notification processing, not alert generation.

B:

A Recovery Services vault holds backup configurations and protected recovery data. Deleting it is disproportionate and may be blocked by protected items; the relevant notification setting is an Azure Monitor alert processing rule, not the vault’s existence.

C:

Suppression rules take precedence over action-group additions when both process a matching alert. Adding another broad suppression rule would prolong the missing email problem and could silence unrelated critical backup notifications.