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 30

Question 290

A noncritical test blob workload has an approved requirement for replicas only inside one primary Azure datacenter and prioritizes minimum redundancy cost. Which option matches that failure-domain acceptance?

  1. ZRS, which places synchronous copies across separate availability zones and costs more than LRS.
  2. RA-GRS, which enables a read-only distant secondary endpoint through geo-replication.
  3. LRS, which maintains locally redundant copies within the primary physical location.
  4. GZRS, which combines primary zonal resilience and a geographically separate secondary copy.

Explanation

Correct Answer

C:

Locally redundant storage keeps replicas in the primary region’s local physical location and is the fitting low-cost option when zonal/geo risks are accepted.

Incorrect Answers

A:

ZRS protects across independent availability zones, which exceeds the stated single-datacenter requirement.

B:

RA-GRS introduces cross-region asynchronous copies and secondary reads beyond the low-cost local-copy requirement.

D:

Geo-zone-redundant storage extends durability across zones and regions, creating unnecessary redundancy for the stated minimal-cost local scenario.

Question 291

A finance platform stores transactional objects in a supported Azure Blob account. The business requires synchronous copies across availability zones in the primary region and asynchronous replication to a secondary geographic region, but does not need read access to the secondary before failover. Which redundancy option is the minimal fit?

  1. GRS, which stores the primary replica using local redundancy and then copies to a secondary region.
  2. ZRS, which copies across primary-region zones but has no secondary geographic replica.
  3. GZRS, subject to the account type and region supporting this model.
  4. RA-GRS, which adds secondary read access but lacks synchronous zone redundancy in the primary region.

Explanation

Correct Answer

C:

GZRS combines synchronous zone-redundant primary storage with asynchronous geo-replication to a secondary Azure region. It provides both requested resilience dimensions without enabling the optional secondary read endpoint. Validate that the storage account type and primary region support GZRS, and plan for the secondary copy to lag committed primary writes because geo-replication is asynchronous. During a regional outage, account failover rules and application recovery still affect when writes can resume.

Incorrect Answers

A:

GRS gives geographic replication to a secondary region, but its primary region uses local rather than zone-redundant storage. That leaves a different primary-region failure domain from the three-zone requirement. Even if failover to the secondary is possible, the contract separately demands synchronous zonal copies in the primary region; that part is missing.

B:

ZRS protects object copies synchronously across multiple availability zones within one primary region. By itself it does not replicate the storage account into a secondary geographic region, so it fails the separate disaster-recovery requirement. The platform needs both zone redundancy and geo-replication, which are combined in GZRS.

D:

RA-GRS permits reading a secondary copy before failover, but the primary side retains local rather than zone-redundant replication. Secondary reads are unnecessary in this scenario and do not fix that primary-zone gap. RA-GZRS would provide both required redundancies but adds optional read access not requested, so non-RA GZRS is the minimal matching design.

Question 292

An application owner claims that a GRS storage account guarantees zero data loss if the entire primary Azure region fails seconds after a write. What should the administrator explain?

  1. GRS replicates to the secondary asynchronously; the last writes can be lost and an appropriate nonzero RPO must be planned.
  2. GRS secondary storage is synchronously committed before every primary write is acknowledged.
  3. Read-access GRS automatically makes the secondary a writable primary without a failover.
  4. Switching the Blob access tier to Hot forces synchronous replication across regions.

Explanation

Correct Answer

A:

Azure acknowledges primary writes before the asynchronous geo-secondary is necessarily current, so a regional disaster can leave an RPO gap.

Incorrect Answers

B:

Secondary geo-replication is asynchronous, unlike synchronous copies within the primary location, so every write is not committed in both regions first.

C:

RA-GRS permits read access to the secondary but does not automatically make that endpoint writable without failover.

D:

Blob access tiers govern storage cost and retrieval behavior, not the asynchronous geo-copy consistency model.

Question 293

A GPv2 storage account has a feature that is incompatible with a requested LRS-to-GZRS redundancy conversion, and the portal rejects the change. What is the appropriate administrative response?

  1. Force the account replication property to GZRS with a resource tag, bypassing the service support check.
  2. Delete the incompatible feature immediately without checking data protection or migration impact.
  3. Check the documented feature, region, account-kind and migration compatibility matrix, then plan a supported transition or replacement account.
  4. Grant the account Reader role to all users to enable cross-region durability.

Explanation

Correct Answer

C:

Storage redundancy conversions depend on account kind, region and enabled features; use the documented supported route instead of forcing an invalid change.

Incorrect Answers

A:

Resource tags cannot override Storage service redundancy availability and change limitations.

B:

Unplanned feature deletion can destroy protection or functionality, and does not establish a validated supported redundancy transition.

D:

Reader grants access to management metadata; they do not change the replication support of an account.

Question 294

An existing standard StorageV2 account uses LRS in a region that supports ZRS. Business continuity now requires read/write availability after loss of an entire availability zone, and the account is eligible for migration. What must the administrator do?

  1. Leave LRS unchanged because its replicas automatically survive failure of the entire datacenter hosting them.
  2. Upgrade from LRS to ordinary GRS and assume the primary LRS replicas become zone redundant without a failover.
  3. Plan and perform an eligible switch to ZRS (or another supported zone-redundant model), observing the account migration requirements.
  4. Enable RA-GRS and treat remote read-access as a substitute for local primary-region zonal availability.

Explanation

Correct Answer

C:

ZRS distributes synchronous replicas across availability zones and is designed to remain readable and writable after a zone outage. An existing account must follow supported redundancy-change/migration procedures.

Incorrect Answers

A:

LRS copies data within one datacenter and does not guarantee availability if that datacenter or zone fails.

B:

GRS provides a geo copy, but its primary region normally uses LRS. Adding asynchronous geo replication does not satisfy synchronous multi-zone primary-region availability.

D:

Read-access GRS exposes a secondary-region read endpoint; it does not give primary-region ZRS resilience or secondary writable availability before failover.

Question 295

A workload reads from the RA-GRS secondary Blob endpoint during primary downtime. Its operator assumes the secondary can also accept new writes without failover. Which statement corrects the misunderstanding?

  1. The RA-GRS secondary endpoint is read-only until the supported failover process promotes it; secondary read capability is not writable failover.
  2. RA-GRS automatically makes its -secondary endpoint writable whenever any read succeeds.
  3. The same connection string with an extra Reader role can write directly to the RA-GRS secondary.
  4. Turning on Blob versioning immediately converts the secondary replica into a writable account.

Explanation

Correct Answer

A:

Read-access geo-redundancy exposes reads from the asynchronously maintained secondary, while writes require a successful account failover to the promoted region.

Incorrect Answers

B:

The secondary endpoint remains read-only under the RA redundancy mode, not writable because it answers reads.

C:

RBAC cannot override the secondary replica’s service-level read-only state in an ordinary RA-GRS deployment.

D:

Blob versioning retains historical object states but does not initiate or complete a geographic storage failover.

Question 296

A product team needs asynchronous replication of supported online-tier block blobs from a source StorageV2 account to a separate destination StorageV2 account. It needs a managed, policy-based copy and accepts replication lag. Which configuration is sufficient when its prerequisites can be enabled?

  1. Set up destination containers and Azure RBAC alone, without defining an object replication policy.
  2. Enable blob versioning on both accounts, change feed on the source, and configure an object replication policy with the correct source/destination container rules.
  3. Use object replication as a synchronous zero-RPO mirror across regions; changes are committed only after both copies confirm.
  4. Enable blob change feed only on the destination account and leave versioning disabled in both accounts.

Explanation

Correct Answer

B:

Object replication uses a policy containing source/destination container rules; versioning is required on both accounts and the source must have change feed. Copies happen asynchronously, so lag remains possible.

Incorrect Answers

A:

A destination container and authorization are necessary surrounding infrastructure but do not instruct Azure Storage to asynchronously copy objects.

C:

Object replication is asynchronous and cannot guarantee zero RPO or synchronous acknowledgments on both accounts.

D:

The source account needs change feed and both accounts need versioning. Enabling change feed only on the destination does not fulfill the prerequisites.

Question 297

A backup team turns on Azure Blob object replication between storage accounts and expects all Azure Files SMB shares to appear automatically in the destination. What limitation must it recognize?

  1. Azure Blob object replication copies every Azure Files SMB share when Blob versioning is enabled.
  2. Object replication is designed for supported block blobs and containers, not Azure Files shares; protect Files with a suitable separate mechanism.
  3. Changing the File share quota automatically makes it eligible for Blob object replication.
  4. A new Blob SAS with list permission replicates SMB shares as part of the same object policy.

Explanation

Correct Answer

B:

Blob object replication operates on eligible block blob objects; Azure Files protection and copying require services or processes that support file shares.

Incorrect Answers

A:

Versioning supports supported Blob object replication but does not transform the separate Azure Files share service into block blobs.

C:

Share quota changes do not alter which service kinds Azure Blob object replication supports.

D:

A SAS delegates access to data operations and does not add Azure Files to the Blob replication engine.

Question 298

An object replication rule is active, blob versioning is enabled on both accounts, and change feed is on at the source. A new source blob named invoices/2026-10.csv is online, but it is not replicated. The rule currently includes only the prefix reports/. What is the most direct fix?

  1. Assume an object replication rule always overrides its prefix filters, so wait without changing the configuration.
  2. Correct the rule’s include-prefix filter to cover invoices/ (or add an appropriate supported rule) and allow asynchronous replication to process the matching blob.
  3. Disable change feed at the source to make the destination copy new objects automatically.
  4. Replace the source blob’s data-plane RBAC assignments with subscription Reader; replication ignores policy filters when Reader is assigned.

Explanation

Correct Answer

B:

The source blob falls outside the configured reports/ prefix. Expand or correct the rule to include invoices/ while keeping the documented source change-feed and versioning prerequisites.

Incorrect Answers

A:

An include-prefix filter restricts which source names are eligible. Waiting cannot make an invoices/ blob match the reports/ rule.

C:

The source change feed is a prerequisite for object replication. Disabling it would break rather than repair replication.

D:

Subscription Reader is management-plane read permission, not a replication-prefix override. The name-filter mismatch is the documented cause here.

Question 299

The compliance team stores ordinary online-tier block blobs in three separate source containers: reports, exports, and customer-data. It wants replication of every eligible new blob from reports to a destination reports-copy container, but none of the other source containers. Which policy design gives that scope?

  1. Create an object-replication policy containing a container-pair rule for reports → reports-copy and no rules for the other two containers.
  2. Configure only destination RBAC roles and assume they select reports data for replication.
  3. Create one rule for customer-data and rely on a destination folder name reports-copy to redirect its source.
  4. Move the reports blobs into the Archive access tier before attempting replication so they replicate first.

Explanation

Correct Answer

A:

An object replication rule maps one source container to one destination container. Scope the policy to the reports container pair; other source containers lacking rules will not participate.

Incorrect Answers

B:

Authorization on the destination controls access, not which blobs and containers Azure replicates. A source/destination object replication rule is still required.

C:

A rule sourced from customer-data copies eligible customer-data blobs, not reports. A destination name does not silently change the selected source container.

D:

Object replication requires eligible online-tier blobs; archived blobs do not replicate. Archiving reports beforehand would obstruct the desired copy.

Question 300

An Azure Storage account uses blob versioning and has an active object-replication policy. An administrator tries to turn blob versioning off but the change is rejected. What must be done before disabling versioning is allowed?

  1. Disable versioning by switching the account to a Storage File share and leave the replication policy active.
  2. Remove the object-replication policy from the account first, then disable blob versioning if no other feature or immutability requirement blocks that change.
  3. Delete only the current blobs, because replication policies do not depend on blob versioning.
  4. Change the storage-account public network access setting; the versioning dependency is controlled by the account firewall.

Explanation

Correct Answer

B:

Azure object replication depends on blob versioning. Microsoft requires existing object-replication policies to be removed before turning off versioning, and additional active immutability settings can independently prevent the change.

Incorrect Answers

A:

Blob versioning and object replication are Blob Storage data-protection features; migrating data to an Azure Files share does not satisfy the prerequisite for disabling versioning on the source account.

C:

Deleting live blobs is destructive and does not remove the object-replication policy dependency. Retained previous versions and policy configuration are separate objects.

D:

Storage network rules affect permitted clients, not the service-side object-replication dependency. Changing the firewall cannot override the versioning configuration prerequisite.