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 26

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.

Question 251

A container stored access policy `legal-read` already specifies the read permission and expiration for a Blob service SAS. A developer generates a new account-key-signed service SAS that names the policy with `si=legal-read` but ALSO includes explicit `sp=r` and `se=` fields for the same permissions and expiry. The signing operation is being rejected under the service SAS parameter rules. Which correction uses the existing policy properly?

  1. Keep the repeated `sp` and `se` values and increase the HTTP request timeout; transport delay allows contradictory signed fields.
  2. Move the blob to a container without `legal-read` so the original policy identifier can still control the SAS from the new container.
  3. Configure the container for anonymous public read and omit the SAS signature; the named stored policy automatically restricts every anonymous request.
  4. Regenerate and sign the service SAS with its signed identifier `si=legal-read`, omitting `sp` and `se` because those constraints are already supplied by that stored access policy.

Explanation

Correct Answer

D:

Microsoft documents that `signedPermissions` (`sp`) and `signedExpiry` (`se`) must be omitted from a service SAS URI when they are already specified in its associated stored access policy. Sign a new, valid service SAS with `si=legal-read`, and let the server-side policy supply those constraints. This differs from waiting for policy propagation.

Incorrect Answers

A:

The service SAS specification requires permissions and expiry to be omitted from the SAS URI when the associated stored access policy already defines them. Increasing a transport timeout cannot correct invalid or redundantly supplied signed fields.

B:

A stored access policy belongs to the container resource where it is defined. Moving data to an unrelated container does not make the original signed identifier automatically apply to a different container and abandons the approved access boundary.

C:

Anonymous public read does not use a signed SAS token and would bypass the intended bounded delegation model. A stored access policy governs eligible service SAS links that explicitly reference it; it is not an anonymous-access policy.

Question 252

A service SAS for container contracts references stored policy identifier partner_old, which was deleted during cleanup. The client still has the original SAS URL. How should the missing-policy failure be resolved safely?

  1. Assign the user Azure subscription Reader because it recreates the missing policy.
  2. Turn off container soft delete to make the deleted policy return.
  3. Rename the storage account and assume the old SAS is automatically re-signed.
  4. Create and issue a new service SAS referencing an authorized active policy identifier and revoke the obsolete link.

Explanation

Correct Answer

D:

A policy-bound service SAS requires Azure Storage to resolve the signed policy identifier at request time. Deleting partner_old invalidates the association, so the old URL may fail despite an unexpired token time field. Create an appropriate current policy, issue fresh signatures referencing that identifier and distribute replacements securely. Recreating an old identifier can unexpectedly make still-valid old tokens work again, so use a controlled new identifier when revocation was intentional.

Incorrect Answers

A:

ARM Reader does not create or restore a container stored access policy and cannot change the SAS token's signed identifier. The service continues to reject an unknown policy reference. Issue an appropriate new policy-bound service SAS instead of granting unrelated management visibility.

B:

Container soft delete protects deleted containers under eligible conditions, not deleted stored access policy identifiers as separate data objects. Disabling a recovery feature would not restore the SAS association and could reduce protection. Reissue the link against a valid policy instead.

C:

Renaming or recreating a storage account is not a supported technique to repair a stored access policy identifier in an existing SAS. SAS signatures bind to resource and policy conditions; URL text cannot be silently regenerated by changing display metadata. Use a fresh authorized policy and token.

Question 253

A storage account key was accidentally committed to a public repository. Several production services still use the account's two keys. Which TWO actions are central to containment while minimizing downtime? Select TWO answers.

  1. Grant subscription Owner to every service identity to avoid changing connection strings.
  2. Apply a CanNotDelete lock and assume the exposed key cannot be used to read blobs.
  3. Inventory affected consumers and migrate them to the unaffected alternate key or identity-based authentication where feasible.
  4. Publish the secondary key alongside the primary so developers can diagnose authentication problems.
  5. Regenerate the compromised access key after relocating legitimate consumers and replace any dependent key-signed SAS tokens.

Explanation

Correct Answers

C:

A leaked account key is a powerful credential that can authorize storage data operations and sign SAS tokens. Before invalidating the compromised key, operators should identify applications using that key, their connection strings, and any tokens it signed. Migrating legitimate consumers to the alternate key or Microsoft Entra-based authorization reduces disruption during emergency key regeneration. The team must also evaluate logs for unauthorized activity and coordinate the change with the incident response owner.

E:

Regenerating the exposed storage access key invalidates requests authenticated with the old key and SAS signatures created from it. After legitimate applications have switched to a safe credential, rotate the compromised key promptly and issue replacement service or account SAS tokens as necessary. Confirm application connections and block remaining unauthorized use. The second key allows a staged process, but the organization should not leave a publicly exposed key active indefinitely merely to avoid change.

Incorrect Answers

A:

Owner is a broad Azure management and access-assignment privilege and does not automatically rewrite applications that still submit the leaked account key. It also worsens the incident's authorization exposure. Migrate consumer credentials or use appropriate data-plane identities, then regenerate the compromised key and reissue affected SAS tokens.

B:

An Azure management lock restricts selected control-plane modifications but does not remove storage Shared Key data authorization. A leaked account key may still be used for valid data requests despite such a lock. Containment requires rotating the compromised key and updating dependent clients, not merely protecting resource deletion.

D:

Disclosing the second storage account key compounds the incident and gives untrusted parties another high-privilege credential. Application owners should receive secrets through approved secure distribution, not a public repository. Use the alternate key privately during migration and rotate the compromised key once legitimate consumers have been accounted for.

Question 254

A legacy production application uses Azure Storage key1 in its connection string. The team needs to regenerate key1 without interrupting service. Which sequence is recommended?

  1. Switch the application to key2, verify connectivity, regenerate key1, and update the application to the newly generated key1 when appropriate.
  2. Give every application account subscription Owner and stop using both storage keys immediately.
  3. Delete the storage account, recreate it with the same name and restore the blobs.
  4. Regenerate key1 immediately while the application still uses it and expect no effect.

Explanation

Correct Answer

A:

Azure Storage provides two account access keys to support staged credential rotation. A safe sequence is to move applications from key1 to the still-valid key2, confirm they work, regenerate key1 and then update clients to the new key1 if returning to the primary credential. Any service or account SAS signed with the regenerated key must also be replaced. Never regenerate the key that live applications still require without a tested migration path and rollback preparation.

Incorrect Answers

B:

Azure subscription Owner does not automatically change how a legacy application authenticates through its Shared Key connection string. Granting management privilege could broaden access while requests still use the old credential. Change client authentication configuration to a valid key or an approved identity model before key regeneration.

C:

Recreating a storage account to rotate credentials is unnecessarily destructive and may disrupt endpoints, metadata, identities and application dependencies. Azure Storage has built-in key regeneration and two-key rollover capabilities. Use the secondary key and staged rotation instead of rebuilding a production account.

D:

Regeneration replaces the old signing credential, so applications still sending key1 will fail authentication until their configuration is updated. It may also invalidate SAS tokens derived from that key. Migrate the application to key2 and test first, then regenerate key1 as part of a controlled rotation.

Question 255

After regenerating an Azure Storage account access key, a backup utility that still uses the old connection string starts returning AuthenticationFailed. Network connectivity and Blob access controls have not changed. What should the operator do?

  1. Update the utility's secret or connection string to a currently valid key, and retest the affected request.
  2. Disable the storage firewall so the old connection string becomes valid again.
  3. Change the storage account's redundancy from LRS to GRS.
  4. Assign Reader at subscription scope while keeping the old key.

Explanation

Correct Answer

A:

Azure Storage key regeneration replaces the old Shared Key signing material, so a connection string holding the previous value no longer authenticates requests. The utility should retrieve the active replacement from the approved secret management system and securely update its configuration, then verify service authorization. If it uses a SAS signed with the old key, that token may need regeneration as well. The error should not be resolved by weakening storage firewalls or granting unrelated Azure resource roles.

Incorrect Answers

B:

A regenerated key is no longer accepted for Shared Key authentication, even when network admission succeeds. The scenario already indicates connectivity is healthy. Disabling firewall controls would unnecessarily expose the account's public endpoint without fixing signature validation. Replace the expired key material in the utility's secret configuration.

C:

Storage replication protects data from faults and does not determine whether a connection string's HMAC signing key is current. An outdated key remains invalid after a redundancy change. The correct recovery is to update the utility's stored credential and confirm the relevant authentication request succeeds.

D:

Azure Reader gives resource metadata visibility but does not cause an obsolete storage account key to pass Shared Key signature verification. The utility is still presenting the invalid old credential. Update the connection string or SAS with a valid signing key instead of adding unrelated management permissions.

Question 256

Security wants Blob applications to authenticate with Microsoft Entra rather than long-lived account keys. Before disabling Shared Key on a supported storage account, what plan should be executed?

  1. Disable Shared Key immediately and assume every key-signed service SAS will continue to work.
  2. Enable anonymous Blob access to avoid using storage access keys or Entra tokens.
  3. Migrate clients and SAS issuers to supported Entra authorization, then set allowSharedKeyAccess to false and verify behavior.
  4. Grant subscription Owner to every workload as an alternative to changing authentication.

Explanation

Correct Answer

C:

Disallowing Shared Key authorization makes eligible key-signed storage requests fail. Before switching the supported account setting off, inventory users of connection strings and account or service SAS tokens, move workloads to Microsoft Entra data roles and user delegation SAS where suitable, and validate service compatibility. Then set Allow storage account key access to Disabled and monitor for rejected requests. This sequence reduces key exposure without unexpectedly breaking legitimate clients that still depend on the old authentication model.

Incorrect Answers

A:

Service and account SAS tokens are signed with storage account keys and may be rejected when Shared Key authorization is disallowed for supported workloads. Turning off the setting without inventory can break active applications. Migrate and test eligible Entra-based access first, then enforce the restriction with a controlled rollout.

B:

Anonymous access removes authentication requirements for eligible public content, defeating the private-blob security objective. It is not a substitute for managed identities or least-privilege data roles. Migrate to supported Microsoft Entra authorization and block Shared Key only after validating required applications.

D:

Owner is a broad Azure management and role-grant permission, not a safe replacement for application data-plane authentication. Workloads should receive appropriate storage data roles via managed identities or authorized principals. Broad resource ownership would introduce unnecessary privileges while leaving existing Shared Key connection strings unchanged.

Question 257

An administrator is planning Azure Storage key rotation for an account used by VMs, automation jobs and older third-party tools. The team has not identified which clients use key1 versus key2. What should happen first?

  1. Turn on anonymous access for every container before rotating the keys.
  2. Inventory the application's key references, connection strings and key-signed SAS dependencies before regenerating a live key.
  3. Regenerate both keys simultaneously and investigate any failures afterward.
  4. Assign Reader to all users so no application needs storage credentials.

Explanation

Correct Answer

B:

Storage access keys are shared secrets that may be embedded in many clients and can also sign service or account SAS tokens. Regenerating a key without identifying dependencies risks widespread authentication failures. Audit application configurations and access patterns, find which key each client uses, prepare a migration to the alternate key or identity-based authorization, and test the change plan. Key rotation should then proceed in a controlled sequence so active services are not unexpectedly left with invalid signatures.

Incorrect Answers

A:

Making data publicly accessible would avoid some authenticated read paths by sacrificing confidentiality, which is not an acceptable rotation strategy. Other write or administrative operations would remain affected by credential changes. Preserve private access and inventory key consumers so the rotation can be performed without disabling authentication.

C:

Regenerating both Azure Storage keys without a consumer inventory would invalidate every application still relying on either old key and affected SAS signatures. This could create an avoidable outage. Identify and migrate clients first, then rotate keys separately while verifying service operation between steps.

D:

ARM Reader lets users view resource configuration but does not automatically authorize an application's Shared Key data requests. It also does not update credentials embedded in jobs or third-party tools. Plan key-dependent client migrations and use appropriate storage data roles where supported, rather than distributing a general Reader grant.

Question 258

A user has Storage Account Contributor and can list account access keys, but the user lacks Storage Blob Data Reader in Azure RBAC. Which statement best explains the security consequence?

  1. Storage Account Contributor is identical to Storage Blob Data Reader and grants only read-only blob DataActions.
  2. The management listKeys permission can expose Shared Key credentials that authorize data access even without Entra blob DataActions.
  3. Adding a resource-group CanNotDelete lock prevents anyone with keys from reading blobs.
  4. ListKeys is a private DNS configuration operation with no security impact.

Explanation

Correct Answer

B:

Azure Storage differentiates Entra-authorized data-plane roles from management-plane permissions such as Microsoft.Storage/storageAccounts/listkeys/action. A principal able to retrieve account keys may use those keys for Shared Key data access when the account allows that method, even without Storage Blob Data Reader. This is why account management and key listing should be treated as sensitive privileges, not inherently data-blind operations. Organizations seeking strong separation should limit key retrieval and consider disabling Shared Key after migrating compatible clients.

Incorrect Answers

A:

These roles address different permission families. Storage Account Contributor manages storage resources and includes key-related management actions, while Storage Blob Data Reader grants specific Entra-authorized blob data read operations. Treating the roles as identical would conceal the ability to retrieve powerful account signing keys.

C:

A management-plane deletion lock does not invalidate storage account keys or prevent permitted data-plane reads. A user holding a valid key may still access data if Shared Key is allowed and the network path is permitted. Mitigate the risk through key permission controls and identity-based access strategy.

D:

Listing storage account keys exposes secrets capable of authenticating data requests where Shared Key remains enabled. It is not a DNS operation and can bypass the intended separation between data-plane OAuth roles and key-based access. Restrict key retrieval and use role definitions appropriate to the administrator's duties.

Question 259

An Azure VM's application must read a private Blob container without any storage access key or SAS in its configuration files. The VM already has a system-assigned managed identity. What should the administrator do?

  1. Enable anonymous read access so the application can bypass authentication.
  2. Grant Azure subscription Owner to the VM's managed identity.
  3. Store the primary storage account key in the VM's startup script.
  4. Grant the VM's managed identity Storage Blob Data Reader at the container scope and use Entra token-based Blob SDK authentication.

Explanation

Correct Answer

D:

A system-assigned managed identity allows the VM-hosted workload to request Microsoft Entra tokens without storing a long-lived application password or account key. Assign the identity a storage data-plane Reader role at the narrow container scope, then configure the Azure Blob client to authenticate with the managed identity credential chain. The storage firewall and DNS path must also permit the VM's network source. This gives the application read-only access to the required blobs with no embedded storage key.

Incorrect Answers

A:

Anonymous access would potentially expose the private dataset to unauthenticated clients and violates the requirement that the application access a protected container. The VM can authenticate with its managed identity, so there is no reason to make the data public. Preserve private authorization and assign the precise data role.

B:

Owner provides extensive Azure resource management and role-assignment powers but is not the least-privilege data-plane role for reading one Blob container. The workload would receive unnecessary control-plane authority and still need an appropriate authentication pattern. Grant container-scoped blob read DataActions to its managed identity instead.

C:

Embedding a storage account key in a script exposes a powerful shared secret and contradicts the explicit requirement to avoid keys or SAS in configuration. The VM already supports a managed identity, which can request Entra tokens securely. Use that identity and a scoped Blob Data Reader grant instead.

Question 260

An automation service rotates an Azure Storage account key. Security requires the new key never appear in pipeline console logs or plain text configuration. Which operational design is suitable?

  1. Store and retrieve updated key material through Azure Key Vault or an approved secret store, using restricted identities and nonlogging deployment variables.
  2. Print the entire key once for debugging, then delete the build log later.
  3. Store the key as a resource-group tag so it is searchable by the operations team.
  4. Put the new key in an ARM template output that every deployment engineer can read.

Explanation

Correct Answer

A:

Azure Key Vault and comparable managed secret systems can hold sensitive storage credentials with access controlled by identity and auditable permissions. During rotation, automation should update protected secret versions and configure consumers to retrieve them securely, without printing the value to build logs or committing it to source control. Restrict who can list or regenerate storage account keys and test clients after the update. Where workloads support managed identities, removing the Shared Key dependency entirely can further reduce exposure.

Incorrect Answers

B:

Pipeline output can be retained, forwarded or copied before anyone deletes a log. Printing a newly generated storage account key violates the secrecy requirement and creates an avoidable exposure. Keep credential values in secure secret stores and use redacted status or authentication success indicators for troubleshooting.

C:

Azure resource tags are metadata, not a secure vault for secrets. Users who can inspect resource metadata could read the credential, and tags may be copied into inventory and billing systems. Store storage account keys in a protected secret store and avoid plaintext handling during deployment.

D:

Publishing sensitive key material as a broadly visible deployment output can expose it to logs, history and users without a legitimate need. The requirement is protected handling and distribution, not convenient display. Use an approved secret reference and narrowly scoped access instead of emitting the credential itself.