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 24

Question 230

A partner must list documents in one Blob container and download selected blobs for the next two days. The partner cannot edit or delete data. What delegation should be issued?

  1. Storage Blob Data Contributor over the entire subscription for one year.
  2. A SAS allowing only write permission because downloading counts as a storage write.
  3. A shared account key that the partner can use to browse every container.
  4. A container-scoped SAS granting read and list for only the approved validity period.

Explanation

Correct Answer

D:

To enumerate blobs in a container, the delegated operation needs list permission, while downloading blob contents requires read permission. A SAS can constrain both operations to the selected container and expire after the authorized period. Avoid write, delete and account-wide resource types because the partner should not modify data or inspect unrelated datasets. If the storage firewall restricts external clients, provide an approved network path as a separate prerequisite.

Incorrect Answers

A:

A broad contributor role permits writes and deletes and may extend to other accounts in the subscription. It is inconsistent with temporary read-only partner access. Use SAS read/list permissions at the specific container scope for the intended two-day period. The authorized task is confined to a single container.

B:

Downloading a blob is a read operation, and listing container members requires list permission. A token with write only would fail those requested operations while granting an unneeded mutation capability. Generate a container-scoped read/list SAS rather than trying to compensate with broader access.

C:

Account keys confer broad authority over supported storage services and are inappropriate for limited partner access to one container. The partner's activities and lifetime can be enforced by a scoped SAS, avoiding long-lived credentials that are difficult to contain if leaked.

Question 231

Security prohibits storage account keys in an application that issues temporary Blob download links. The application has Microsoft Entra credentials and approved data access. Which SAS should it prefer?

  1. A service SAS signed with the secondary account key.
  2. A user delegation SAS signed with a Microsoft Entra-acquired delegation key.
  3. An account SAS signed with the storage account's primary shared key.
  4. A new anonymous access policy that makes the Blob container public.

Explanation

Correct Answer

B:

A user delegation SAS is signed using a user delegation key obtained through Microsoft Entra authorization rather than the storage account's shared key. The issuer must hold the proper permission to request the delegation key at an eligible scope and suitable data access for the delegated operations. This honors the instruction to avoid account-key signing. Apply narrowly scoped read permission, HTTPS and expiration in the resulting SAS and protect the signed URL as a bearer capability.

Incorrect Answers

A:

Using the secondary key does not change the signing model: service SAS tokens are signed with account-key material. The application would still need a powerful shared secret. The preferred option for an Entra-capable Blob issuer is a user delegation SAS with the necessary delegation-key action.

C:

An account SAS uses the storage account key for its signature, directly conflicting with the prohibition on shared-key material in the issuing application. It can also cover broader service-level operations. Use the Entra-backed user delegation SAS mechanism where the target service and operation support it.

D:

Anonymous access removes the authenticated delegation requirement instead of satisfying it. The business needs controlled temporary links, not indiscriminate publication. Use an Entra-backed signed SAS scoped to the requested objects and expiration window rather than enabling unauthenticated container reads. The customer must receive an individually authorized link instead.

Question 232

A customer presents an otherwise valid Azure Storage SAS URL that expired an hour ago. The storage firewall and endpoint connectivity are correct. Which remediation directly addresses the failure?

  1. Change the blob's access tier from Cool to Hot to extend the SAS lifespan.
  2. Have an authorized issuer create a replacement SAS with a valid allowed time window and required permissions.
  3. Grant Reader on the storage account to every customer to revive their old SAS URLs.
  4. Add the client's public IP to every storage firewall rule to override expiry.

Explanation

Correct Answer

B:

Azure Storage evaluates the SAS validity period when it authorizes a request. After the signed expiry time, the service denies operations regardless of whether the URL was once valid. Issue a new SAS for the needed resource and permissions, with carefully selected start and expiry times and suitable clock-skew margin where relevant. There is no reason to widen the storage firewall or alter an unrelated RBAC role when the documented expiration is the cause.

Incorrect Answers

A:

Access tier is a data storage and cost setting, unrelated to the signed validity interval carried by a SAS token. Moving the blob to Hot will not make a previously expired signature valid. Reissue the SAS with a permitted expiry and original least-privilege scope.

C:

ARM Reader provides resource metadata visibility to authenticated principals and does not extend the signed expiry of a bearer SAS URL. It also would create unrelated access grants. The expired SAS must be replaced or renewed through an authorized issuing workflow.

D:

Firewall IP rules govern network source authorization and do not revalidate an expired SAS signature. A wider network allowance could increase exposure while leaving the token invalid. The caller needs a newly issued token with the right validity times, not a blanket network exception.

Question 233

A vendor was issued a read-only download link, but inspection reveals the SAS also includes blob delete permission. The link has not yet been used. What is the best correction?

  1. Revoke or replace the exposed token as appropriate and issue a new SAS permitting read only.
  2. Give the vendor Storage Blob Data Owner so the SAS can be ignored.
  3. Disable all logging for the container so the vendor does not see permission errors.
  4. Leave delete enabled because a read-only web client cannot invoke delete requests.

Explanation

Correct Answer

A:

SAS permissions are encoded in the signed token, so adding an unnecessary delete permission increases the operations a recipient can perform during the token's validity. Do not rely on the vendor's promise to avoid deletion. Stop distributing the overprivileged token, use the supported revocation mechanism for its SAS type if needed, and issue a short-lived read-only replacement for the correct resource. The final signed permissions should match the intended download activity.

Incorrect Answers

B:

Blob Data Owner provides extensive data permissions and would make the least-privilege problem worse. The requirement is only a temporary read-only download capability. Replace the excessive SAS rather than assigning a more powerful persistent Azure role. Revoke excess rights promptly, before wider distribution to clients.

C:

Logging does not determine what operations a SAS can authorize. Turning it off would remove visibility into attempted misuse without narrowing the vendor's signed permissions. Revoke or supersede the overprivileged token and issue an accurate read-only link instead. Keep auditing enabled so attempts to misuse the token remain observable.

D:

The SAS itself authorizes operations independently of how the vendor's normal browser interface behaves. Anyone possessing the URL could use a different client to call allowed methods, including deletion. Remove the unnecessary signed permission rather than relying on user interface limitations.

Question 234

A SAS URL for blob invoices/2026-09.csv is copied into an application request for a different blob named invoices/2026-10.csv. The token has not expired. Why may the second request fail?

  1. Set the destination blob access tier to Hot because SAS supports only Hot blobs.
  2. A SAS can read any blob in the subscription so the error must be a VM DNS issue.
  3. A resource-scoped SAS authorizes the signed resource, so the target URI must match the delegated scope.
  4. A SAS signature is ignored once its initial blob has been read successfully.

Explanation

Correct Answer

C:

The signed SAS includes resource scope information and permissions. When it was issued for one blob, reusing it against a different blob is not equivalent to receiving authorization for that second object. Check the resource URI and signed resource type, then generate a new SAS for the intended blob or container scope with the required permissions and lifetime. The valid expiry of the original token does not broaden its resource reach.

Incorrect Answers

A:

SAS authorization and a blob's online access tier are different mechanisms. A properly signed SAS can authorize supported operations on eligible blobs regardless of a simple Hot-versus-Cool distinction. The likely cause in this scenario is use of a token for a different signed resource.

B:

A blob-scoped SAS does not automatically authorize unrelated resources elsewhere in the subscription. Validity involves the signed resource and permissions as well as time. The wrong target URI can explain the denial even if networking works, so verify the SAS scope before changing DNS.

D:

Storage continues checking the token's signed parameters for later operations; successfully reading one authorized object does not transform the token into an unrestricted credential. The second request remains subject to its resource scope. Issue the proper token rather than expecting signature validation to turn off.

Question 235

Security anticipates that a temporary SAS URL could leak. The client is expected to use only HTTPS from a known public egress address. Which SAS restrictions reduce misuse where the chosen SAS type supports them?

  1. Set HTTPS-only signed protocol, an eligible signed-IP restriction, narrow operations and short expiration.
  2. Remove HTTPS restrictions so the client can choose either HTTP or HTTPS.
  3. Give subscription Reader and assume that Azure RBAC filters the SAS URL by caller identity.
  4. Set unlimited expiry because IP restrictions make the SAS impossible to steal.

Explanation

Correct Answer

A:

Supported SAS formats allow protocol and sometimes IP-range conditions in addition to a limited resource, permissions and validity time. HTTPS-only signing avoids accidental use over unencrypted HTTP, while a correct public egress IP range can reduce where a stolen token is useful. Validate service-specific signed-IP semantics, particularly for same-region Azure clients, before deployment. These controls mitigate exposure but do not eliminate bearer-token risk, so distribute the SAS securely and retain network rules.

Incorrect Answers

B:

Allowing HTTP undermines the stated compliance requirement and can expose the signed bearer token in transit. A SAS URL is itself sensitive because possession may grant data operations. Specify HTTPS-only where supported instead of making transport encryption optional. This is especially important for SAS URLs that can be forwarded.

C:

An ordinary SAS is often a bearer capability that can be used by a holder who presents the signed token, subject to its constraints. A separate ARM Reader role does not impose a caller-specific IP restriction on the SAS. Express the supported protocol and IP limits within the token and storage networking configuration.

D:

An IP condition can limit some request origins but cannot guarantee a token never leaks or is never usable from an allowed network. Long validity would extend the impact of compromise and violate least-privilege lifetime principles. Use a short expiration and HTTPS in addition to an eligible IP restriction.

Question 236

A systems integrator must perform an Azure Blob service-level operation such as retrieving certain service properties. It currently uses a blob-scoped service SAS designed only for object reads. Which delegated token type should it evaluate?

  1. An Azure VM User Login assignment to the integrator's service principal.
  2. A carefully scoped account SAS with the necessary service-level resource type and operation permissions.
  3. An Azure Backup policy for the storage account.
  4. A blob-scoped SAS with read permission reused against the storage service properties endpoint.

Explanation

Correct Answer

B:

An account SAS can delegate certain Azure Storage service-level operations not available through a service SAS signed for one blob. Configure only the eligible storage service, resource type and permission bits needed for the actual operation, with HTTPS and limited lifetime. Because an account SAS is signed using account-key material, protect the signer and consider whether Entra authorization could serve the operational need. Do not extend a blob-only token beyond its supported scope by assumption.

Incorrect Answers

A:

VM User Login relates to supported sign-in inside Azure virtual machines and is unrelated to storage service property requests. Assigning it does not change a SAS's signed service and resource type. Evaluate the correct storage authorization mechanism for the service-level operation.

C:

Backup settings govern recovery points and data protection, not what a SAS token can authorize at service level. Attaching a backup policy would not transform a blob read token into a service-properties operation token. Choose the supported account SAS scope and permissions where appropriate.

D:

Reading a particular blob is not equivalent to authorizing an operation on service-level settings. The signed resource type and supported operation set matter; adding more time to a blob SAS does not create account-level service authority. Use an eligible account SAS or a different authorized management mechanism.

Question 237

A service generates new blob-scoped SAS download links with signed start (st) set to the issuer's current UTC time and an approved short expiry. Customers using the links immediately sometimes get a 403 saying the SAS is not yet valid; the signature, scope, read permission, network path and expiry have been checked. Servers have small clock differences. What should the issuer change for immediate-access links?

  1. Set signed start 15 minutes in the future to prevent customers from requesting the link too early.
  2. Increase Storage Blob Data Owner permissions for customers because SAS signed start requires an Azure role.
  3. Reissue the SAS without its optional signed start, or set that start sufficiently in the past to tolerate clock skew, while retaining its short expiry and least-privilege permissions.
  4. Create a resource-group tag containing the issuer's UTC time because storage authorization uses tags to override the SAS start timestamp.

Explanation

Correct Answer

C:

The Azure Storage SAS guidance warns that setting the signed start to current time can cause intermittent failures because system clocks differ. Omitting the optional start makes an otherwise valid SAS usable immediately, or choosing a start at least about 15 minutes in the past allows for skew. The issuer must regenerate and sign the token with the corrected time values while preserving approved permissions and short expiration.

Incorrect Answers

A:

Moving the signed start into the future makes immediate authorization fail for more clients, not fewer. The scenario already identifies short-lived signed tokens whose start is too close to current time. For immediate access, Microsoft recommends leaving the optional SAS start unset or setting it in the past to absorb differences between issuer and storage clocks.

B:

A SAS is evaluated as a signed delegation, including its time window, rather than by assigning the recipient broad Microsoft Entra Blob ownership. The intermittent 403 occurs before the signed-start time as observed by the service; a stronger Azure RBAC role neither changes the token's signed start nor addresses clock skew.

D:

Resource-group tags are descriptive Azure Resource Manager metadata and do not override SAS cryptographic validation or the signed-start (st) query field. Editing a tag cannot make an already signed token valid before its start. The authorized signer must issue a token with appropriate signed time bounds.

Question 238

A service issued a user delegation SAS for a sensitive blob and later suspects the delegation key was compromised. A developer suggests deleting the blob container's stored access policy to revoke this SAS. What should be done instead?

  1. Assign subscription Owner to the downloader to cancel the original token.
  2. Change the token's expiry field in the URL query string without generating a new signature.
  3. Delete the container's stored access policy because all SAS token types inherit its settings.
  4. Use the supported user delegation key revocation mechanism and plan for the effects on tokens signed by that key.

Explanation

Correct Answer

D:

User delegation SAS tokens are signed with Microsoft Entra-authorized delegation keys and cannot reference a container stored access policy. Deleting such a policy would not be the supported revocation lever for the issued token. Use the storage service's delegation-key revocation operation as documented, understanding that other SAS tokens signed by the affected delegation key may also stop working. Follow with credential and issuer investigation and replacement of legitimate temporary links.

Incorrect Answers

A:

Owner is an administrative RBAC role and granting it does not cancel a bearer SAS token signed with a delegation key. It would dramatically expand privileges instead of fixing a suspected token compromise. Revoke the relevant delegation key under an authorized process.

B:

The signed fields are covered by cryptographic validation. Manually editing expiry text invalidates the signature and is not a controlled revocation or renewal procedure for existing recipients. Use supported key revocation to invalidate compromised delegation SAS tokens and issue fresh signed links for legitimate clients.

C:

Stored access policies are supported only for eligible service SAS tokens, not user delegation SAS or account SAS. Removing an unrelated policy does not directly revoke a user-delegation-key signature. Use the correct key revocation flow for this token type. A delegation key has an independent validity and revocation lifecycle.

Question 239

A vendor has a valid account-key-signed Blob service SAS URL with sp=r for reading a report. The vendor now needs to overwrite that report and proposes changing sp=r to sp=rw in the existing URL while keeping the original sig value. The storage account still accepts Shared Key authorization, and neither the network nor the expiry is blocking the request. What will happen?

  1. Changing the signed permissions without recomputing the signature invalidates authorization; an authorized issuer must issue a new correctly signed SAS granting any approved write operations.
  2. Azure Storage accepts the vendor's added write permission because a valid sig covers only the SAS expiration, never sp.
  3. The edited URL automatically becomes a user delegation SAS and inherits Blob Data Contributor from any user who opens it.
  4. Changing the blob access tier to Hot makes the unchanged read-only signature valid for arbitrary write permission changes.

Explanation

Correct Answer

A:

Azure Storage verifies SAS query fields, including the signed permissions, against the cryptographic signature. Increasing sp from read to read/write while reusing the original signature causes a mismatch and fails authentication; the bearer cannot promote its own delegation. Only an authorized SAS issuer can deliberately grant additional write operations and compute a new signature, subject to the account's other controls.

Incorrect Answers

B:

Signed permissions (sp) are among the fields bound to a service SAS signature. The server does not accept a changed sp just because another unchanged field, such as expiry, was once valid. A vendor cannot expand its access by editing the signed query string. It needs a newly signed token for separately authorized write operations.

C:

A service SAS continues to be a service SAS when the recipient edits a query parameter. User delegation SAS requires a Microsoft Entra-authorized delegation key and different signing material; no token type or Azure role magically changes because the vendor modifies sp. A signature mismatch still prevents use of the altered token.

D:

Hot, Cool and other Blob access tiers affect data placement, access charges and retrieval behavior, not integrity checks on signed authorization fields. Making the blob Hot does not cause Azure Storage to disregard the SAS signature. Keep the original read-only token immutable and ask an authorized issuer for a new signed write delegation if approved.

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.