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 47

Question 460

A storage account is protected by a ReadOnly Azure Resource Manager lock. An administrator has Owner role but the portal cannot list the account access keys. What is the likely cause?

  1. Enable Blob soft delete to allow read-only management operations and retention settings unlock key-listing calls.
  2. Storage access key listing is always unrestricted when a principal has subscription Reader.
  3. The ReadOnly management lock also blocks control-plane operations that require POST/write actions, including some key-list operations.
  4. Assign Key Vault Secrets User on the storage account and the new identity role removes the inherited ReadOnly management lock.

Explanation

Correct Answer

C:

An Owner role does not bypass an applicable management lock. A lock can interfere with operations that look observational but use a non-read API.

Incorrect Answers

A:

Data protection settings do not override Azure Resource Manager ReadOnly locks; listKeys is a blocked POST-style management operation.

B:

Reader does not universally authorize sensitive account key retrieval and a lock may still restrict the control-plane call.

D:

Key Vault data roles do not grant Azure storage account management or bypass a scope-level ReadOnly resource lock.

Question 461

A VM reaches a storage account through a working Private Link address but Blob downloads return an authorization error. The managed identity has no storage data role. Which distinction best explains the failure?

  1. Assign Network Contributor on the private endpoint resource and network access automatically grants blob content permissions.
  2. Private endpoint networking supplies reachability, but the VM identity still needs appropriate Blob data-plane authorization.
  3. Assign Storage Account Contributor on the account but omit a Blob data-plane role for the Entra-managed identity.
  4. Repair the private DNS mapping again and retry with the same managed identity that has no Blob data role.

Explanation

Correct Answer

B:

The private interface does not grant read/write permissions. RBAC, SAS or an authorized key mechanism must independently authorize the data request.

Incorrect Answers

A:

Network Contributor manages networking but does not grant Storage Blob Data Reader or Contributor access to the blob service data plane.

C:

Storage management roles do not inherently supply the Entra blob data access actions required by the application.

D:

DNS repair addresses endpoint routing, but the scenario already confirms the private endpoint works; an identity without Blob data authorization will still receive a data-plane denial.

Question 462

An analyst is given a Blob service SAS signed with only read and list permissions and reports HTTP 403 when deleting a file. The SAS is otherwise valid and within its time window. What should support check?

  1. Use the same read/list-only SAS but add the delete permission string as an ordinary HTTP query parameter after the signature.
  2. Change the container public access level to Blob and the same signed read-only SAS now permits deletion requests.
  3. Extend the read-only SAS expiration time without reissuing its signed permission set, and a longer lifetime enables delete.
  4. The SAS permissions do not include delete; issue only an appropriately approved token if deletion is truly required.

Explanation

Correct Answer

D:

The signed permission set governs allowed operations. Read/list access does not imply delete rights, regardless of valid time or network access.

Incorrect Answers

A:

SAS permissions are cryptographically signed. Adding an unsigned operation flag cannot grant a missing delete permission.

B:

Anonymous Blob read settings never add SAS delete permission. The token’s signed permissions determine whether delete is authorized.

C:

A longer time window does not change the permissions embedded in the SAS signature. A new appropriately authorized token is needed.

Question 463

A storage administrator wants to flag SAS URLs whose validity is longer than organizational policy permits while allowing legitimate limited-time delegation. Which storage control should be considered?

  1. Set a storage-account SAS expiration policy and use the setting to rewrite expiry timestamps inside already issued signed URLs.
  2. Configure the supported SAS expiration policy and monitor or enforce the maximum allowed validity according to service capabilities.
  3. Create a stored access policy on one container and use its expiry setting as the global lifetime limit for account SAS and user-delegation SAS tokens.
  4. Rotate both storage account keys on a schedule and treat that action as an update of each SAS token's stated expiration interval.

Explanation

Correct Answer

B:

A SAS expiration policy can identify or restrict long-lived delegated tokens; access signatures still need minimal permissions and secure issuance.

Incorrect Answers

A:

An account expiration policy can log or block noncompliant applicable requests, but it cannot edit the cryptographic signed expiry fields of existing SAS URLs.

C:

Stored access policies apply to associated service SAS credentials, not every type of SAS. They do not globally govern account SAS or user-delegation SAS signatures.

D:

Key rotation may invalidate SAS tokens signed with an affected account key; it does not rewrite expiry timestamps or provide a per-token policy-compliance finding.

Question 464

A user-delegation SAS leaked, and security needs to invalidate current signatures derived from its delegation key rather than rotate an account Shared Key. What operation should the response plan evaluate?

  1. Rotate the storage account primary Shared Key but leave the Microsoft Entra user delegation key that signed the compromised SAS valid.
  2. Revoke the user delegation keys for the storage account, recognizing that other SAS tokens signed by those keys may also fail.
  3. Delete the stored access policy on the container, and it will revoke all user delegation SAS tokens signed without such policies.
  4. Rotate only storage key2 and all user delegation signatures are destroyed.

Explanation

Correct Answer

B:

A user delegation SAS is not signed with the storage Shared Key. Revoking delegation keys can invalidate issued user-delegation signatures and affects all dependent tokens.

Incorrect Answers

A:

User delegation SAS signatures rely on their delegation key rather than the Shared Key, so Shared Key rotation does not revoke them.

C:

Stored access policies are not associated with user delegation SAS signatures. Revoking user delegation keys is the relevant operation.

D:

User delegation SAS signatures use an Entra-authorized delegation key rather than the storage account Shared Key.

Question 465

A Blob container already has five distinct stored access policies for service SAS tokens. An administrator attempts to create a sixth policy and receives a validation error. Which quota should they plan around?

  1. Create a sixth stored access policy on a different Blob container and its identifier is automatically valid for SAS URLs signed against the original container.
  2. Convert the affected service SAS URLs into account SAS tokens and the old container stored access policy still controls their expiry centrally.
  3. Add a sixth stored access policy only for read permission, and read-only policies are exempt from the five-policy limit.
  4. Azure Blob containers support a maximum of five stored access policies per container; consolidate identifiers or redesign delegation.

Explanation

Correct Answer

D:

The per-container stored access policy limit is five, independent of the number of individual service SAS URLs issued against those identifiers.

Incorrect Answers

A:

Stored access policies are scoped to their associated storage resource. A policy on another container doesn't authorize or revoke SAS tokens bound to the original container.

B:

Account SAS tokens can't refer to a container stored access policy. Changing SAS type would also remove the centralized policy control the scenario requires.

C:

The limit is on stored policy count, not on their permission combinations. Read-only policies still consume a slot.

Question 466

A customer asks to optimize the network path used for public Azure Storage endpoints, without changing which public client IPs are allowed. Which account configuration affects path preference rather than authorization?

  1. Use a private endpoint and it changes how all public storage requests choose Microsoft or internet routing across the global network.
  2. Modify the storage firewall default action to Deny and treat the access-control decision as an internet-versus-Microsoft network route selection.
  3. Review the supported storage routing preference setting and choose the intended Microsoft global or internet routing path.
  4. Enable RA-GRS to control public traffic routing over Microsoft global network instead of setting storage routing preference.

Explanation

Correct Answer

C:

Routing preference can influence the network path for applicable endpoints; it does not replace storage firewall rules or data credentials.

Incorrect Answers

A:

Private Link offers a private connectivity path but does not replace the storage account’s configured public routing preference.

B:

A firewall restricts who may connect; it does not select the account public endpoint network routing preference.

D:

RA-GRS governs redundancy and secondary read availability, not the routing preference of a storage public endpoint.

Question 467

Two supported Azure Blob accounts use an object replication policy. An engineer assumes a newly uploaded object must be readable at the destination immediately, before the source event has replicated. What should be corrected?

  1. Changing the destination container metadata to Synchronous forces instant replication.
  2. Object replication is asynchronous and destination state may lag; monitor replication status before relying on the copied object.
  3. Increase the object-replication policy rule priority to make the source blob upload and destination commit a single atomic operation.
  4. A successful source write proves destination commit occurred in the same transaction.

Explanation

Correct Answer

B:

The replication policy is not an immediate synchronous commit protocol. Applications needing strict cross-account consistency require a separate design.

Incorrect Answers

A:

Container metadata cannot alter the asynchronous service replication contract.

C:

Object replication does not expose a rule priority that creates synchronous cross-account commit semantics. Destination replication remains asynchronous.

D:

Source and destination replication stages are separate; source success does not guarantee immediate destination availability.

Question 468

A new data lake workload needs directory-like analytics access via Azure Data Lake Storage Gen2. The team is deciding whether to enable hierarchical namespace during account creation. What should they confirm?

  1. Use slash-delimited blob names on a flat-namespace account and implement directory access-control behavior solely through the naming convention.
  2. Enable blob versioning and blob soft delete on the existing flat-namespace account as the mechanism to activate native directories.
  3. Use a supported storage account with hierarchical namespace enabled, and verify compatibility with required blob features before choosing the account design.
  4. Select Archive tier for all analytics objects and use the tier change as the mechanism for assigning Data Lake Gen2 directory ACLs.

Explanation

Correct Answer

C:

Hierarchical namespace supplies directory semantics for Gen2 analytics, but some Blob features and migration constraints depend on account settings.

Incorrect Answers

A:

Slashes in flat Blob object names do not create the native Data Lake Gen2 directory namespace or hierarchical POSIX-style ACL semantics.

B:

Data protection features retain eligible object history; they do not enable the hierarchical namespace needed for the required Data Lake directory operations.

D:

Archive tier controls offline retrieval behavior, not namespace semantics, directory permission inheritance or the enabling of hierarchical namespace.

Question 469

A storage account has public network access disabled. A subnet has a Microsoft.Storage service endpoint but no storage Private Link connection. Its clients cannot connect. What networking distinction explains the failure?

  1. A service endpoint always works without any public service endpoint or private interface.
  2. A service endpoint still accesses the service public endpoint; with public network disabled, the workload needs supported private endpoint connectivity.
  3. Grant Storage Blob Data Owner to every VM to override the service network policy.
  4. Change the account firewall default action to Allow while keeping public network access disabled, and the service endpoint will become usable.

Explanation

Correct Answer

B:

Service endpoints secure selected subnet traffic to a public endpoint. They do not create a private address or override a disabled public endpoint.

Incorrect Answers

A:

Service endpoints are not Private Link; they do not create the internal service NIC required for private-only access.

C:

Data authorization does not bypass a storage account public-network denial.

D:

A permissive default firewall action does not reinstate a publicly disabled Storage endpoint. A private-only client requires an approved private endpoint.

Question 470

A SaaS provider uses one supported Azure Blob storage account for several customers and wants each customer container to use a distinct cryptographic key scope without creating a separate storage account. Which Blob feature supports that design?

  1. Set container-level immutable storage policies for each customer and retention policies select a separate encryption key per container.
  2. Enable account-wide customer-managed encryption with one key and each customer container automatically receives a different key.
  3. Configure customer-specific container names while leaving the account-wide default encryption scope unchanged for every container.
  4. Create separate Blob encryption scopes and configure an appropriate default scope per customer container.

Explanation

Correct Answer

D:

Blob encryption scopes can apply keys at container or object level, including supported customer-managed keys, without relying only on the account-wide default scope.

Incorrect Answers

A:

Immutability enforces retention and delete restrictions, not which cryptographic key scope is used to encrypt the container.

B:

An account-wide key applies to data governed by that account scope. Distinct customer keys require supported separate encryption scopes.

C:

Container names alone do not select encryption scopes; explicitly assign the appropriate default scope for each customer container.