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 11

Question 100

An operations analyst needs to inspect containers, upload a handful of blobs and verify object metadata from their workstation without memorizing CLI syntax. Which Microsoft tool best matches?

  1. Use Azure Storage Explorer with appropriately scoped authentication to browse and manage permitted storage resources.
  2. Use the Azure Portal Storage browser instead of Storage Explorer, and treat the portal as a standalone desktop browser with local multi-account credential profiles.
  3. Use AzCopy to upload bytes and it exposes a graphical desktop window for browsing blob metadata and containers.
  4. Use Azure Data Explorer as the desktop storage-account file management application, and treat its KQL interface as a means to upload individual blobs.

Explanation

Correct Answer

A:

Storage Explorer offers a graphical interface for storage operations and honors supported credentials/permissions. It is distinct from a high-throughput scripted transfer tool.

Incorrect Answers

B:

Portal browsing is an interactive administrative option, but the requested Microsoft desktop graphical tool is Azure Storage Explorer.

C:

AzCopy is a command-line bulk-transfer utility rather than the requested interactive desktop file explorer.

D:

Azure Data Explorer is an analytics service, not the Azure Storage Explorer graphical client for object operations and scoped credentials.

Question 101

An administrator enabled Blob soft delete and later an operator deletes an entire container. Recovery fails because container retention was never configured. What protection should have been enabled for that deletion mode?

  1. Increase individual blob soft-delete retention to 90 days but keep container soft delete disabled.
  2. Enable blob versioning plus blob soft delete but leave container soft delete disabled and it handles container namespace removal.
  3. Enable Blob versioning only and it will recreate a deleted container namespace with all contents automatically.
  4. Enable container soft delete with suitable retention in addition to individual Blob soft delete.

Explanation

Correct Answer

D:

Blob and container deletion are distinct protection scopes. Container soft delete is needed to restore a deleted container and its contents within retention.

Incorrect Answers

A:

Blob soft delete covers individual blobs; protection for an entirely deleted container is a separate container soft-delete setting.

B:

Blob versions and per-blob soft deletion do not substitute for the setting that retains an accidentally deleted container as a unit.

C:

Versioning does not replace the container soft-delete retention feature needed to recover a deleted container.

Question 102

Container soft delete was enabled. An application deleted a container named reports and later recreated a new empty reports container. The administrator now tries to restore the deleted original and receives a name-conflict error. What should they do?

  1. Enable blob versioning on the storage account and it will automatically rename the conflicting active container.
  2. Preserve any new data, remove the conflicting active reports container, and restore the deleted container to its original name while retention remains.
  3. Create a third container named reports-old and Azure will restore the deleted container under that new name.
  4. Attempt to undelete the old reports container while leaving the newly created active reports container in place with the same name.

Explanation

Correct Answer

B:

Soft-deleted Azure containers are restored only to their original names. The active name collision must be resolved first, and any recently written data in the replacement container must be preserved before removing it.

Incorrect Answers

A:

Blob object versions do not rename an active container or remove the name conflict that prevents undeleting a different deleted container.

C:

Container soft delete restores to the original container name. An arbitrary new name does not satisfy that restore operation.

D:

A conflicting current container name must be cleared safely before the deleted container can be restored to that original name.

Question 103

A data pipeline overwrites its source manifest several times daily. The operator needs a manually controlled immutable-in-time copy of its state immediately before a risky deployment, without changing the live blob name. What storage feature fits?

  1. Create a Blob snapshot of the current object before deployment and retain its identifier.
  2. Enable Blob versioning for the storage account and use its automatic version creation as the explicitly timed manual snapshot of the manifest.
  3. Write the planned deployment timestamp into blob metadata and later use that metadata value to retrieve the prior blob contents.
  4. Rely solely on blob soft-delete retention to provide the manually named pre-deployment point-in-time snapshot without executing a snapshot operation.

Explanation

Correct Answer

A:

A blob snapshot captures a read-only point-in-time state of that blob. It can be used for later comparison or restore operations.

Incorrect Answers

B:

Automatic versioning retains prior versions as supported write operations occur, but it is not the same as explicitly creating and identifying a snapshot immediately before the deployment.

C:

Custom metadata labels an object but does not record an immutable historical content copy. Creating a snapshot captures the desired pre-change state.

D:

Soft delete can help recover eligible deleted or overwritten blob states, but it does not substitute for creating a controlled, identifiable snapshot at the exact chosen deployment checkpoint.

Question 104

A team needs to prevent a single Azure Files share from growing beyond its approved allocation while other shares continue operating. What should the administrator configure?

  1. Create an Azure Policy that audits storage share capacity but never change the specific Azure Files share quota.
  2. Increase the storage account aggregate capacity allocation but leave the individual Azure Files share quota unlimited.
  3. Set the Azure file share quota to the appropriate supported capacity limit.
  4. Enable blob lifecycle tiering on the account and it caps how much data clients can place in an SMB Azure Files share.

Explanation

Correct Answer

C:

A share quota constrains the provisioned or maximum capacity for that share as supported by the share tier. It is more targeted than an account-wide assumption.

Incorrect Answers

A:

An audit policy reports state, not a hard storage consumption limit on the share. The share-level quota enforces the allocation.

B:

An account-level allowance does not enforce the specified per-share cap on one file share.

D:

Blob lifecycle actions do not enforce an Azure Files share-specific capacity quota.

Question 105

A flat-namespace storage account has a Blob container named project-data. Its blob names start with either audit/ or live/. Only audit/ block blobs older than 90 days should move to a supported cooler tier. What lifecycle-rule configuration has the intended narrow scope?

  1. Set prefixMatch to project-data/audit/ and use a supported 90-day age condition for eligible blobs.
  2. Set the storage-account default access tier to Cool and only old audit/ blobs are selectively transitioned.
  3. Use a lifecycle rule with no prefix filter, applying its 90-day condition to every eligible blob in the account.
  4. Set prefixMatch to audit/ without the project-data container name and it selects that directory inside project-data.

Explanation

Correct Answer

A:

Microsoft requires a prefixMatch string to start with the container name. project-data/audit/ selects blob names beginning audit/ in project-data; the age condition limits when eligible blobs transition.

Incorrect Answers

B:

A storage-account default access tier does not selectively transition only the audit/ blob names after 90 days. Use a scoped lifecycle rule for the described set.

C:

Without a prefix filter the age action can affect live/ and other blobs in that account; it does not enforce the requested audit/ scope.

D:

For Azure Blob lifecycle management, prefixMatch must start with the container name. The bare audit/ value would be interpreted as a container-name prefix, not the directory of project-data.

Question 106

A CI workflow holds a correct Bicep file but receives AuthorizationFailed when deploying a storage account into another team’s resource group. What should the owner check?

  1. Assign Reader only and it allows resource creation.
  2. Grant the pipeline identity the required Azure resource-management actions at the target deployment scope.
  3. Run Bicep validation and what-if successfully and the pipeline identity automatically gains resource write permissions.
  4. Add the target resource group name as a pipeline environment variable, without adjusting the identity’s denied role actions.

Explanation

Correct Answer

B:

Template validity cannot override Azure authorization. The deployment identity needs sufficient permissions where the resources will be created.

Incorrect Answers

A:

Reader does not include write resource-management actions. It cannot perform the requested deployment.

C:

Template checks describe potential deployment changes but do not grant Microsoft.Authorization permissions at the intended Azure scope.

D:

Correcting a group name or input does not resolve AuthorizationFailed when the deployment principal lacks resource-management write permissions.

Question 107

A template must provision twelve similarly configured development storage accounts with distinct names derived from an approved list. The team wants one maintainable resource declaration. Which Bicep construct fits?

  1. Write twelve unrelated Bicep source files and hand-edit differences for every deployment.
  2. Create twelve conditional Bicep resources with a fixed hard-coded name instead of iterating over twelve distinct approved names.
  3. Use a Bicep resource loop over the approved names or configuration array.
  4. Call one Bicep module once without any resource or module loop and it will create a resource for every value in the input list.

Explanation

Correct Answer

C:

Bicep loops express repeated resource creation without manually duplicating the entire definition. Names and scope must be validated for uniqueness and service constraints.

Incorrect Answers

A:

Duplicated definitions are harder to maintain and more prone to drift. The resources differ primarily by inputs.

B:

A hard-coded name duplicates the same resource identity and cannot create the intended set of distinct storage accounts.

D:

One module invocation does not automatically iterate over list entries. A loop or explicit instances are required for twelve resources.

Question 108

A Bicep deployment requires an administrator password from a protected pipeline secret store. The team must avoid exposing it in deployment logs or a plain parameter file. What configuration is appropriate?

  1. Pass the pipeline secret as an ordinary Bicep string parameter and rely on the repository remaining private to protect deployment history.
  2. Set a normal string parameter with a hard-coded password committed to Git.
  3. Declare a secure parameter and pass the secret through a protected runtime mechanism such as Key Vault reference or secure pipeline input.
  4. Use a secure Bicep parameter but echo its value to the CI job log before deployment for debugging purposes.

Explanation

Correct Answer

C:

Secure parameters help protect sensitive deployment inputs from routine logging. Secret handling also requires avoiding direct output or committing plaintext values.

Incorrect Answers

A:

A normal string parameter can be exposed through deployment surfaces. Secure parameter handling and protected secret injection are needed.

B:

An ordinary checked-in string can expose credentials to repository readers and deployment history. It does not satisfy the secret protection requirement.

D:

Marking the parameter secure is not sufficient if the pipeline itself prints the secret to a log. Avoid secret exposure end to end.

Question 109

A Bicep deployment provisions a storage account and the next pipeline task needs its resource ID. The pipeline cannot safely guess the generated name. How should the template expose this information?

  1. Declare an output containing the created resource ID and consume that deployment output downstream.
  2. Predict the resource ID by concatenating the account display name and subscription name in a local script without reading deployment output.
  3. Store the ID as a comment in the Bicep file before it is deployed.
  4. Add the created account ID to its own resource tag only and a downstream pipeline can read that tag before deployment completes.

Explanation

Correct Answer

A:

Outputs export selected deployment values as part of the ARM deployment result. This is more reliable than guessing a resource identifier after creation.

Incorrect Answers

B:

Friendly names do not fully encode Azure resource IDs and scopes. An output tied to the deployed resource is safer.

C:

A static comment cannot know a runtime-generated resource ID. It is not a deployment result interface.

D:

A tag on the deployed resource cannot provide the downstream pipeline with a reliable deployment output without a separate read.

Question 110

A Bicep template uses an existing resource declaration for a Key Vault in subscription A but the deployment runs in subscription B. Deployment cannot resolve the vault because the scope is assumed incorrectly. What must change?

  1. Grant the pipeline Reader at the target subscription while leaving the cross-subscription Key Vault existing-resource scope unchanged.
  2. Declare the Key Vault at the default deployment subscription scope and Bicep will search all other subscriptions automatically.
  3. Use an account-level name variable for the Key Vault but leave the existing-resource scope tied to the deployment subscription.
  4. Specify the correct supported resource scope and identity for the existing Key Vault reference.

Explanation

Correct Answer

D:

Existing-resource references resolve resources at their declared scope. Cross-scope references must explicitly target the correct subscription/resource group where supported.

Incorrect Answers

A:

RBAC may permit reads but does not direct Bicep to the correct subscription and resource-group scope for the referenced vault.

B:

An existing-resource declaration resolves according to an explicit or default scope. Cross-subscription resources require the correct scope.

C:

Changing the resource name input does not change which Azure subscription contains the referenced Key Vault.