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 32

Question 310

A new Azure Storage account must use a customer-managed encryption key held in Azure Key Vault. The storage account managed identity already has the required key permissions, and the vault has soft delete enabled, but purge protection is currently disabled. What additional vault setting is required?

  1. Create a user-delegation SAS for every Blob container so the key cannot be purged.
  2. Enable purge protection on the Key Vault before configuring Storage encryption with that customer-managed key.
  3. Disable Key Vault soft delete so key versions can be removed immediately.
  4. Rotate the storage account shared access keys because they are the customer-managed encryption root key.

Explanation

Correct Answer

B:

Azure Storage customer-managed keys in Key Vault require both soft delete and purge protection so the key cannot be permanently purged while storage remains dependent on it. Soft delete is already enabled in the scenario, making purge protection the missing prerequisite.

Incorrect Answers

A:

User-delegation SAS tokens authorize Blob requests; they neither protect Key Vault keys from permanent deletion nor meet Azure Storage customer-managed encryption prerequisites. Issuing them per container does not enable vault purge protection.

C:

Disabling soft delete does not meet the documented configuration requirement and would weaken key recovery protections. Soft delete is required for supported Key Vault-backed storage customer-managed encryption, not a feature to turn off.

D:

Azure Storage account access keys authenticate shared-key requests; they are unrelated to the Key Vault encryption key used for customer-managed server-side encryption. Regenerating them cannot enable Key Vault purge protection.

Question 311

An operations runbook proposes rotating Azure Storage account access keys to comply with a requirement to rotate the Key Vault customer-managed key used for data at rest. Which statement corrects the runbook?

  1. Regenerating an account access key automatically rotates the Key Vault customer-managed encryption key.
  2. A storage account access key and an encryption key are interchangeable if both are generated by Azure.
  3. Disabling TLS forces the storage service to use a newly generated Key Vault key.
  4. Rotate the customer-managed key version through Key Vault and maintain the storage managed identity’s key access; account access keys are separate request-signing credentials.

Explanation

Correct Answer

D:

Key version rotation is a Key Vault lifecycle task; Azure Storage can discover a new version automatically if configured. Keep crypto permissions and old-key availability through the transition.

Incorrect Answers

A:

Account key regeneration changes shared-key authorization secrets, not the Key Vault key version protecting stored data.

B:

These secrets serve different purposes: client request authentication versus encryption-key hierarchy.

C:

TLS governs encryption during transport, not the Key Vault key selected for at-rest storage encryption.

Question 312

A storage account that uses a customer-managed Key Vault key now reports encryption-key failures because the referenced key was disabled yesterday. The key object and its identity permissions still exist. What is the recovery action?

  1. Regenerate the storage account shared access keys and leave the Key Vault key disabled.
  2. Re-enable the referenced Key Vault key, verify the storage managed identity can use it, and confirm service access recovers.
  3. Enable anonymous Blob access so requests no longer require encryption-key access.
  4. Set the container access tier to Hot so encryption can be bypassed.

Explanation

Correct Answer

B:

A disabled Key Vault key cannot perform required cryptographic operations. Restore availability of the referenced key and its permissions, then validate recovery.

Incorrect Answers

A:

Storage access keys do not repair a disabled encryption key in Key Vault.

C:

Anonymous authorization has no bearing on service-side customer-managed encryption-key availability.

D:

Blob access tiers alter pricing and retrieval behavior, not whether the configured account encryption key is usable.

Question 313

The research team is planning two new Blob containers in storage account stresearch; neither container exists yet. Legal files must use a customer-managed encryption key different from the one for ordinary research data, and uploads into the legal container must not override that key. Which configuration meets the requirement without another storage account?

  1. Create a customer-managed-key encryption scope, then create the legal container with that scope as its default and prohibit scope overrides.
  2. Set both containers to the same storage account default encryption key and use different blob access tiers.
  3. Enable a CanNotDelete management lock on the restricted container instead of changing its encryption scope.
  4. Use two shared access signature signing keys from the storage account as the at-rest data encryption keys.

Explanation

Correct Answer

A:

An Azure Blob encryption scope can use a Key Vault customer-managed key to isolate encryption within one storage account. Create the scope first, then specify it as the legal container’s default encryption scope when the container is created, and disallow overrides so future uploads cannot select a different scope. This does not automatically re-encrypt blobs already stored elsewhere; the case deliberately specifies new, unprovisioned containers. Choosing a different access tier or storage account key cannot establish the required at-rest customer-key boundary.

Incorrect Answers

B:

Blob access tiers govern storage economics and retrieval frequency; they do not change which key protects data at rest. Applying the same account-scoped encryption key to both containers would not satisfy the requirement for a different key boundary. The approved scope must be attached to the relevant data.

C:

Resource locks restrict supported management-plane operations and do not establish independent at-rest encryption key scopes for Blob data. Even if a lock prevents an administrator from deleting a management resource, it cannot select a different Key Vault key to encrypt the specified container’s blobs.

D:

Storage access keys sign data requests and shared access signatures; they are authentication credentials, not the at-rest encryption scope selection mechanism. Changing an account key does not isolate the legal container’s encryption key from other data. Use a supported encryption scope with explicit key management instead.

Question 314

A read-only operations analyst must browse Blob containers in three Azure subscriptions using Azure Storage Explorer. Company policy requires Microsoft Entra sign-in and RBAC, prohibits shared keys and SAS connections, and the analyst already has suitable Blob Data Reader permissions. How should the analyst connect?

  1. Sign into Storage Explorer with the approved Microsoft Entra account, select the accessible subscriptions, and browse the authorized Blob containers.
  2. Request a storage account access key for each account and attach with shared-key authentication.
  3. Attach one container SAS URL and assume it exposes all containers across three subscriptions.
  4. Remove the storage accounts’ network rules and browse anonymously without an authenticated data role.

Explanation

Correct Answer

A:

Storage Explorer supports Microsoft Entra sign-in and respects authorized Azure resource and data-plane roles. This meets the stated prohibition on keys and SAS while limiting visibility to allowed resources.

Incorrect Answers

B:

Account keys provide broad shared-key access and directly violate the organization’s authorization requirement.

C:

A container SAS is scoped to its signed resource and permissions; it cannot discover every account’s resources and is expressly forbidden here.

D:

Anonymous browsing is neither required nor allowed for the protected containers. Network reachability alone does not grant the analyst data access.

Question 315

An outside contractor has no Microsoft Entra guest identity in the tenant but must download objects from one approved Blob container using desktop Azure Storage Explorer for the next 24 hours. Account keys must not be shared, and no other containers may be read. Which connection method meets this?

  1. Send the contractor the storage account access key and ask them to sign in using Shared Key.
  2. Give the contractor a subscription-wide Owner assignment so Storage Explorer can discover every storage account.
  3. Create an unauthenticated public container and let the contractor download from it indefinitely.
  4. Issue a read/list SAS URL scoped to the approved container with a 24-hour expiry and have Storage Explorer attach to that container URL.

Explanation

Correct Answer

D:

Storage Explorer supports attaching to a Blob container by a signed SAS URL. A container-scoped SAS with read/list permissions and a short expiry can delegate the requested access without disclosing an account key.

Incorrect Answers

A:

An account key grants substantially broader authority than a 24-hour download and explicitly violates the restriction against sharing keys.

B:

Subscription Owner is excessive and would require identity onboarding. It is unrelated to the specifically delegated container access needed here.

C:

Making the container anonymously public abandons the signed, time-bound access requirement and exposes it to additional visitors.

Question 316

An analyst has Microsoft Entra sign-in to Storage Explorer but receives authorization failure when uploading a new blob to an existing private test container. Network access is already permitted. What is required?

  1. Grant the analyst an eligible Blob write data role at the container scope and upload with Storage Explorer.
  2. Assign Azure subscription Reader, which automatically grants Blob upload privileges.
  3. Enable anonymous read access to allow authenticated uploads.
  4. Rotate the account encryption key instead of granting data-plane write permissions.

Explanation

Correct Answer

A:

A role such as Storage Blob Data Contributor grants upload/write permissions at an appropriate scope; signing in alone does not.

Incorrect Answers

B:

Reader is a management-plane read permission and does not confer Blob content write rights.

C:

Anonymous public read does not grant authenticated write permissions and unnecessarily exposes data.

D:

At-rest key rotation does not resolve a missing data-plane authorization grant.

Question 317

Before deleting a retired blob, an analyst needs to compare its actual bytes with a retained local reference copy. They can browse the container in Storage Explorer and have data read rights. What should they do?

  1. Download/open the blob using Storage Explorer and compare content or a trusted checksum against the retained reference before deleting.
  2. Compare only the blob display name with the local filename, without reading either file.
  3. Rotate the storage account access key to force the two copies to match.
  4. Use the Blob access tier property as proof that byte contents are identical.

Explanation

Correct Answer

A:

Storage Explorer can open or download selected blobs. A byte-level comparison or trusted checksum establishes whether their contents match.

Incorrect Answers

B:

Matching object names do not prove content equality.

C:

Key rotation changes access credentials, not the contents of either copy.

D:

Hot/Cool/Archive tier metadata describes storage characteristics rather than file equivalence.

Question 318

An analyst has Storage Blob Data Reader on container `recon` in storage account `stlogs`, and a direct SDK read using Microsoft Entra authentication succeeds. In Azure Storage Explorer, the storage account does not appear in the subscription tree because the analyst has no Azure management-plane Reader assignment. The security team will not grant broader management-plane visibility. The analyst knows the container URL `https://stlogs.blob.core.windows.net/recon`. How can the analyst browse this container in Storage Explorer without changing RBAC?

  1. Grant subscription-wide Reader so Storage Explorer can enumerate every storage account, even though broader management-plane visibility is prohibited.
  2. Use the Storage Explorer Connect dialog to attach directly to the Blob container by its URL, selecting Microsoft Entra ID sign-in in the correct tenant.
  3. Obtain and distribute the storage account key and connect to the entire account instead of using the existing scoped Entra data permission.
  4. Upgrade the analyst to Storage Blob Data Contributor at the container and retry the subscription tree without a management-plane Reader role.

Explanation

Correct Answer

B:

Storage Explorer can attach directly to a supported Blob container through its resource URL with Microsoft Entra sign-in, even when it cannot enumerate the account in the subscription browser. The existing container-scoped Storage Blob Data Reader role can then authorize listing and reading blobs without granting broader management-plane Reader.

Incorrect Answers

A:

Azure Reader would let Storage Explorer discover management-plane resources, but subscription-level Reader widens the analyst’s management visibility beyond the stated authorization boundary. The question explicitly forbids that grant, so it is not the acceptable remedy.

C:

An account key grants broad account-level data access and would discard the intended identity- and container-scoped access model. Storage Explorer supports direct Entra attachment, so distributing an account key is unnecessary and contrary to least privilege.

D:

Storage Blob Data Contributor adds write/delete data permissions but does not add the Azure Resource Manager Reader permissions required to enumerate storage accounts. The missing subscription-tree entry is a discovery limitation; direct resource attachment solves it without elevating data privileges.

Question 319

A developer must copy a blob from one private container to another using Storage Explorer without changing either container’s public-access settings. Which operation and privileges are appropriate?

  1. Use Storage Explorer Copy and Paste with permission to read the source and write the destination.
  2. Make both containers publicly writable, then drag the blob between them anonymously.
  3. Regenerate the source account key; copying does not require access to the destination.
  4. Change the source to Archive and assume the paste operation will automatically rehydrate it.

Explanation

Correct Answer

A:

Storage Explorer supports Copy and Paste between Blob containers. A protected copy must be authorized at the source and destination.

Incorrect Answers

B:

Public anonymous write is neither the documented path nor an acceptable security prerequisite.

C:

A new source access key does not grant required destination Blob permissions.

D:

Archive-tier transitions and rehydration are separate storage operations, not automatic copy authorization.

Question 320

An external auditor needs temporary read access to exactly one private Azure Files share through desktop Storage Explorer. They have no tenant identity and must not receive a storage account key. Which connection is best?

  1. Give the auditor the account’s primary Shared Key so all file shares can be discovered.
  2. Enable anonymous read access for the Azure Files share as if it were a public Blob container.
  3. Give the auditor the public SMB UNC path without any authorization mechanism.
  4. Attach the single Azure Files share using a time-limited, read/list SAS URL with permissions scoped to that share.

Explanation

Correct Answer

D:

Storage Explorer supports SAS-based attachment for an individual Azure Files share; its validity and permissions can be limited without exposing the account key.

Incorrect Answers

A:

An account key is an overly broad credential and violates the instruction not to share one.

B:

Azure Files shares are not exposed by simply enabling Blob container anonymous-access settings.

C:

An SMB path still requires reachable service endpoints and appropriate credentials.