Pass Your Microsoft AZ-104 Exam Easy!

Microsoft AZ-104 Exam Questions & Answers, Accurate & Verified By IT Experts

Instant Download, Free Fast Updates, 99.6% Pass Rate

AZ-104 Premium Bundle

$79.99

Microsoft AZ-104 Premium Bundle

AZ-104 Premium File: 606 Questions & Answers

Last Update: Sep 24, 2026

AZ-104 Training Course: 132 Video Lectures

AZ-104 PDF Study Guide: 458 Pages

AZ-104 Bundle gives you unlimited access to "AZ-104" files. However, this does not replace the need for a .vce exam simulator. To download VCE exam simulator click here
Microsoft AZ-104 Premium Bundle
Microsoft AZ-104 Premium Bundle

AZ-104 Premium File: 606 Questions & Answers

Last Update: Sep 24, 2026

AZ-104 Training Course: 132 Video Lectures

AZ-104 PDF Study Guide: 458 Pages

$79.99

AZ-104 Bundle gives you unlimited access to "AZ-104" files. However, this does not replace the need for a .vce exam simulator. To download your .vce exam simulator click here

Microsoft AZ-104 Practice Test 21

Question 200

A file share is deleted by mistake and must be recoverable for a defined period. What should be configured?

  1. Copy only the affected file from its known-good share snapshot into the live share
  2. Enable Azure Files share soft delete with suitable retention
  3. Recognize that soft-delete expiry may make recovery impossible without another backup
  4. Configure supported immutable blob retention policies at the appropriate scope

Explanation

Correct Answer

B:

Share soft delete can protect against deletion of the share itself within its configured window.

Incorrect Answers

A:

File-level copy from a point-in-time snapshot restores one known-good item without reverting newer unrelated files. The stated constraint is different: share soft delete can protect against deletion of the share itself within its configured window.

C:

Retention policy is finite; do not promise restore of data past its expiry. The stated constraint is different: share soft delete can protect against deletion of the share itself within its configured window.

D:

Immutability governance is different from soft delete; mode and retention requirements need review. The stated constraint is different: share soft delete can protect against deletion of the share itself within its configured window.

Question 201

A share snapshot from yesterday exists; today a single file was corrupted while other files changed legitimately. How should the administrator recover without rolling back new work?

  1. Review the Azure Files share provisioned size/quota and supported capacity limits
  2. Copy only the affected file from its known-good share snapshot into the live share
  3. Enable Azure Files share soft delete with suitable retention
  4. Restore the entire share snapshot over live files, overwriting every change made since yesterday
  5. Implement appropriate snapshot retention and account for retained changed data

Explanation

Correct Answer

B:

File-level copy from a point-in-time snapshot restores one known-good item without reverting newer unrelated files.

Incorrect Answers

A:

A share quota is distinct from resource group quota; capability varies by file share tier. The stated constraint is different: file-level copy from a point-in-time snapshot restores one known-good item without reverting newer unrelated files.

C:

Share soft delete can protect against deletion of the share itself within its configured window. The stated constraint is different: file-level copy from a point-in-time snapshot restores one known-good item without reverting newer unrelated files.

D:

The scenario says only one file is corrupted and other current files contain legitimate changes. Replacing the whole share from yesterday’s snapshot could roll back valid work and introduce needless data loss. Use the existing known-good snapshot as a source for the single damaged file, preserve other live content and verify that the application reads the restored version. A broad restore is excessive for a one-file incident.

E:

Snapshots may preserve versions of changed blocks and incur ongoing storage cost. The stated constraint is different: file-level copy from a point-in-time snapshot restores one known-good item without reverting newer unrelated files.

Question 202

A team retains hundreds of daily file-share snapshots and sees rising storage charges. What operational consideration is missing?

  1. Enable Azure Files share soft delete with suitable retention
  2. Restore the affected files from a relevant Azure Files share snapshot
  3. Copy only the affected file from its known-good share snapshot into the live share
  4. Implement appropriate snapshot retention and account for retained changed data

Explanation

Correct Answer

D:

Snapshots may preserve versions of changed blocks and incur ongoing storage cost.

Incorrect Answers

A:

Share soft delete can protect against deletion of the share itself within its configured window. The stated constraint is different: snapshots may preserve versions of changed blocks and incur ongoing storage cost.

B:

Replica redundancy copies overwrites; a time-stamped share snapshot preserves prior file state. The stated constraint is different: snapshots may preserve versions of changed blocks and incur ongoing storage cost.

C:

File-level copy from a point-in-time snapshot restores one known-good item without reverting newer unrelated files. The stated constraint is different: snapshots may preserve versions of changed blocks and incur ongoing storage cost.

Question 203

A compliance application writes Blob log objects that must be retained for 180 days. They are accessed frequently for the first seven days and rarely after day 30, but deleting them before day 180 is prohibited. What storage automation can reduce cost without violating retention?

  1. Inspect lifecycle rule filters, blob type, and rule conditions against actual objects
  2. Configure a lifecycle action that permanently deletes every log blob after seven days, ignoring the mandatory 180-day retention
  3. Choose a hot access tier for frequently accessed blobs
  4. Evaluate lifecycle deletion alongside configured soft-delete and retention behavior
  5. Configure filtered blob lifecycle rules for age-based tier transition

Explanation

Correct Answer

E:

Azure Blob lifecycle management can evaluate object age and selected prefixes or tags, then move eligible logs from an online tier used for recent access to a cheaper supported online tier as reads decrease. The 180-day retention rule means tiering is appropriate but premature deletion is not. Configure filters for the compliance log objects, select age thresholds aligned with the seven-day hot and thirty-day infrequent-access pattern, and leave any permitted delete action no earlier than the mandatory retention boundary. Validate the rule with actual blob properties and service tier compatibility before broad deployment.

Incorrect Answers

A:

A policy can be enabled yet not match the target objects because of prefix or type filtering. The stated constraint is different: lifecycle management can move eligible blobs based on conditions; verify tier support and rule scope.

B:

Deleting log blobs at day seven directly contradicts the mandatory 180-day retention requirement in this scenario. An Azure Blob lifecycle rule can perform deletion when its conditions are met, but a rule that targets these objects before the retention period expires would destroy compliance evidence rather than optimize only the storage tier. Configure tier transitions as the blobs age, with carefully scoped filters, while retaining the records for the full required interval and honoring immutability or soft-delete policies as applicable.

C:

Keeping blobs hot during their first period of frequent access may control access charges, but it does not address the full 180-day compliance-retention plan or automatic transition after usage drops.

D:

Policy delete actions and recoverability windows are separate controls; no perpetual retention is implied. The stated constraint is different: lifecycle management can move eligible blobs based on conditions; verify tier support and rule scope.

Question 204

A lifecycle policy runs but new object names never move to the expected tier. What should be examined?

  1. Evaluate lifecycle deletion alongside configured soft-delete and retention behavior
  2. Configure filtered blob lifecycle rules for age-based tier transition
  3. Inspect lifecycle rule filters, blob type, and rule conditions against actual objects
  4. Use lifecycle filters and version-specific actions with explicit retention limits

Explanation

Correct Answer

C:

A policy can be enabled yet not match the target objects because of prefix or type filtering.

Incorrect Answers

A:

Policy delete actions and recoverability windows are separate controls; no perpetual retention is implied. The stated constraint is different: a policy can be enabled yet not match the target objects because of prefix or type filtering.

B:

Lifecycle management can move eligible blobs based on conditions; verify tier support and rule scope. The stated constraint is different: a policy can be enabled yet not match the target objects because of prefix or type filtering.

D:

Versioning creates multiple billable objects; current and previous versions may need different rules. The stated constraint is different: a policy can be enabled yet not match the target objects because of prefix or type filtering.

Question 205

A cleanup rule permanently deletes old blobs and a team assumes soft delete will always retain them. What should they distinguish?

  1. Evaluate lifecycle deletion alongside configured soft-delete and retention behavior
  2. Configure supported immutable blob retention policies at the appropriate scope
  3. Set a blob soft-delete retention period and assume every lifecycle-deleted version can be recovered indefinitely after that period.
  4. Enable blob versioning for overwrite history, with appropriate delete protection

Explanation

Correct Answer

A:

Policy delete actions and recoverability windows are separate controls; no perpetual retention is implied.

Incorrect Answers

B:

Immutability governance is different from soft delete; mode and retention requirements need review. The stated constraint is different: policy delete actions and recoverability windows are separate controls; no perpetual retention is implied.

C:

Soft delete is a time-bounded recoverability feature, not a permanent archive of everything removed by lifecycle management. Retention expiration and the configured lifecycle action must be evaluated together, including whether a version or snapshot was removed and whether a backup exists. Once a recovery interval elapses, a deleted object may become unrecoverable through soft delete. The operational distinction in this scenario is to inspect exactly what the lifecycle rule deletes and how the applicable retention protection works; simply setting a soft-delete period does not make recovery unlimited.

D:

Versioning preserves previous object versions; soft delete primarily addresses deletions. The stated constraint is different: policy delete actions and recoverability windows are separate controls; no perpetual retention is implied.

Question 206

A versioned **block-blob** container stores actively updated reports. The current versions should transition to cool storage after 45 days, while each previous version must remain recoverable until at least 120 days after that version was originally created and may then be deleted by policy. Which lifecycle design meets both requirements?

  1. Create only a baseBlob tierToCool action and assume the rule automatically deletes previous versions 120 days after they stop being current.
  2. Disable blob versioning before applying the lifecycle rule so only the latest uploaded report remains billable.
  3. Add a version.delete action after one day to avoid paying for historical versions, while keeping the current-blob tier rule.
  4. Use a baseBlob rule for the current version's cool transition plus a separate version action that deletes previous versions after the specified age, with suitable filters and retention safeguards.

Explanation

Correct Answer

D:

Define lifecycle rules that explicitly distinguish current block blobs from their retained previous versions. The baseBlob action can transition current versions to cool after the chosen 45-day condition, while a version action can delete older versions only when the appropriate creation-age condition meets the 120-day recovery policy. Scope filters to the intended blob type and container prefix, and examine legal holds or immutability requirements before deleting anything. Because Microsoft evaluates previous-version age from its creation time, confirm the policy's actual guarantee for reports that remain current a long time before being overwritten.

Incorrect Answers

A:

A baseBlob action applies to the current blob version, not automatically to each previous version generated by overwrites. Lifecycle management has distinct action groups for the base blob and previous versions. A cool transition after 45 days could be correct for the current state, but the rule as proposed contains no explicit action to retire older versions after their required 120-day retention. Retained versions remain billable. Configure a version-specific cleanup action separately and confirm how the age is computed for each previous version before enforcing retention.

B:

Disabling versioning would stop the future creation of previous versions, contradicting the business requirement to recover an earlier report state after accidental or incorrect overwrites. A lifecycle policy can manage versions without discarding the versioning feature. Current and earlier versions represent different recovery objects: both have storage cost and separately applicable lifecycle actions. The administrator should retain blob versioning, protect the required history, and apply tier transition to current versions and controlled deletion to historical versions rather than remove the mechanism that captures revisions.

C:

Deleting previous versions after a single day conflicts with the specified minimum 120-day recovery window. A technically valid lifecycle version.delete action can still be inappropriate when applied with the wrong time condition. Microsoft evaluates previous-version lifecycle age from that version's creation time, which must be considered carefully when translating business retention requirements. The lifecycle design should not use a one-day deletion threshold merely to reduce cost, and it should be tested against representative overwrite histories before the deletion policy is enabled.

Question 207

A general-purpose v2 storage account had blob versioning enabled before yesterday's overwrite of `reports/final.csv`. The Versions list now shows the previous blob with an older version ID and the correct contents. The app needs those exact earlier bytes as the current blob without discarding the retained version history. What should the administrator do?

  1. Enable blob versioning today and assume that doing so reconstructs yesterday's pre-overwrite version.
  2. Download the current version again, because the most recent version ID is always the old contents.
  3. Restore the container from container soft delete, even though the container was not deleted.
  4. Create a lifecycle rule for previous versions, assuming that it recreates any missing historical blob data.
  5. Identify the known-good previous version ID and copy or promote that version to become the blob's current content.

Explanation

Correct Answer

E:

Blob versioning preserves an addressable previous version when a versioned block blob is overwritten. The scenario explicitly confirms that versioning was enabled before yesterday's write and that a known-good historical version ID is present. Select that prior version, verify its timestamp and contents, and use the supported copy or Make current version operation to restore its bytes to the blob's current state. The operation must respect the caller's blob data authorization and any immutability controls. Confirm the application's reads afterward. Blob soft delete can also protect overwrites in some configurations, but it is not needed when the required previous version already exists.

Incorrect Answers

A:

Blob versioning captures historical states while the feature is enabled; turning it on only after an overwrite cannot retroactively recover bytes for which no version or other recovery object exists. The facts explicitly establish that versioning was enabled before the incident and that a known-good previous version remains accessible. Therefore the appropriate operation is to select that existing version and make its contents current. Enabling versioning can be part of future data-protection planning, but it is not a substitute for identifying and restoring the actual earlier object in this scenario.

B:

The current blob version represents the object state after the overwrite. Simply downloading the current version repeats the corrupted or unwanted contents and does not select yesterday's known-good state. Versioning identifies individual historical states by version ID; the relevant older version can be inspected and copied or promoted to become the current blob. The administrator should confirm the timestamp, metadata and actual content before changing the current object, and validate dependent application reads afterward. Neither a generic newest-version query nor a successful blob download proves that the right prior bytes have been recovered.

C:

Container soft delete is designed to recover an accidentally deleted container and its contents when the required retention feature was enabled. No container deletion occurred here; only one blob was overwritten while the container remains present. Restoring the container therefore answers a different failure mode and could create unnecessary disruption. The storage account already has a preserved historical version of the individual blob, and that version is the appropriate recovery object. Inspect the older version ID, verify its content and promote or copy it as a new current state while keeping other blobs unaffected.

D:

Lifecycle management can transition or delete eligible current and previous blob versions based on rule filters, age and storage tier. It does not reverse an overwrite or synthesize lost bytes from a missing historical version. A badly chosen lifecycle rule might even remove the very version needed for recovery. The scenario explicitly says an earlier version exists because versioning was active at the time of the write. Select that previously stored version to restore the content, then review lifecycle retention separately so useful history remains available for the required recovery window and storage costs are bounded.

Question 208

An application accidentally replaced a configuration blob and there are several old versions. What is the safe restoration approach?

  1. Identify and restore the exact known-good previous blob version
  2. Copy only the affected file from its known-good share snapshot into the live share
  3. Restore an arbitrarily selected old blob version without checking which version is known good
  4. Account for storage consumed by retained previous blob versions

Explanation

Correct Answer

A:

Selecting the wrong historic version can reintroduce a prior error even when restore succeeds.

Incorrect Answers

B:

File-level copy from a point-in-time snapshot restores one known-good item without reverting newer unrelated files. The stated constraint is different: selecting the wrong historic version can reintroduce a prior error even when restore succeeds.

C:

Blob versioning may retain multiple historical versions, not all of which represent the intended healthy configuration. Selecting any previous version solely because it is older could restore an already incorrect or incompatible document. Identify the known-good timestamp/content and restore or copy that specific version, then validate the dependent application. The recovery choice should follow evidence of correctness, not the first available version ID.

D:

Version history keeps older content for recovery and can grow independently of current visible object count. The stated constraint is different: selecting the wrong historic version can reintroduce a prior error even when restore succeeds.

Question 209

A workload frequently updates versioned blobs, and cost increases although container size seems stable. What explains this?

  1. Account for storage consumed by retained previous blob versions
  2. Identify and restore the exact known-good previous blob version
  3. Restore the applicable previous blob version after identifying its timestamp
  4. Use lifecycle filters and version-specific actions with explicit retention limits

Explanation

Correct Answer

A:

Version history keeps older content for recovery and can grow independently of current visible object count.

Incorrect Answers

B:

Selecting the wrong historic version can reintroduce a prior error even when restore succeeds. The stated constraint is different: version history keeps older content for recovery and can grow independently of current visible object count.

C:

Blob versioning tracks overwrite history distinctly from manually created blob snapshots. The stated constraint is different: version history keeps older content for recovery and can grow independently of current visible object count.

D:

Lifecycle rules can expire or tier eligible previous blob versions to manage cost, but the immediate cost explanation is that versioning retains older objects as separately billable data. A rule alone does not explain the measured growth.

Question 210

A compliance officer assumes blob versioning alone will prevent all deliberate deletions and purge activity. What is missing?

  1. Enable blob versioning alone and assume it prevents all subsequent privileged deletions and purges
  2. Restore the applicable previous blob version after identifying its timestamp
  3. Recognize that soft-delete expiry may make recovery impossible without another backup
  4. Use suitable delete protection and retention policy in addition to versioning

Explanation

Correct Answer

D:

Blob versioning preserves earlier content versions, but on its own does not establish an immutable legal retention obligation or prevent every authorized deletion and subsequent purge. The compliance officer's assumption is therefore too broad. Identify the required period and threat model, then configure supported retention, legal hold or immutability controls where appropriate alongside versioning and relevant delete protection. Test how deletes, version cleanup, lifecycle rules and elevated operators behave under those controls. A historical copy might help recovery, yet recovery is different from a policy that prevents deliberate destruction during a mandatory preservation period.

Incorrect Answers

A:

Blob versioning can retain older object versions after modifications but does not by itself impose an immutable retention commitment on those versions. Privileged deletion or purge paths may remain available depending on account settings and lifecycle. The compliance officer needs an appropriate immutable retention or legal hold design in addition to versioning, with supported policy scope and authorized deletion governance. Versioning alone cannot satisfy the stated anti-purge objective.

B:

Blob versioning tracks overwrite history distinctly from manually created blob snapshots. The stated constraint is different: versioning is history management, not a blanket immutability or authorization policy.

C:

Retention policy is finite; do not promise restore of data past its expiry. The stated constraint is different: versioning is history management, not a blanket immutability or authorization policy.


Microsoft Azure Administrator (AZ-104) Practice Tests

Purchase Individually

AZ-104 Premium File

Premium File
AZ-104 Premium File
606 Q&A
$76.99$69.99

AZ-104 Training Video Course

Training Course
AZ-104 Training Video Course
132 Lectures
$27.49$24.99

AZ-104 Study Guide

Study Guide
AZ-104 Study Guide
458 PDF Pages
$27.49$24.99

Site Search:

 

VISA, MasterCard, AmericanExpress, UnionPay

SPECIAL OFFER: GET 10% OFF

ExamCollection Premium

ExamCollection Premium Files

Pass your Exam with ExamCollection's PREMIUM files!

  • ExamCollection Certified Safe Files
  • Guaranteed to have ACTUAL Exam Questions
  • Up-to-Date Exam Study Material - Verified by Experts
  • Instant Downloads
Enter Your Email Address to Receive Your 10% Off Discount Code
A Confirmation Link will be sent to this email address to verify your login
We value your privacy. We will not rent or sell your email address

SPECIAL OFFER: GET 10% OFF

Use Discount Code:

MIN10OFF

A confirmation link was sent to your e-mail.
Please check your mailbox for a message from support@examcollection.com and follow the directions.

Next

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your e-mail address below to get started with our interactive software demo of your free trial.

Free Demo Limits: In the demo version you will be able to access only first 5 questions from exam.