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 25

Question 240

An application identity has Blob Data Reader scoped only to one container. It can read blobs, but Azure rejects its request to obtain a user delegation key for creating SAS links. What is the most targeted authorization fix?

  1. Grant Storage Account Contributor on the entire subscription and distribute its access keys.
  2. Change the storage account redundancy from LRS to GRS.
  3. Give the identity another Blob Data Reader role on the same container.
  4. Grant the generateUserDelegationKey action at an eligible storage-account or higher scope, such as through Storage Blob Delegator.

Explanation

Correct Answer

D:

Get User Delegation Key is a storage-account-level operation requiring Microsoft.Storage/storageAccounts/blobServices/generateUserDelegationKey/action at the storage account, resource group or subscription scope. A container-only data role may authorize reading blobs without permitting that key request. Add a suitable narrowly scoped role such as Storage Blob Delegator at account scope while preserving the existing container data-reader grant. Then issue appropriately limited user delegation SAS tokens and avoid unnecessary account-key access.

Incorrect Answers

A:

Subscription-wide storage management and key handling would exceed the application's need to sign limited Entra-backed tokens. The required delegated key action can be granted more narrowly, for example via Storage Blob Delegator at storage-account scope. Avoid expanding permissions and distributing shared account credentials.

B:

Redundancy controls data replication and availability but has no bearing on whether the caller holds the Azure RBAC action for requesting a user delegation key. The API denial is an authorization scope issue. Assign the correct action at an eligible scope rather than altering storage replication.

C:

Repeating an unchanged container-scoped read role does not grant the storage-account-level generateUserDelegationKey action. The identity may already perform data reads while still lacking permission to request a signing key. Add a suitable role at the correct account-level scope rather than duplicating the data assignment.

Question 241

Five short-lived download links for blobs in the same container must share a centrally adjustable expiry date. The issuing service uses account-key-signed service SAS tokens. What should it configure?

  1. Generate five ad hoc account SAS tokens and expect them to inherit the container policy.
  2. Create an appropriate named container stored access policy and issue service SAS tokens referencing its signed identifier.
  3. Place the expiration date in a resource-group tag instead of a SAS policy.
  4. Grant every link recipient Storage Blob Data Owner on the subscription.

Explanation

Correct Answer

B:

A container stored access policy can hold validity and permission terms used by eligible service SAS tokens. Each linked token references the policy identifier, so a permitted update to that one policy can adjust the shared expiration or revoke access without individually regenerating links. Define policy permissions and time terms consistently with the service SAS encoding rules. This central control applies to the named container and service SAS type, not account SAS or user delegation SAS.

Incorrect Answers

A:

Account SAS tokens cannot be associated with stored access policies. Each ad hoc account token carries its own signed validity and permissions, so changing a blob container policy would not alter those tokens. Use eligible service SAS links that reference the named policy to obtain the desired shared control.

C:

A resource tag is metadata and is not evaluated as an authorization condition when Azure Storage validates a service SAS. Changing the tag cannot extend or revoke signed tokens. A named stored access policy is the supported mechanism for this type of centrally managed service SAS.

D:

A subscription-wide Blob Data Owner grant provides persistent extensive data privileges and does not create the requested common token expiry. The users need temporary links with linked policy constraints, not broad Azure RBAC assignments. Define a container stored access policy and sign service SAS tokens against it.

Question 242

An administrator updates the expiry of a container stored access policy used by several service SAS links. A client immediately receives a transient 403 after the update. What should be checked before declaring the policy broken?

  1. Delete the storage firewall because policy updates are network authorization failures.
  2. Allow for stored access policy propagation and confirm the updated identifier, permissions and validity fields.
  3. Switch the container from private to anonymous public access while policy propagates.
  4. Grant the client subscription Owner to bypass the transient policy failure.

Explanation

Correct Answer

B:

Microsoft documents that creating or updating a stored access policy can require up to about thirty seconds to become effective across the storage service. During the interval, associated service SAS requests may temporarily return 403. Check the matching signed identifier, effective expiry and permission configuration, wait for the documented propagation interval, then retry. This is different from changing an ad hoc token's signed fields, which requires generating a new signature.

Incorrect Answers

A:

A 403 after a stored access policy update may arise from transient policy availability or signed parameters, even when networking is unchanged. Removing firewall restrictions is a security risk and not a justified response to the documented propagation delay. Check SAS policy association and wait appropriately.

C:

Enabling anonymous access would bypass the intended temporary authenticated delegation model and potentially expose data to unauthorized users. It is not a safe mitigation for stored policy propagation. Keep the container private and verify linked service SAS requests after policy changes have settled.

D:

Subscription Owner is a broad ARM role and does not turn a policy-bound SAS into an unrestricted credential. The SAS service still evaluates its policy identifier and validity. Elevating the recipient would create unrelated administrative power while missing an expected propagation and token-configuration issue.

Question 243

An incident responder must invalidate all service SAS URLs associated with container stored access policy vendor2026 after a vendor credential leak. Other policies on the same container must remain usable. What should be done?

  1. Delete every container on the storage account so that all SAS links become invalid.
  2. Remove or expire the vendor2026 signed identifier while preserving the other stored policies and verifying propagation.
  3. Remove only the expiry parameter from the vendor's issued SAS URL.
  4. Grant the vendor Reader on the container to cancel the old SAS tokens.

Explanation

Correct Answer

B:

A policy-bound service SAS references a particular stored access policy signed identifier. Deleting that identifier, renaming it, or updating its expiry into the past can invalidate associated links while leaving other policies intact, provided the policy replacement operation preserves their identifiers. Review the affected customers, allow policy propagation and verify denial of the compromised URLs. Regenerating both storage account keys would unnecessarily disrupt unrelated signed links and applications.

Incorrect Answers

A:

Deleting unrelated containers would be destructive and far exceeds the scope of the compromised vendor policy. Azure Storage supports revocation of policy-bound service SAS by changing the specific stored access policy identifier or terms. Preserve other access policies and data while invalidating only the affected links.

C:

A service SAS URI is cryptographically signed. Editing its query string cannot revoke every previously distributed copy and often invalidates only the edited link. The server-side stored policy is the control that can affect all service SAS tokens associated with its identifier.

D:

Adding a new management-plane or data-plane role does not revoke an existing bearer SAS signed against a stored access policy. It also provides the compromised principal with more access. Change the referenced stored policy to invalidate the affected links, and verify resulting behavior.

Question 244

A developer creates an account SAS for access to Blob and File service-level operations. They ask which blob container stored access policy will centrally control its expiry. What is the correct response?

  1. Create a blob container stored access policy and pass its identifier into the account SAS.
  2. Enable storage versioning to make the account SAS inherit the latest container expiry.
  3. None; account SAS tokens are ad hoc and cannot reference a stored access policy.
  4. Assign the developer Storage Blob Data Reader, which retroactively binds the account SAS to the policy.

Explanation

Correct Answer

C:

An account SAS can authorize supported service-level operations across one or more Azure Storage services, but its start time, expiry and permissions are supplied as signed ad hoc token parameters. Stored access policies are supported for eligible service SAS tokens only; an account SAS cannot inherit a blob container's policy identifier. Keep account SAS validity short and plan for shared-key revocation, or use other supported authorization mechanisms if centrally revocable access is mandatory.

Incorrect Answers

A:

Account SAS does not support stored access policy linkage. Adding a policy identifier or creating a new policy will not provide shared expiry control over an account SAS. Only eligible service SAS tokens can reference those server-side policies, so choose an appropriate SAS type or redesign the delegation workflow.

B:

Blob versioning preserves historical object states and does not manage shared access signature validity. A container stored access policy cannot control account SAS tokens merely because versioning is enabled. Use the account SAS expiry fields directly or a different supported delegation design.

D:

A data reader role controls Microsoft Entra-authorized content reads and has no mechanism to rewrite or associate an existing signed account SAS with a stored policy. Account SAS tokens are signed using an account key and remain ad hoc. RBAC grants do not change their token format.

Question 245

Security revoked several account-key-signed Blob service SAS links by deleting their container stored access policy with signed identifier `vendor-old`. A week later, an engineer proposes recreating the same `vendor-old` identifier with a new future expiry to onboard a different supplier. Some original policy-linked SAS tokens remain otherwise unexpired. Which action prevents unintentionally reactivating those compromised links?

  1. Recreate `vendor-old` unchanged because deleting it permanently invalidates every earlier signature even if the same identifier reappears.
  2. Give the former vendor an Azure Reader role so the deleted policy remains permanently revoked when reused.
  3. Change only the storage account region; existing SAS signatures stop working when the account remains accessible in a new region.
  4. Use a NEW stored access policy identifier for the replacement supplier and issue newly signed service SAS URLs; do not recreate the deleted identifier while old URLs might remain valid.

Explanation

Correct Answer

D:

Use a distinct signed identifier for new suppliers and sign their new service SAS tokens against that fresh stored policy. Microsoft specifically cautions that reusing the exact deleted policy name can restore old SAS validity when the old URL is otherwise unexpired, so separating identifiers preserves intended revocation.

Incorrect Answers

A:

For policy-bound service SAS, revocation depends on resolving the stored access policy identifier. Microsoft documents that recreating a deleted identifier with the same name can make earlier SAS URLs valid again under the recreated policy, provided their own expiration has not passed. Deletion is not an irreversible cryptographic revocation.

B:

An Azure resource management Reader role does not control the bearer SAS signature or the stored access policy identifier. The old SAS links may become valid again if the deleted signed identifier is recreated, regardless of an unrelated identity role.

C:

A storage account region or replication setting does not rotate the storage signing key or change the signed identifier on already issued service SAS URLs. This suggestion does not address the policy-identifier resurrection hazard.

Question 246

An Azure Blob container has several groups of customers who need independent expiry and revocation for their service SAS links. A developer proposes ten different stored access policies on that one container. What must be considered?

  1. Only one service SAS can reference each stored access policy.
  2. Give every customer subscription Owner so the policy count no longer matters.
  3. Any number of policies can be added because every SAS token is created client-side.
  4. A container supports at most five stored access policies; design separate eligible policy groups within that limit.

Explanation

Correct Answer

D:

Azure Storage limits the number of stored access policies on a single blob container to five at a time. Each signed identifier can control service SAS tokens that reference it, so plan the customer groups and revocation domains within that limit. If more independently revocable groups are required, assess separate containers or a different authorization design. Attempting to configure ten policies on one container causes the service to reject the policy set rather than expanding capacity.

Incorrect Answers

A:

A named stored access policy can be shared by multiple eligible service SAS tokens so that they inherit common constraints. The policy limit counts stored identifiers, not tokens. One policy can support a customer group, but different independently revocable groups may need separate identifiers.

B:

Granting Owner would expose extensive management and access-assignment privileges and does not increase the stored access policy limit. It also abandons controlled temporary delegation. Use supported policy grouping or redesign the resource boundaries to maintain independent revocation safely. The same five-policy limit still applies at container scope.

C:

The ability to issue many signed SAS URLs does not remove the server-side limit on stored policy identifiers per container. Azure Storage enforces the number of policies configured through its access control list operation. Design within the five-policy constraint instead of assuming unlimited server policy entries.

Question 247

A service SAS refers to container policy readpolicy, and the signed URI omits explicit read permission because the policy supplies it. The policy is changed to list-only. What governs subsequent reads through the linked SAS?

  1. The SAS becomes a user delegation SAS and uses the caller's Entra permissions instead.
  2. The old read right remains forever because it was present when the SAS was originally issued.
  3. The effective stored access policy permissions; read requests cease to be authorized if read is removed.
  4. The storage account's redundancy determines whether the old read permission still applies.

Explanation

Correct Answer

C:

When a service SAS is associated with a stored access policy, eligible permissions can be defined in the policy rather than duplicated in the signed URI. Updating readpolicy to exclude read removes that operation from the policy-bound token's effective authorization after the change is active. Listing a container and downloading blob contents are distinct operations. Inspect the stored identifier and propagation behavior instead of inferring that the old read permission remains permanently baked into the URL.

Incorrect Answers

A:

Changing stored policy permissions does not change a service SAS signed with an account key into an Entra-backed user delegation SAS. Those are different token types and signing mechanisms. The service SAS continues to use its policy identifier and currently effective allowed operations.

B:

The benefit of a server-side stored access policy is that supported constraints can be modified for associated service SAS tokens. A policy change can remove read permission from subsequent requests. The historical state of the policy at issuance does not guarantee the previous rights remain effective.

D:

Storage replication does not control SAS authorization bits. The access decision is made using the token and any associated stored policy's effective permissions, not whether the account is LRS, ZRS or GRS. Review the stored access policy rather than changing redundancy.

Question 248

A team issued many ad hoc service SAS links last month. Today it creates a stored access policy named quarterly to gain shared revocation for those same links. What else is required?

  1. Nothing; every SAS URL issued in the past automatically attaches to the newest container policy.
  2. Reissue eligible service SAS links that explicitly reference quarterly; the prior ad hoc links do not retroactively inherit it.
  3. Change the blob container's access level to public to make the old tokens inherit the policy.
  4. Give callers more Reader RBAC assignments so the old URLs recognize quarterly.

Explanation

Correct Answer

B:

A stored access policy controls service SAS tokens through a signed identifier included when the token is generated. Existing ad hoc URLs carry their own signed permissions and time bounds and are not automatically linked to a newly created policy. Create appropriate replacement service SAS links referencing quarterly and retire the old URLs using the available revocation controls and expiry plan. Creating the policy alone does not change independently issued signatures.

Incorrect Answers

A:

Stored access policy association is explicit and depends on a matching signed identifier in the service SAS. Azure Storage does not retroactively rewrite issued ad hoc URLs. Reissue eligible tokens if central policy control is needed and plan for outstanding old links.

C:

Public access configuration affects anonymous read behavior and does not attach policy identifiers to existing signed tokens. Enabling it could expose data to unintended recipients. Keep the container private and reissue valid policy-bound service SAS links if shared revocation is required.

D:

Reader role assignments are unrelated to the signed identifier embedded in existing SAS URLs. Adding Azure RBAC roles cannot change those signed parameters or bind an ad hoc token to a server policy. Recreate the service SAS with the desired policy reference.

Question 249

Two Azure Blob containers, legal and marketing, need distinct customer revocation policies. A developer creates one signed identifier on legal and expects it to govern service SAS tokens for marketing. What is the correct design?

  1. Define the appropriate stored access policy on each relevant container and sign its service SAS tokens against that container's identifier.
  2. Enable blob versioning to replicate one container's stored policy to every other container.
  3. Replace both policies with a subscription-wide Reader role for all customers.
  4. Use the legal container's policy identifier against any container in the storage account.

Explanation

Correct Answer

A:

Blob stored access policies are associated with a specific container's access control list. A policy on legal does not become a universal account-wide policy for unrelated marketing blobs. Create separate policy entries where supported, issue links that reference the correct container and signed identifier, and maintain independent expiration or revocation plans. This respects the two containers' different business authorization boundaries without treating a storage account as one shared policy namespace.

Incorrect Answers

B:

Versioning preserves previous blob content and does not replicate access-policy identifiers between separate containers. A versioning setting cannot provide shared cross-container SAS revocation. Configure the policy on each intended container and issue matching tokens. Each signed identifier must exist on its own eligible target container.

C:

A broad Azure RBAC role is neither a stored access policy nor an appropriate way to delegate temporary partner data access. It would also increase scope and potentially require identities for each customer. Retain per-container service SAS policies with suitable constraints rather than distributing subscription permissions.

D:

Policy identifiers are resolved in the context of the eligible storage resource whose access is requested. The existence of an identically named or unrelated identifier on another container is not a universal grant. Configure policy entries on the actual target container when using policy-bound service SAS.

Question 250

An application backend sends the storage account master key to customer devices so they can download files, and now security requires central revocation of those customers' temporary links. What should the backend change?

  1. Enable anonymous public read on every container and delete the revocation process.
  2. Assign every client subscription Owner to make their downloads easier to audit.
  3. Keep giving clients the master key, since a stored policy can restrict a raw account key.
  4. Stop distributing account keys and issue scoped, policy-bound service SAS links or supported Entra-based delegation instead.

Explanation

Correct Answer

D:

Shared account keys grant powerful storage capabilities and are unsuitable for customer devices. Keep account-key material on protected infrastructure when service SAS signing is used, distribute only short-lived resource-scoped SAS URLs, and associate eligible service SAS with stored access policies when central revocation is needed. If supported, Entra user delegation SAS avoids account-key signing but has a different revocation mechanism. Rotate compromised shared keys through a planned process and verify clients can no longer use them.

Incorrect Answers

A:

Anonymous access removes the authenticated temporary link requirement and can expose private data to anyone with a URL. It cannot replace individual customer revocation. Keep containers private and use correctly scoped delegated tokens with a documented revocation design. It also contradicts the requirement to preserve private customer content.

B:

Subscription Owner is vastly broader than temporary file downloads and provides administrative authority rather than centrally revocable customer SAS links. It may increase the attack surface without improving key control. Issue least-privilege tokens and protect signing credentials instead. The storage owner must control the temporary authorization boundary.

C:

A stored access policy constrains eligible service SAS tokens that reference it, not the storage account's master key itself. A customer with an account key can bypass the intended link-level delegation pattern by signing other requests. Stop distributing shared keys and move to scoped delegated access.