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 40

Question 390

A finance report compares subscriptions with prepaid reservations and wants expenses allocated over the benefit term rather than charged only on the day of purchase. Which Cost Management view should be considered?

  1. Use actual cost exclusively because it always spreads every prepaid charge evenly.
  2. Use an amortized cost view when appropriate so reservation and savings-plan benefits are allocated over time.
  3. Switch the subscription Cost Management view from amortized to actual cost to spread reservation expenses over time.
  4. Filter the report to reservation purchases only and ignore amortized benefit usage and allocation.

Explanation

Correct Answer

B:

Amortized cost reporting can distribute prepaid benefit costs across usage periods for analysis. The desired accounting method should be explicit.

Incorrect Answers

A:

Actual cost and amortized cost answer different questions about prepaid benefits.

C:

Actual cost reports can show prepaid purchases at purchase time, rather than amortizing benefit cost across consumption periods.

D:

Purchase-only filtering does not distribute prepaid benefit costs over the term as requested.

Question 391

A service principal uses Entra authentication to create a user delegation SAS but receives an authorization error requesting a user delegation key. Which permission should be checked?

  1. Allow the application public IP through the storage firewall and the missing generateUserDelegationKey action is granted.
  2. Give the principal Storage Blob Data Reader only at one individual blob scope and delegation-key generation is automatically permitted.
  3. Assign Storage Blob Data Contributor at a single container while omitting the supported storage-account-level permission to obtain a user delegation key.
  4. Verify the principal has the supported generateUserDelegationKey action at an eligible storage scope in addition to needed blob data permissions.

Explanation

Correct Answer

D:

Issuing a user delegation SAS requires authorization to obtain a delegation key. This is distinct from merely reading or writing a blob.

Incorrect Answers

A:

Firewall network reachability is separate from Azure RBAC permission to obtain a delegation key.

B:

The delegation-key operation must be allowed at an eligible account or higher scope; narrow data-reading access alone is insufficient.

C:

Container-scoped Blob data access alone may allow data operations but does not satisfy the required user-delegation-key action at a suitable storage account or ancestor scope. Verify both permissions.

Question 392

A client has a SAS allowing read of one known blob, but an application tries to enumerate every blob in its container and receives a permission error. What delegation difference matters?

  1. Container listing requires an appropriate SAS list permission and scope, distinct from reading one specified blob.
  2. Change the SAS resource scope from one blob to its container but keep permissions read-only with no list action.
  3. Extend the SAS expiry period so listing becomes allowed even though the token still lacks list permission.
  4. Assign Azure Storage Reader management access and it adds missing list permissions to the existing SAS signature.

Explanation

Correct Answer

A:

SAS permissions identify individual operations. Read access to a known object does not imply container enumeration.

Incorrect Answers

B:

Container-level scope without the required list permission still cannot authorize container enumeration.

C:

Expiry controls the validity window, not which data operations the token allows.

D:

SAS permissions are encoded in the token; a separate ARM metadata role does not retroactively change them.

Question 393

A storage account allows selected public IPv4 sources and disables access from other networks. A reviewer assumes selected-network mode automatically forces all allowed clients through Private Link. What should be clarified?

  1. Grant each client Storage Blob Data Reader, and data RBAC changes network routing to a private IP endpoint.
  2. Enable selected public networks and Azure creates an approved private endpoint NIC automatically.
  3. Selected-network firewall rules can still allow approved clients through the storage service's public endpoint; Private Link is a separate mechanism.
  4. Change the client role to Storage Blob Data Contributor and its DNS will now resolve to private endpoint addresses.

Explanation

Correct Answer

C:

Storage firewall filtering and Private Link choose different network designs. Allowing a public source IP does not instantiate private endpoint infrastructure.

Incorrect Answers

A:

Storage data roles govern authorization, not network endpoint selection. Allowed public clients can still use the public service endpoint.

B:

Firewall IP allowlisting does not deploy Private Link infrastructure.

D:

Storage data RBAC cannot change DNS or endpoint addressing; a private endpoint must be separately configured.

Question 394

A legacy application must temporarily use a storage account key. Security policy requires central secret rotation without placing the key in source control. What configuration helps?

  1. Store the key in a suitable secret-management service such as Azure Key Vault and retrieve it through authorized app identity.
  2. Put the storage account key in an App Service application setting as plaintext and commit that setting to the infrastructure repository.
  3. Place the storage key in an Azure resource tag so all authorized metadata readers can retrieve it.
  4. Embed the key in an ARM template output for convenient inspection after every deployment.

Explanation

Correct Answer

A:

A secret store enables controlled key access and rotation workflows. The team should migrate to Entra authentication when supported.

Incorrect Answers

B:

Application configuration stored as a tracked literal still risks source exposure and lacks centralized controlled secret retrieval.

C:

Resource tags are not an appropriate secret store and expose credentials through management APIs.

D:

Ordinary deployment outputs are not a safe central rotation or secret distribution mechanism and can expose credentials.

Question 395

A helpdesk team wants to give one contractor access to a single folder on an Azure Files share by sending the storage account access key. What risk should the admin explain?

  1. Use a storage account key alongside a single-folder NTFS ACL and the key itself enforces that folder boundary.
  2. Storage account keys confer broad storage-level authorization and are unsuitable for a single-folder least-privilege user grant.
  3. Sign an account-level Shared Key SMB request and its authority will be limited to a contractor-specific Entra group.
  4. Give the contractor a key from key1 rather than key2 to create a folder-specific permission boundary.

Explanation

Correct Answer

B:

Shared Key authorization is not naturally scoped per human file directory. Supported identity-based SMB access with share roles and ACLs better fits least privilege.

Incorrect Answers

A:

Account keys are not per-user credentials constrained by a selected NTFS folder ACL.

C:

Storage account key authentication is not a per-contractor identity assignment and can bypass intended least-privilege share scoping.

D:

The two storage account keys are broad account credentials, not distinct folder-level access tokens.

Question 396

A newly created StorageV2 account has encryption at rest enabled. An administrator assumes blob soft delete also has a guaranteed thirty-day retention without checking settings. What should be verified?

  1. Inspect the account's Blob soft delete configuration and actual retention period because encryption at rest and deletion recovery are distinct controls.
  2. Set account replication to LRS and it establishes a fixed thirty-day soft-delete retention period.
  3. Encryption automatically creates thirty-day recoverable copies for all deletes in every account.
  4. Enable thirty-day container soft delete while leaving the distinct individual blob soft-delete retention configuration unverified.

Explanation

Correct Answer

A:

Service-side encryption protects stored bytes but does not define recovery retention. Blob data protection settings must be explicitly verified.

Incorrect Answers

B:

Redundancy controls copies of current data and does not itself set blob deletion recovery retention.

C:

Encryption does not imply a specific soft-delete period.

D:

Container soft delete protects eligible whole-container deletion; it does not establish the specified thirty-day retention for deleted individual blobs. Confirm the blob-level setting separately.

Question 397

A storage account has object replication enabled between two accounts, but blobs from a newly created source container do not appear in a destination container. The policy currently maps only existing container pairs. What should be changed?

  1. Enable blob versioning in the new source container but leave its source/destination policy pair unmapped.
  2. Add a supported replication policy mapping for the intended source and destination container pair, with prerequisites confirmed.
  3. Raise the destination account replication level and every new source container is automatically included.
  4. Enable change feed and blob versioning on both accounts but omit the new container pair from the active object-replication policy mapping.

Explanation

Correct Answer

B:

Object replication uses policy rules linking eligible container pairs. New containers need an applicable rule to participate.

Incorrect Answers

A:

Versioning is a prerequisite for object replication, but it does not add the missing container pair rule.

C:

Underlying account redundancy does not decide which source and destination containers an object replication policy maps.

D:

Versioning and change feed support object replication prerequisites, but the policy must still match each intended source and destination container pair. A new unmapped container is not automatically replicated.

Question 398

A team wants to create an account with ZRS, but deployment fails because the chosen region or account type does not support that combination. What should the operator do?

  1. Verify regional and account-kind redundancy availability, then choose a supported placement or alternative durability design.
  2. Increase the account quota in the same region and retry the ZRS combination even if the account kind does not support it.
  3. Change the storage account access tier and this always resolves a region-level ZRS unavailability error.
  4. Choose the same unsupported ZRS SKU in a new resource group within the same Azure region without changing account kind.

Explanation

Correct Answer

A:

Azure Storage redundancy choices are subject to region and account support. A valid combination is required before deployment.

Incorrect Answers

B:

Quota increases cannot enable redundancy configurations not supported for the region and account type.

C:

Blob access tiers manage cost and access patterns; they do not make unsupported regional redundancy available.

D:

Moving a request to a different resource group does not change the region-and-account-type feature availability that caused the unsupported SKU error.

Question 399

An operator wants to distribute a storage account access key to a vendor but limit it to one Blob container. Which security limitation matters?

  1. Account access keys authorize broad account operations and should be replaced with scoped SAS or Entra-based data access for the vendor.
  2. Regenerate storage account key2, designate key2 for the vendor, and use that key as though its permissions were scoped to the vendor container.
  3. Give the vendor identity a container-scoped Azure RBAC data role and distribute the account key for the same container as a secondary credential.
  4. Set the vendor Blob container to the Cool tier and use that per-container configuration to restrict account-key calls to this container.

Explanation

Correct Answer

A:

Shared Key is a high-privilege account credential, not a naturally scoped user delegation. Narrower access mechanisms are required for one container.

Incorrect Answers

B:

Both storage account access keys remain high-privilege account credentials. Key rotation does not change the scope of Shared Key authorization to one Blob container.

C:

Scoped RBAC constrains Entra-authenticated identity operations, not the separate Shared Key credential. A disclosed account key can still authorize broad account operations.

D:

Access tiers govern cost and data accessibility rather than Shared Key permissions. The account access key is not naturally scoped by container tier.

Question 400

A bulk AzCopy command can read the source container but returns authorization failures only when writing the destination account. What should be checked first?

  1. Change the destination access tier from Cool to Hot without inspecting its write permissions.
  2. Grant additional source-container read access while leaving the destination identity or SAS unchanged.
  3. Verify the destination identity or SAS has the required create/write permissions for the target container.
  4. Re-run AzCopy with a larger concurrency value without changing the destination authorization.

Explanation

Correct Answer

C:

Cross-account copy requires appropriate permissions on both ends. A source read grant does not automatically authorize writes at the destination.

Incorrect Answers

A:

Blob tier changes do not grant missing destination data create or write permissions.

B:

The observed failure occurs during destination writes; source read authorization alone cannot fix it.

D:

Concurrency tuning cannot repair a permission-denied response for writes at the target account.