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 31

Question 300

An Azure Storage account uses blob versioning and has an active object-replication policy. An administrator tries to turn blob versioning off but the change is rejected. What must be done before disabling versioning is allowed?

  1. Disable versioning by switching the account to a Storage File share and leave the replication policy active.
  2. Remove the object-replication policy from the account first, then disable blob versioning if no other feature or immutability requirement blocks that change.
  3. Delete only the current blobs, because replication policies do not depend on blob versioning.
  4. Change the storage-account public network access setting; the versioning dependency is controlled by the account firewall.

Explanation

Correct Answer

B:

Azure object replication depends on blob versioning. Microsoft requires existing object-replication policies to be removed before turning off versioning, and additional active immutability settings can independently prevent the change.

Incorrect Answers

A:

Blob versioning and object replication are Blob Storage data-protection features; migrating data to an Azure Files share does not satisfy the prerequisite for disabling versioning on the source account.

C:

Deleting live blobs is destructive and does not remove the object-replication policy dependency. Retained previous versions and policy configuration are separate objects.

D:

Storage network rules affect permitted clients, not the service-side object-replication dependency. Changing the firewall cannot override the versioning configuration prerequisite.

Question 301

An older Azure Storage account has AllowCrossTenantReplication currently set to true. Security requires that future Blob object-replication policies involving this account never connect to a different Microsoft Entra tenant. No existing cross-tenant object-replication policy uses the account. Which supported control directly enforces the requirement?

  1. Add an include-prefix filter named same-tenant/ to each container-pair replication rule.
  2. Assign the Reader role on the storage account to all users from the same tenant.
  3. Disable the source storage account change feed and keep the replication policies unchanged.
  4. Set the storage account AllowCrossTenantReplication property to false, and provide full account resource IDs when defining allowed same-tenant replication policies.

Explanation

Correct Answer

D:

Microsoft documents AllowCrossTenantReplication=false as the storage-account security control that prohibits new cross-tenant object-replication policies. Because there are no existing cross-tenant policies, it can be set directly; same-tenant policies must use full resource IDs for Azure to verify tenant identity.

Incorrect Answers

A:

An object-replication prefix filter selects blob names, not the Microsoft Entra tenant of a policy counterpart. A blob can be under same-tenant/ even when the destination account belongs to another tenant.

B:

Azure RBAC Reader does not enforce the object-replication tenant boundary. The object-replication security property controls whether the account can participate in cross-tenant policies.

C:

Change feed is required at the replication source; disabling it would disrupt eligible replication rather than limit participation to storage accounts in the same tenant.

Question 302

A team enables Azure Blob object replication between two storage accounts and expects all source account firewall allow lists, Azure RBAC role assignments and network restrictions to appear on the destination automatically. What correction should the administrator make?

  1. Keep the existing blob-copy rule but explicitly document that data replication never requires access configuration on either account.
  2. Copy the source storage account firewall settings into a blob metadata field and expect Azure to enforce them as destination network policy.
  3. Treat object replication as copying supported block blob data, versions, properties and metadata; separately configure and verify the destination account’s RBAC, network and security controls.
  4. Enable prefix filtering and assume the selected prefix becomes the destination account’s firewall policy.

Explanation

Correct Answer

C:

Object replication replicates eligible blob objects and their supported properties and metadata, not Azure Resource Manager account configuration. Set the destination security posture independently.

Incorrect Answers

A:

Some client authentication and account controls are needed separately; they are not created merely because an object replication rule copies object data. This option incorrectly rules out such configuration.

B:

Blob metadata is stored as object attributes. It is not an Azure RBAC role assignment or a storage-account firewall configuration.

D:

A replication prefix filters which blob names are copied. It is unrelated to destination firewall network rules or role assignments.

Question 303

An architect proposes Azure Blob object replication from storage account st-primary in one Azure region to st-secondary in another. The recovery contract requires every acknowledged block-blob write to be synchronously committed in both regions with zero data loss at failover. What should the Azure administrator report?

  1. Create an object replication policy with blob versioning on both accounts and change feed on the source, then promise synchronous write acknowledgements.
  2. Copy the storage account firewall, tags and access policies to the destination and treat those metadata copies as synchronous object replication.
  3. Restrict object replication to a selected prefix and assume filtered blobs meet a strict zero-recovery-point objective.
  4. Explain that Azure Blob object replication is asynchronous and cannot independently guarantee the stated synchronous cross-region zero-RPO requirement.

Explanation

Correct Answer

D:

Microsoft documents Azure Storage object replication as asynchronous copying of block blobs between source and destination accounts. Because of that delay, it does not provide a synchronous durability guarantee that every acknowledged source write is already available cross-region. Even when versioning, change feed and policies are properly configured, the administrator must identify the conflict with the zero-RPO contractual requirement and choose an architecture whose documented recovery guarantees actually meet the demand, rather than promising an impossible property.

Incorrect Answers

A:

Versioning and source change feed are prerequisites for Azure Blob object replication, but satisfying prerequisites does not make the replication synchronous. A successful client write to the source does not prove that the new version has already arrived in the destination region. The recovery point requirement therefore remains unmet.

B:

Storage account configuration and blob data replication are different concerns. Matching account network rules or metadata on another account does not replicate the committed blob contents. Moreover, object replication does not automatically clone every security or management setting, so these changes cannot establish the promised synchronous write consistency.

C:

A replication filter controls which objects a policy selects; it does not alter when destination copies become available. The selected objects still replicate asynchronously, and excluded objects might never be copied. Prefix filtering therefore cannot be offered as a zero-data-loss guarantee for all acknowledged writes.

Question 304

A company replicates block blobs from storage account prod-logs to dr-logs. Replicated data arrives, but analysts cannot read it because their Microsoft Entra storage data role exists only on prod-logs. What is the correct administrative repair?

  1. Edit the source blobs’ metadata to contain the role assignment and assume Azure turns that text into RBAC on dr-logs.
  2. Grant the analysts the minimum suitable Blob data-plane role at the appropriate scope on dr-logs and verify destination network access separately.
  3. Disable source blob versioning; roles will then replicate automatically as normal blob properties.
  4. Configure a prefix filter for logs/ and assume this also copies all Azure role assignments from the source account.

Explanation

Correct Answer

B:

Object replication copies supported blob objects and metadata, not Azure RBAC grants. The analysts need an explicit appropriate role at dr-logs, subject also to the destination network rules.

Incorrect Answers

A:

Blob metadata is application data associated with an object. It cannot provision Azure RBAC assignments at a storage-account or container scope.

C:

Versioning is an object replication prerequisite on both accounts. Turning it off would not grant user access and could stop replication.

D:

An include-prefix selects replicated blob names. It neither assigns destination principal permissions nor duplicates storage firewall policy.

Question 305

A newly created general-purpose v2 storage account contains payroll blobs. The compliance requirement is encryption at rest using Microsoft-managed keys, with no customer-owned Key Vault dependency. What should the administrator do?

  1. Configure a Key Vault customer-managed key and replace the default storage encryption key.
  2. Disable storage service encryption because HTTPS already encrypts the blobs.
  3. Rotate both storage account access keys to enable encryption at rest.
  4. Keep the default Azure Storage encryption configuration that uses Microsoft-managed keys.

Explanation

Correct Answer

D:

Azure Storage automatically encrypts account data at rest, using Microsoft-managed keys unless customer-managed keys are configured. No separate key vault is needed.

Incorrect Answers

A:

A customer-managed key introduces customer custody and a vault dependency, contrary to the requirement for Microsoft-managed keys.

B:

TLS protects connections, not stored data; disabling encryption at rest would not meet the stated control.

C:

Storage account access keys authorize requests and do not act as the at-rest key-management setting.

Question 306

A company is required to manage the root encryption key protecting Blob data in an existing storage account. The key must remain under its Azure Key Vault governance while the storage account retains its existing containers. Which configuration meets that requirement?

  1. Leave account encryption on Microsoft-managed keys and rotate the storage account SAS tokens.
  2. Assign Storage Blob Data Owner to the security team without changing encryption settings.
  3. Add an encryption scope based only on Microsoft-managed keys and assume this transfers key custody.
  4. Configure supported storage-account customer-managed encryption using a Key Vault key and an authorized managed identity.

Explanation

Correct Answer

D:

Storage accounts can use customer-managed keys protected in Key Vault or Managed HSM. A supported managed identity must be permitted to use the selected key.

Incorrect Answers

A:

Default Microsoft-managed encryption is managed by Microsoft, not the customer. SAS rotation concerns data authorization.

B:

Blob Data Owner is a data-plane authorization role; it does not select the account root encryption key.

C:

An encryption scope backed by Microsoft-managed keys does not give the customer custody of those keys.

Question 307

A security auditor claims that enforcing HTTPS for Blob requests eliminates the need to retain Azure Storage encryption at rest. Which response correctly describes the two controls?

  1. HTTPS protects data in transit, while Azure Storage encryption at rest protects the stored data independently.
  2. HTTPS turns storage account access keys into encryption-at-rest keys.
  3. Enabling TLS automatically switches a storage account from Microsoft-managed to customer-managed keys.
  4. Encrypting stored blobs automatically authorizes all clients to access them over HTTPS.

Explanation

Correct Answer

A:

Correct: Azure Storage encrypts data at rest separately from network transport protection; requiring HTTPS does not replace storage encryption.

Incorrect Answers

B:

Access keys authenticate signed storage requests; they are not the encryption-at-rest configuration.

C:

TLS and the choice of Microsoft-managed or customer-managed at-rest keys are separate settings.

D:

Encryption at rest does not grant data access; authorization and network policies still apply.

Question 308

A storage account uses a versionless customer-managed Key Vault key reference with automatic key-version updates. A new key version was created one hour ago. How can the team minimize disruption while retiring the old version?

  1. Keep the previous key version available for at least 24 hours and confirm Azure Storage has adopted the new version before disabling the old one.
  2. Immediately purge the previous key version; Azure Storage checks for updates continuously.
  3. Rotate the storage account access keys instead of permitting Azure Storage to use the new Key Vault key version.
  4. Remove the managed identity Key Vault cryptographic permissions after creating the new version.

Explanation

Correct Answer

A:

With automatic key-version updating, Azure Storage checks Key Vault daily. Allow at least 24 hours for the new version to be detected before disabling its predecessor.

Incorrect Answers

B:

Immediate purge can break encryption-key access because key-version discovery is not continuous.

C:

Storage account access keys are authorization secrets, not the Key Vault key version used for at-rest encryption.

D:

The managed identity needs cryptographic access to use the configured customer-managed key, including after rotation.

Question 309

An existing Azure Storage account uses a Key Vault customer-managed key. Blob reads begin failing after an administrator removes the storage managed identity’s Key Vault cryptographic access. The key is still enabled. What is the direct remedy?

  1. Restore the storage account managed identity’s supported Key Vault key permissions or crypto-service role.
  2. Open the storage account firewall to all public networks without changing identity permissions.
  3. Regenerate the storage account shared-access signing keys.
  4. Turn off container-level blob soft delete to release the encryption key.

Explanation

Correct Answer

A:

Storage must be allowed to access the configured key (for example wrap/unwrap/get through the appropriate vault permission model). Restoring the authorized identity’s key access addresses the failure.

Incorrect Answers

B:

Network firewall exposure does not restore a Key Vault authorization removed from the storage encryption identity.

C:

Shared-access signing keys authorize clients and cannot replace the customer-managed encryption-key permission.

D:

Soft delete retention for blobs is unrelated to the identity’s ability to use its Key Vault key.

Question 310

A new Azure Storage account must use a customer-managed encryption key held in Azure Key Vault. The storage account managed identity already has the required key permissions, and the vault has soft delete enabled, but purge protection is currently disabled. What additional vault setting is required?

  1. Create a user-delegation SAS for every Blob container so the key cannot be purged.
  2. Enable purge protection on the Key Vault before configuring Storage encryption with that customer-managed key.
  3. Disable Key Vault soft delete so key versions can be removed immediately.
  4. Rotate the storage account shared access keys because they are the customer-managed encryption root key.

Explanation

Correct Answer

B:

Azure Storage customer-managed keys in Key Vault require both soft delete and purge protection so the key cannot be permanently purged while storage remains dependent on it. Soft delete is already enabled in the scenario, making purge protection the missing prerequisite.

Incorrect Answers

A:

User-delegation SAS tokens authorize Blob requests; they neither protect Key Vault keys from permanent deletion nor meet Azure Storage customer-managed encryption prerequisites. Issuing them per container does not enable vault purge protection.

C:

Disabling soft delete does not meet the documented configuration requirement and would weaken key recovery protections. Soft delete is required for supported Key Vault-backed storage customer-managed encryption, not a feature to turn off.

D:

Azure Storage account access keys authenticate shared-key requests; they are unrelated to the Key Vault encryption key used for customer-managed server-side encryption. Regenerating them cannot enable Key Vault purge protection.