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 18

Question 170

A storage private endpoint has been requested from a different subscription, but the portal shows the connection as Pending. DNS already resolves privately; requests still fail. What configuration should be checked?

  1. Have the storage owner approve the private endpoint connection request before relying on that path.
  2. Change the private DNS A record to a different private address while the pending connection remains unapproved.
  3. Recreate the private DNS zone group while leaving the endpoint connection in Pending approval.
  4. Grant the requester Owner in the consumer subscription as a way to get the remote storage resource to approve its own private endpoint connection.

Explanation

Correct Answer

A:

Cross-owner Private Link connections can require explicit provider-side approval. Private DNS alone cannot make a pending connection usable.

Incorrect Answers

B:

DNS changes do not approve a Private Link connection; the service owner must authorize the pending endpoint request.

C:

Correct DNS does not authorize a pending private endpoint connection. The storage resource owner must approve the request.

D:

Control over the consumer subscription alone does not replace the target storage owner’s approval of a cross-subscription endpoint request.

Question 171

A storage account must reject legacy TLS client connections below the organization's supported minimum version. A few old scripts still connect with outdated libraries. Which account configuration addresses the server-side requirement?

  1. Configure the storage account's supported minimum TLS version and update incompatible clients.
  2. Configure the minimum TLS version only in the client scripts while leaving the storage account server policy unchanged.
  3. Enable Secure transfer required without setting a server-side minimum TLS version.
  4. Restrict the storage firewall to approved source networks without configuring minimum TLS.

Explanation

Correct Answer

A:

The minimum TLS setting controls the oldest protocol version accepted by supported storage endpoints. Clients must negotiate an accepted version.

Incorrect Answers

B:

Client-side configuration does not enforce a minimum TLS version against other legacy clients that can still reach the account.

C:

Secure transfer requires HTTPS but does not alone express the specific permitted minimum TLS protocol version.

D:

Network filtering limits origin IPs but does not reject outdated TLS protocols from still-authorized clients.

Question 172

A legacy script uses http:// for Blob endpoints and fails after security baseline changes, though the credentials are valid. What account policy most directly explains the failure?

  1. Change the storage account minimum TLS setting while leaving the script on unencrypted HTTP.
  2. Disable anonymous Blob access and authenticated HTTP always becomes HTTPS automatically.
  3. Change the storage account access tier to Hot while keeping the script’s plaintext HTTP URL.
  4. Secure transfer required rejects plaintext HTTP, so clients must use HTTPS.

Explanation

Correct Answer

D:

Secure transfer required enforces encrypted requests on applicable storage endpoints. The client should use HTTPS rather than weakening the security baseline.

Incorrect Answers

A:

TLS-version negotiation applies to HTTPS. A request using plaintext HTTP is rejected by Secure transfer required even if the client is otherwise capable of modern TLS.

B:

Disabling anonymous access changes authorization, not HTTP transport. The script must explicitly use an HTTPS endpoint.

C:

Access tier affects storage pricing and retrieval, not the account-level requirement for an encrypted transport.

Question 173

A new Azure Storage account has no customer-managed key configured. A reviewer says all blobs are therefore stored unencrypted. What should the administrator clarify?

  1. Azure Storage applies service-side encryption at rest by default using Microsoft-managed keys unless a supported alternate key configuration is selected.
  2. Enable anonymous Blob access and it creates customer-managed encryption keys.
  3. Use only HTTPS clients and transport encryption is the sole mechanism for data-at-rest encryption.
  4. Choose GRS rather than LRS because only geo-redundant storage supports at-rest encryption.

Explanation

Correct Answer

A:

Azure Storage encryption at rest is enabled by default. Customer-managed keys change key control rather than deciding whether baseline storage encryption exists.

Incorrect Answers

B:

Public read access changes authorization exposure, not the source or existence of data-at-rest encryption keys.

C:

HTTPS protects data in transit; Azure Storage uses separate server-side encryption of the persisted objects.

D:

Encryption at rest is a storage-service default across supported redundancy configurations; GRS selection is not its prerequisite.

Question 174

A team configures Blob object replication between two storage accounts and expects its Azure Files SMB share to replicate under the same rule. What should be explained?

  1. Object replication covers Azure Files because both services use the same storage account name.
  2. Enable Blob versioning on both accounts and this will make SMB file shares eligible for blob object replication.
  3. Blob object replication policies apply to eligible block blobs rather than Azure Files shares.
  4. Create a blob object-replication policy with a filter matching an Azure Files share URL.

Explanation

Correct Answer

C:

Azure Blob object replication and Azure Files are distinct storage services with different replication mechanisms. File share protection requires a supported file-specific design.

Incorrect Answers

A:

A common account does not merge blob and file API feature eligibility.

B:

Blob versioning supports eligible blob object replication but does not convert Azure Files shares into block blobs.

D:

Azure Files paths are not eligible source or destination block blobs under the Blob object replication feature.

Question 175

A deployment agent can configure a storage account using Azure Contributor but AzCopy upload using Entra authentication returns authorization failure. Which authorization must the operator check?

  1. Grant the appropriate Storage Blob Data Contributor or other required blob data action at the relevant scope.
  2. Grant Storage Blob Data Reader to the deployment agent and retry the upload.
  3. Add another management Contributor grant and it provides data writes.
  4. Assign Storage File Data SMB Share Contributor to the agent at the storage account scope and repeat the Blob upload.

Explanation

Correct Answer

A:

Entra-authenticated AzCopy operations need the correct storage data-plane actions. Broad management rights are not a substitute for scoped blob write authorization.

Incorrect Answers

B:

Blob Data Reader supports reading objects, not writing new blob content. Upload through Entra needs a suitable blob data write role.

C:

Repeating a control-plane role does not add a missing data action.

D:

The SMB Share Contributor role targets Azure Files authorization; it does not grant the Blob data actions required for the Entra-authenticated AzCopy upload.

Question 176

A regulatory archive must prevent data modification or deletion for seven years, even by ordinary storage data administrators. Soft delete alone can recover a deletion but does not prohibit one. Which control is required?

  1. Assign Storage Blob Data Reader to the compliance officer while retaining ordinary write access for everyone else.
  2. Enable only blob soft delete for fourteen days and allow all users to permanently delete content afterward.
  3. Configure an appropriate immutable storage time-based retention policy for the eligible container or blobs, with retention mode and governance approvals carefully planned.
  4. Enable Blob versioning with no immutable policy and prior versions can never be deleted early.

Explanation

Correct Answer

C:

Immutable storage provides write-once-read-many protection for the governed period. Locked retention settings require deliberate governance because shortening retention may be prohibited.

Incorrect Answers

A:

The compliance officer's read role does not constrain other principals who still have write or delete authority.

B:

Soft delete offers restoration within retention but does not itself prevent the deletion request from taking effect.

D:

Versioning can preserve earlier versions for recovery but does not enforce seven-year WORM retention against authorized deletion.

Question 177

A general-purpose v2 storage account has hierarchical namespace DISABLED. An app stores eligible block blobs for several business units in one container. Lifecycle transitions must target only blobs with the blob index tag RetentionClass=Cold, regardless of blob name. Which supported filter should the administrator configure?

  1. Use the blob-name prefix filter 'RetentionClass=Cold' without considering where that string occurs in the path.
  2. Configure the transition for every blob, and tagging objects afterward will automatically exclude the other business units.
  3. Set a lifecycle filter on arbitrary user-defined blob metadata named RetentionClass, without creating a blob index tag.
  4. Use the lifecycle rule's blob index tag match filter for the RetentionClass key with the value Cold.

Explanation

Correct Answer

D:

In this flat-namespace account, blobIndexMatch can select eligible block blobs by the exact index-tag key and value without depending on their paths. Blob index tag filters are not integrated with lifecycle management for hierarchical-namespace accounts.

Incorrect Answers

A:

A path-prefix filter compares container/blob names, not blob index-tag key/value pairs. It cannot select blobs by a tag that appears only in the tag index.

B:

Without the specified blob index-tag match condition, eligible blobs for other business units could be transitioned as well; tags do not retroactively narrow an unfiltered rule.

C:

Lifecycle blobIndexMatch uses supported blob INDEX tags, not arbitrary metadata fields. A matching user-defined metadata property is not interchangeable with a blob index tag.

Question 178

A file share is accidentally deleted, but soft delete was enabled at the storage account. The share remains inside the retention window. What should an operator do to restore the content?

  1. Use the Azure Files undelete or restore-share workflow for the deleted share before the retention period expires.
  2. Restore an Azure Blob snapshot as the method for recreating the deleted SMB file share and its contents.
  3. Use Blob soft delete's undelete-blob command on each SMB file path.
  4. Create an empty replacement share and Azure automatically copies the old content into it.

Explanation

Correct Answer

A:

File share soft delete retains eligible deleted shares for recovery. Restore operations must observe supported naming and retention conditions.

Incorrect Answers

B:

Blob snapshots protect blobs, not an Azure Files share deletion. Use the share-level undelete capability during its retention window.

C:

Blob recovery APIs and Azure Files share recovery are distinct mechanisms.

D:

A new empty share has no automatic relationship to the deleted retained share and may cause a name conflict.

Question 179

A lifecycle rule moves base blobs to a cooler tier when they have not been modified for 90 days. An application uploads a recent replacement to an old blob name. What matters for eligibility?

  1. The storage account creation date controls every blob's age regardless of writes.
  2. Evaluate the rule's supported age basis, such as days since the blob's last modification, rather than assuming an old name makes the replacement eligible.
  3. Use a time-based rule triggered only by blob creation and a recently overwritten base blob keeps its oldest original creation time.
  4. Azure always uses the blob filename's embedded date instead of object metadata.

Explanation

Correct Answer

B:

Lifecycle age predicates use supported object timestamps, not arbitrary filenames. A fresh overwrite can reset relevant modification-age calculations.

Incorrect Answers

A:

Account creation is unrelated to the last modification of a particular blob.

C:

The rule in the scenario is based on modification age. Selecting creation-age logic changes when a recently replaced blob becomes eligible.

D:

Names do not become authoritative timestamps for lifecycle policies unless explicitly encoded into a supported prefix rule.

Question 180

A file-share administrator creates frequent share snapshots but management needs protection from accidental removal of the storage account itself. What additional design consideration is essential?

  1. Create additional snapshots in the same storage account and treat their number as protection against deletion of the containing account.
  2. Switch the storage account to GRS and use its asynchronous secondary replica as the sole recovery strategy for deliberate account deletion.
  3. Use supported Azure Files backup or independently managed retention protection rather than assuming in-account snapshots survive every account-level loss event.
  4. Enable share soft delete and rely on its retention policy as an independently isolated copy after the entire storage account is removed.

Explanation

Correct Answer

C:

Share snapshots are useful point-in-time versions but have a different isolation and deletion model than independently governed backup recovery points.

Incorrect Answers

A:

More snapshots improve recovery options for file changes but do not place the copies outside the same storage-account failure or deletion boundary.

B:

Storage redundancy protects against supported infrastructure failures; it is not independently governed backup retention for destructive account-level actions.

D:

Share soft delete is scoped to recoverable deleted shares inside the existing storage-account protection boundary. It is not an independent backup of a deleted entire account.