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 38

Question 370

An administrator attempts to recover a prior state of an Azure Files file by enabling Blob object versioning on the storage account. Which protection is actually applicable to the Azure Files share?

  1. Use Blob version IDs as though they refer to SMB file versions.
  2. Treat a storage account access key rotation as an automatic file snapshot.
  3. Use Azure Files share snapshots or a supported Azure Files backup policy for file-level recovery points.
  4. Enable anonymous public Blob container read and assume it creates Azure Files versions.

Explanation

Correct Answer

C:

Share snapshots and Azure Files backup are the supported service-specific recovery mechanisms.

Incorrect Answers

A:

Blob version IDs apply to Blob Storage objects, not Azure Files SMB file versions.

B:

Key rotation is an authorization control and does not preserve file history.

D:

Public Blob access cannot provide Azure Files historical data.

Question 371

A classic Azure Files SMB share was deleted yesterday. Storage account diagnostics show that share soft delete had been disabled before the deletion. The team asks an administrator to find the deleted share in the soft-delete recovery list and restore its contents. What is the accurate recovery assessment?

  1. Enable share snapshots today and assume Azure automatically backfills snapshots of yesterday’s deleted share.
  2. Use the Azure Files undelete-share operation even though the share was permanently deleted while soft delete was off.
  3. Treat undelete as unavailable for that deletion and investigate surviving independent backups or replicated application copies.
  4. Apply a CanNotDelete resource lock to the storage account now so the deleted share reappears.

Explanation

Correct Answer

C:

Classic Azure Files soft delete keeps deleted shares recoverable only when that protection was already enabled at deletion time. If it was off, the administrator should not promise a portal undelete operation. Recovery instead depends on independent Azure Backup recovery points, application copies, or another retained data source established before the event. The administrator should verify which sources actually exist and preserve evidence of the incident, not create false recovery expectations.

Incorrect Answers

A:

Share snapshots preserve earlier share states only when the snapshots already exist on the source share. Enabling snapshot scheduling after a share has been deleted does not retroactively recreate missing historical snapshots. A backup outside the deleted share may still be relevant, but it must predate the loss.

B:

Share soft delete must have been enabled when the deletion occurred for its retention mechanism to keep the deleted share recoverable. The scenario explicitly states it was disabled beforehand. Running an undelete command cannot restore a resource that never entered the retained soft-deleted state.

D:

Azure management locks govern permitted control-plane operations going forward; they do not create recovery-point data for a share that was already removed. Applying a lock after deletion cannot resurrect missing file contents. Locks are not substitutes for share soft delete or a separately maintained backup strategy.

Question 372

A storage operator wants current Hot block blobs under container1/reports/ to move to Cool after more than 30 days since modification, with no manual job. What is the Azure-native configuration?

  1. Create a Blob lifecycle policy with a baseBlob tierToCool age action and the appropriate container/prefix filter.
  2. Rotate the account access keys every 30 days; Azure automatically tiers old data after each rotation.
  3. Apply a storage management ReadOnly lock and expect the Hot-to-Cool transition to occur.
  4. Require all clients to use HTTPS, which changes old Hot blobs to Cool when requests stop.

Explanation

Correct Answer

A:

Lifecycle management can tier supported current block blobs using a modification-age threshold and scoped filter.

Incorrect Answers

B:

Key rotation does not schedule Blob access tier changes.

C:

Read-only management locks are not automatic data-tiering policies.

D:

HTTPS is a transport security setting, not a tiering trigger.

Question 373

A lifecycle rule should delete eligible current block blobs 365 days after last modification. The account has no soft-delete retention and the blobs have no immutability policy or legal hold. Which configuration implements the request?

  1. Define a baseBlob delete action with a supported modification-age condition and proper blob-type/filter scope.
  2. Define tierToCool only; Azure then permanently deletes every blob after day 365 automatically.
  3. Configure an Archive rehydration action, which guarantees deletion of each current blob.
  4. Set the container public access level to Blob and assume anonymous reads initiate deletions.

Explanation

Correct Answer

A:

Lifecycle policies support current-version baseBlob delete actions based on object age, subject to supported conditions.

Incorrect Answers

B:

Changing the access tier does not by itself delete an object at the specified date.

C:

Rehydration restores offline blobs to online accessibility and is not a delete action.

D:

Public access level controls read authorization, not lifecycle retention or deletion.

Question 374

A lifecycle policy should tier block blobs only when their full path begins with container1/archive/. The team previously used the prefix archive/ and saw no matching objects. Which filter is correct?

  1. Use a prefixMatch value of archive/ without the container name, since Azure prepends it automatically.
  2. Use *.archive/* with wildcard matching, which is required for prefixMatch.
  3. Use a subscription-level Resource Manager tag filter instead of the Blob path.
  4. Use a case-sensitive prefixMatch of container1/archive/ in the Blob lifecycle policy rule.

Explanation

Correct Answer

D:

A valid prefixMatch starts with the container name and then the desired Blob path prefix.

Incorrect Answers

A:

Lifecycle prefixes include the container name as part of the matched Blob path.

B:

The prefixMatch filter uses literal prefix text, not shell wildcards.

C:

Resource Manager tags are not equivalent to Blob lifecycle prefix or index-tag filters.

Question 375

A lifecycle rule intended to affect only old audit files starts moving fresh application uploads into Cool. The policy has no prefixMatch filter and the age threshold is zero. What should be repaired?

  1. Constrain the Blob lifecycle rule to the correct container/path and a suitable age threshold, then observe its asynchronous execution.
  2. Disable all Azure Storage firewall rules, because they control which blobs are old enough to tier.
  3. Regenerate all storage account keys, which recalculates the lifecycle age of existing objects.
  4. Change application Blob names without updating the rule, because the rule ignores paths.

Explanation

Correct Answer

A:

A rule with an overly broad filter and zero-age condition includes newly uploaded data; correct both conditions.

Incorrect Answers

B:

Storage network rules govern connectivity rather than lifecycle selection.

C:

Key rotation does not correct lifecycle rule conditions or reset object age.

D:

The policy’s prefix matching depends on the Blob names and must be explicitly adjusted.

Question 376

Blob versioning is enabled. Compliance must retain the current blob but delete historical versions older than the approved threshold without affecting the current version. What lifecycle rule should be used?

  1. Apply a baseBlob delete action to every active blob that is older than the threshold.
  2. Configure a version-targeted lifecycle delete action with the appropriate age condition for previous versions.
  3. Enable anonymous read so older versions disappear after the first GET.
  4. Turn off Blob encryption for old versions so Azure deletes them automatically.

Explanation

Correct Answer

B:

Lifecycle policy actions can target previous versions separately from the active base blob.

Incorrect Answers

A:

A baseBlob delete action targets the current version and risks violating the retention requirement.

C:

Anonymous read policy does not perform version retention or lifecycle deletion.

D:

Encryption state does not implement previous-version age-based deletion.

Question 377

An Azure Blob lifecycle rule is created at 10:00. The administrator expects all eligible objects to be moved at 10:00 the next minute, and reports a failure when none move. Which behavior is documented?

  1. Azure lifecycle policies are synchronous with each individual PUT and execute at the precise second after the age threshold.
  2. Policy activation and object processing are asynchronous; allow up to 24 hours for a new policy to take effect and monitor later runs.
  3. Lifecycle policies are triggered only when users rotate storage account keys.
  4. A lifecycle rule can run only by enabling anonymous container reads.

Explanation

Correct Answer

B:

Microsoft documents delayed activation and background execution; object count and workload affect processing time.

Incorrect Answers

A:

Lifecycle processing is not an immediate, transaction-synchronous operation.

C:

Access key rotation is not a lifecycle scheduling trigger.

D:

Anonymous public read has no relationship to lifecycle policy execution.

Question 378

A StorageV2 account contains current Hot block blobs that can remain unchanged for months but are read regularly. Finance wants automated tiering only after 60 days without reads or writes, rather than 60 days since the last modification. Blob last-access-time tracking is disabled. Which change supports the requested criterion for current blobs?

  1. Create only a base-blob tierToCool rule using daysAfterModificationGreaterThan = 60; modification age represents the time of each recent read.
  2. Enable Azure Blob versioning; the creation dates of previous versions will automatically become the current blob's last-access timestamps.
  3. Set a prefixMatch value of lastaccess/; a path filter automatically records file read activity and updates LastAccessTime.
  4. Enable blob last-access-time tracking, then use a compatible base-blob tiering rule with daysAfterLastAccessTimeGreaterThan = 60 while accounting for observed tracking history and asynchronous evaluation.

Explanation

Correct Answer

D:

Microsoft supports blob access-time tracking and a daysAfterLastAccessTimeGreaterThan condition for current blobs. Tracking must be enabled for the desired last-read signal; timestamps are not retroactively populated from untracked history, and only the first read within 24 hours updates last access to reduce overhead. A lifecycle run then evaluates the eligible base blobs asynchronously, not at the exact threshold second.

Incorrect Answers

A:

DaysAfterModificationGreaterThan evaluates the time since the current blob was modified; an ordinary read does not alter its last-modified timestamp. For an object that is old but read every week, this rule could transition data despite recent use. The objective explicitly requires last access, so enable tracking and use its separate access-age condition.

B:

Blob versioning saves historical content versions when supported changes occur; it is not a replacement for access-time measurement on the current blob. Previous-version creation times do not prove when the current blob was last read. Use the documented Blob last-access tracking feature rather than infer access activity from versions.

C:

PrefixMatch scopes a lifecycle policy by the case-sensitive blob path; it does not measure read or write events or populate LastAccessTime. The name of a virtual prefix cannot substitute for enabling the tracking feature. An appropriate lifecycle filter can coexist with the access-age condition, but it does not itself supply the requested time signal.

Question 379

A regulated Blob container has an immutable retention policy that prevents deletion of the protected current objects until their retention period ends. A lifecycle rule also requests deletion earlier. What should the administrator expect?

  1. Lifecycle deletion ignores immutable retention whenever the data reaches the policy age.
  2. Setting the access tier to Archive cancels a legal hold on the Blob.
  3. Immutable retention or legal hold protection prevails over conflicting lifecycle deletion until the restriction no longer applies.
  4. Using a storage account SAS with delete permission overrides immutability.

Explanation

Correct Answer

C:

WORM and legal hold restrictions are intended to prevent unauthorized or premature deletion, including by lifecycle jobs.

Incorrect Answers

A:

Azure Storage enforces supported immutability despite lifecycle policy conditions.

B:

Archive tier does not remove WORM retention or legal hold controls.

D:

A SAS grants delegated permissions but cannot bypass the service’s immutability policy.

Question 380

A log-ingestion service writes continually to an Azure append blob using Append Block. Blob versioning is enabled on the account, but compliance expects an automatically generated previous version for every append. What should the administrator explain and recommend?

  1. Each Append Block call creates a separate immutable previous version, so no other control is necessary.
  2. Blob versioning must be disabled for every block blob because the account also contains an append blob.
  3. Changing the append blob metadata after ingestion automatically recreates every intermediate pre-append state as individual versions.
  4. Append Block does not create an automatic blob version for each append; use a supported explicit snapshot or another history/capture strategy when individual append states must be retained.

Explanation

Correct Answer

D:

Microsoft lists Append Block among write operations that do not trigger creation of an automatic blob version. If the business requires a recoverable state after each append, take supported explicit snapshots or implement another separately recorded history mechanism.

Incorrect Answers

A:

Azure Blob versioning does not create a new version for every Append Block operation. Assuming that each append automatically preserves a recoverable pre-append state can leave gaps in the organization’s required history.

B:

Blob versioning can still be enabled for the account and can retain prior versions when eligible write operations occur. The presence of an append blob does not force versioning off for all block blobs in the account.

C:

Setting blob metadata cannot retroactively reconstruct each earlier append state. An additional metadata write changes metadata but does not recreate the historical byte sequences that were never independently captured.