McAfee-Secured Website

Exam Bundle

Exam Code: AZ-104

Exam Name Microsoft Azure Administrator

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Azure Administrator Associate

Microsoft AZ-104 Bundle $44.99

100% Microsoft AZ-104 Guaranteed Success With Testking Training Materials

Get Real AZ-104 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    AZ-104 Questions & Answers

    606 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual AZ-104 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • AZ-104 Video Course

    AZ-104 Video Course

    132 Video Lectures

    AZ-104 Video Course is developed by Microsoft Professionals to help you pass the AZ-104 exam.

    Description

    This course will improve your knowledge and skills required to pass Microsoft Azure Administrator exam.
  • Study Guide

    AZ-104 Study Guide

    458 PDF Pages

    Developed by industry experts, this 458-page guide spells out in painstaking detail all of the information you need to ace AZ-104 exam.

Microsoft Azure Administrator (AZ-104) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    606 Questions

    $124.99
  • AZ-104 Video Course

    Video Course

    132 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    458 PDF Pages

    $29.99

Microsoft AZ-104 Practice Test 26

Question 250

After a regional storage outage, operators want to estimate how many recent writes might not be present in the secondary GRS copy. Which information is pertinent?

  1. Examine the last synchronization time and asynchronous replication state for the affected account.
  2. Every acknowledged write is synchronously in the secondary region.
  3. Use only the primary account’s latest successful availability metric as an exact timestamp for the most recent secondary-region commit.
  4. Compare only the most recent primary-side Blob modification time without consulting the geo-replication synchronization status.

Explanation

Correct Answer

A:

Last sync status provides evidence of replication lag and potential recovery point exposure. Asynchronous geo replication cannot guarantee zero data loss at failover.

Incorrect Answers

B:

GRS cross-region copies are asynchronous rather than synchronously guaranteed at every client acknowledgement.

C:

Availability of the primary endpoint does not indicate which acknowledged writes have reached the asynchronously updated secondary replica.

D:

Primary writes may not yet be present in the secondary. Last sync status gives evidence of secondary replication lag.

Question 251

A team notices that a deleted blob passed the configured seven-day soft-delete window yesterday. They increase retention to thirty days and expect the object to reappear. What is the limitation?

  1. Every retention increase automatically recreates all previously purged blobs.
  2. Create a new container soft-delete retention policy and it will reconstruct a Blob object already purged from retention.
  3. Enable ZRS and surviving availability-zone replicas recreate an object removed by completed logical deletion.
  4. Increasing future soft-delete retention does not restore objects already permanently removed after their earlier retention expired.

Explanation

Correct Answer

D:

Retention policies protect eligible deletions during their effective window. Once data is permanently purged, a later policy increase cannot retroactively preserve it.

Incorrect Answers

A:

Retention changes are not an unlimited historical recovery mechanism.

B:

Container soft delete protects deleted containers, not restoration of a previously expired and permanently removed individual blob.

C:

Zone redundancy protects against infrastructure failures, not permanent logical deletions after the retention window.

Question 252

A business-critical archived blob must be read sooner than a standard rehydration typically permits, and the storage account supports priority retrieval. Which administrative option should be evaluated?

  1. Repeat a Standard-priority archive rehydration request and use the repeated requests as a way to guarantee immediate data availability.
  2. Turn on blob versioning and read a historical version directly from the Archive tier while its offline tier state is unchanged.
  3. Request a supported high-priority archive rehydration while considering its latency and additional cost.
  4. Increase the requester's Storage Blob Data Reader privileges and use the elevated role to bypass the Archive tier's asynchronous rehydration.

Explanation

Correct Answer

C:

Rehydration priority can influence processing time where supported but may cost more. Archive tier still requires an online access transition or copy.

Incorrect Answers

A:

Standard rehydration is asynchronous; submitting more requests does not guarantee instant retrieval. High-priority rehydration is the documented accelerated option when supported.

B:

Versioning preserves eligible object history but does not make archive-tier content accessible through ordinary online reads without rehydration.

D:

Authorization to read an object does not change whether its bytes are currently offline in Archive. Access requires a supported online-tier rehydration or copy.

Question 253

A media archive team wants to move blobs to a cheaper tier only after no reads for 120 days. Their lifecycle rules currently consider last modification but not reads. What capability should be investigated?

  1. Enable Blob change feed alone and interpret write events as a complete record of every read.
  2. Enable supported last-access-time tracking and apply an eligible lifecycle condition based on access recency.
  3. Use only a modification-age rule, and every read updates the blob modification timestamp.
  4. Assign Reader on a storage account to update the last-access timestamp for individual blobs.

Explanation

Correct Answer

B:

Last access time tracking supports access-based lifecycle patterns for eligible blobs, with service-specific update behavior and limits.

Incorrect Answers

A:

Change feed records supported changes, not a direct per-blob last-read timestamp needed by an access-based lifecycle rule.

C:

Reading an object does not mean the blob has been modified; last-access tracking provides a separate supported access recency signal.

D:

Azure management Reader is an authorization role, not a signal collection feature.

Question 254

One storage account hosts production and scratch Azure Files shares. Only the production share should receive protected daily backup with thirty-day retention. How should administrators scope protection?

  1. Enable Blob versioning on the account and treat it as Azure Files share backup.
  2. Enroll the specific eligible production file share in Azure Backup and assign a policy matching its frequency and retention.
  3. Apply one backup policy to the storage account and it automatically protects every existing and future share.
  4. Create a production-share tag named BackedUp without enrolling the share in a backup policy.

Explanation

Correct Answer

B:

Azure Files backup protection is configured for supported selected file shares. The actual protected item and recovery points must be checked.

Incorrect Answers

A:

Blob object versioning is not a substitute for file-share backup jobs and recovery points.

C:

Account existence alone does not mean every share is enrolled in backup protection.

D:

A tag is descriptive metadata and does not create managed recovery points or thirty-day backup retention.

Question 255

A storage admin enabled blob versioning and now needs to delete old previous versions after 180 days while retaining the current base blob. What policy target is appropriate?

  1. Turn off Blob versioning and previously created versions are automatically retained forever.
  2. Apply a lifecycle delete action to the current base blob only, and treat the delete action as removal of just historical versions.
  3. Use a lifecycle action targeting previous versions with daysAfterCreationGreaterThan set to 180 days.
  4. Delete current base blobs after 180 days, and the previous-version retention requirement is met.

Explanation

Correct Answer

C:

Microsoft supports lifecycle actions targeting previous versions with daysAfterCreationGreaterThan. A prior version’s age is measured from when that version was first written, not when it became noncurrent.

Incorrect Answers

A:

Disabling versioning changes new writes but does not automatically establish indefinite retention for old versions.

B:

A baseBlob lifecycle action targets current blobs; it does not perform a version-only cleanup while preserving the live base blob.

D:

Deleting current base blobs targets live data rather than the previous versions specified in the requirement and risks losing the actively served content.

Question 256

A developer changed a Bicep file and wants to catch syntax and type errors locally without contacting an Azure subscription or changing resources. Which operation fits?

  1. Run an Azure Resource Manager deployment validation against the production subscription, because this is entirely local.
  2. Rename the .bicep file to .json without compiling the Bicep syntax.
  3. Run the Bicep build or validation tooling locally and inspect compilation diagnostics before deployment.
  4. Run the production deployment first to discover every syntax problem.

Explanation

Correct Answer

C:

Bicep build compiles the source to ARM JSON and reports many language or type errors without deploying resources. Runtime scope and permissions remain separate checks.

Incorrect Answers

A:

An Azure deployment validate command depends on the target Azure control plane; Bicep build can catch syntax and type errors locally without contacting Azure.

B:

Changing the extension does not transform Bicep source into a valid ARM JSON template or perform compilation diagnostics.

D:

Production deployment is unnecessary and risky for errors detectable earlier.

Question 257

Two Bicep resources in one deployment must reference the same newly created storage account. A developer manually concatenates its subscription, group and name into several IDs. What is a more maintainable approach?

  1. Pass a manually constructed storage resource ID into each dependent module even though both resources are declared together.
  2. Copy the manually concatenated ID strings into more templates for consistency.
  3. Reference the storage account's Bicep resource symbol and use its id property in dependent resources.
  4. Hard-code the storage account name in each dependent resource and omit the resource symbol and ID relationship.

Explanation

Correct Answer

C:

Symbolic references keep dependent resource identities aligned and can create implicit dependencies. They avoid brittle repeated string construction.

Incorrect Answers

A:

Manually repeated IDs remain brittle across subscription and resource-group changes compared with a single symbolic resource reference.

B:

Duplicating hand-built IDs increases the chance of scope or name errors.

D:

Hard-coding repeats environment-specific details and weakens deployment dependency tracking compared with symbolic references.

Question 258

A Bicep file successfully builds locally but Azure deployment fails with AuthorizationFailed for the target resource group. What should the pipeline operator inspect?

  1. Change the Bicep resource declaration from an existing resource reference to a new resource deployment while retrying under the same unauthorized pipeline principal.
  2. Run the Bicep linter again and fixing all style warnings automatically grants the pipeline its missing Azure RBAC rights.
  3. Validate deployment principal RBAC actions at the requested scope rather than treating successful compilation as Azure authorization.
  4. Give the deployment service principal Reader at the target resource group and it will create new resources.

Explanation

Correct Answer

C:

Compilation verifies language structure, not the identity's permission to create resources. The deployment principal must be authorized at the destination scope.

Incorrect Answers

A:

Changing an existing-versus-new resource declaration does not grant the pipeline principal missing Microsoft.Authorization or resource-provider write permissions at the deployment target. Inspect and repair RBAC scope and actions.

B:

Source linting and resource-scope permissions are distinct. Successful lint/build does not authorize management writes.

D:

Reader permits inspection but not the necessary deployment write operations. Suitable scoped authorization is required.

Question 259

A platform team publishes reusable Bicep modules to a managed registry. Application pipelines should produce repeatable deployments even when the shared module is updated. Which practice reduces accidental change?

  1. Pin only the module registry hostname while letting every module reference resolve to an unreviewed changing version.
  2. Use a floating version alias pointing to the most recently published module for every production deployment.
  3. Always use an unreviewed mutable latest tag in every production deployment.
  4. Reference a reviewed version of the module and control upgrades through a deliberate versioning process.

Explanation

Correct Answer

D:

Version-pinned module references help make infrastructure builds reproducible. Upgrades should be tested and promoted intentionally.

Incorrect Answers

A:

Pinning the registry server is not equivalent to selecting a reviewed module version; builds could still resolve changed module content.

B:

A moving alias can switch the implementation without application review; a controlled version reference improves repeatability.

C:

Uncontrolled moving tags can introduce new resource behavior without application review.

Question 260

A Bicep template receives an administrator credential as a secure parameter. A developer then declares a normal output containing the plaintext password. Which risk should the reviewer flag?

  1. The secure parameter automatically encrypts every ordinary output referencing it.
  2. Secrets must not be exposed through ordinary deployment outputs; use supported secure handling and avoid emitting credentials.
  3. Store the plaintext password in a normal output named securePassword, and the output identifier itself prevents deployment-history disclosure.
  4. Mark the input secure but leave the output a normal string, and the input decorator protects its downstream output value.

Explanation

Correct Answer

B:

Deployment outputs can be visible through deployment records and pipelines. Secure input alone does not make a plaintext output safe.

Incorrect Answers

A:

A secure parameter protects the input handling but does not justify echoing the value in output.

C:

An output name has no secret-protection semantics. A normal deployment output can expose its value through deployment operations or pipeline logs.

D:

The input’s secure designation does not make an ordinary plaintext output safe to disclose. Avoid exporting the credential.