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 29

Question 280

A legacy HTTPS storage client fails after the account minimum permitted TLS version is increased to the security-approved baseline. What is the durable remediation?

  1. Disable storage-network firewall restrictions to allow legacy TLS negotiation.
  2. Upgrade the client to negotiate a supported TLS version while retaining the approved storage minimum TLS setting.
  3. Change the storage account replication from LRS to GRS.
  4. Issue a SAS with write permission so the old TLS handshake is accepted.

Explanation

Correct Answer

B:

The client must support the account minimum TLS protocol for HTTPS requests to succeed without weakening the required security baseline.

Incorrect Answers

A:

Storage firewall rules govern network admission; removing them cannot add an obsolete TLS version to a secure handshake.

C:

Data redundancy is unrelated to TLS protocol negotiation between the client and storage service.

D:

SAS permission bits authorize operations after a secure connection and cannot bypass TLS version negotiation.

Question 281

A security review finds an Azure Storage account allows containers to opt in to anonymous Blob reads. Policy requires anonymous access disabled at the entire account, while authenticated reads remain possible. Which control should change?

  1. Disable the storage account setting that permits anonymous Blob access, while keeping approved authenticated methods enabled.
  2. Create a Blob SAS for anonymous visitors and leave account-wide anonymous access permitted.
  3. Assign Reader on the resource group; this disables container anonymous policies automatically.
  4. Switch account redundancy from ZRS to GRS, which restricts anonymous Blob operations.

Explanation

Correct Answer

A:

Disallowing anonymous Blob access at the storage account overrides per-container public exposure while leaving authenticated Blob authorization available.

Incorrect Answers

B:

A bearer SAS grants delegated access; issuing more SAS links does not turn off the account’s anonymous Blob access capability.

C:

Management-plane Reader access does not change the storage account’s anonymous Blob service setting.

D:

Storage redundancy affects replica placement, not whether anonymous HTTP blob reads are permitted.

Question 282

An Azure Storage account must accept Blob reads only through a private endpoint from an approved VNet. DNS and private routing are already tested. What account-level network action completes the public-network ban?

  1. Disable public network access on the storage account while preserving the approved Blob private endpoint and DNS path.
  2. Enable anonymous Blob read access and keep the public endpoint open.
  3. Allow 0.0.0.0/0 in the storage account IP firewall as a fallback.
  4. Assign Storage Blob Data Owner at subscription scope to all clients without changing network configuration.

Explanation

Correct Answer

A:

Disabling public network access prevents public endpoint traffic while authorized private endpoint requests can continue through validated private routing.

Incorrect Answers

B:

Anonymous public access would increase public data exposure rather than enforce a private-only network boundary.

C:

An all-source public IP allow rule contradicts the required ban on public endpoint requests.

D:

Data-plane role grants cannot by themselves prevent public endpoint reachability or satisfy the private-only access policy.

Question 283

A production storage account hosts blob evidence and Azure Files shares. Operations is considering permanently deleting the entire account after decommissioning an application, but has not inventoried its contents or dependent services. Which action should precede the deletion decision?

  1. Delete the storage account immediately because Azure automatically retains all file shares and blobs after account deletion.
  2. Inventory the account data, consumers, protection/backup state and lifecycle dependencies, then decide what must be retained or migrated before deletion.
  3. Change the account name in the resource group; renaming preserves data while decommissioning the original endpoint.
  4. Turn off anonymous blob access and assume that operation removes the account and its data safely.

Explanation

Correct Answer

B:

The risk is deletion of the entire service namespace and stored data, not a routine configuration toggle. Inventory blobs, shares, backups, consumers and retention obligations, and migrate or protect required data before an approved deletion.

Incorrect Answers

A:

Deleting a storage account is destructive and is not an automatic object-recovery process. Unexamined blobs, shares and service dependencies could be lost or broken.

C:

An Azure storage account name forms its service endpoints and cannot simply be renamed to carry its existing namespace to a new name. A newly named account requires an intentional migration.

D:

Disabling anonymous blob access changes an authorization exposure setting; it neither inventories dependent content nor safely decommissions a storage account.

Question 284

The records team is provisioning a new Azure Blob storage account for evidence files. Every uploaded blob version must be protected against overwrite or deletion for 90 days, while new evidence must remain uploadable. The account has not yet been created. Which configuration supports this requirement?

  1. Create a supported storage account with version-level immutability enabled, enable blob versioning, and configure a 90-day time-based retention policy for protected versions.
  2. Set the storage account access tier to Archive at creation and rely on that tier to reject all modifications.
  3. Enable blob soft delete for 90 days but leave immutability policies and blob versioning disabled.
  4. Apply an Azure Resource Manager CanNotDelete lock to the storage account and assume it blocks all Blob REST API delete and overwrite requests.

Explanation

Correct Answer

A:

Version-level immutable storage supports write-once-read-many retention for blob versions while allowing additional objects and versions to be created. The new account can be provisioned with support for version-level immutability, and blob versioning must be enabled for version-level time-based policies. A 90-day retention rule then protects applicable versions from being overwritten or deleted during the retention interval. The administrator should confirm account feature compatibility and test policy activation before relying on it for evidence preservation.

Incorrect Answers

B:

Archive is a blob access tier for infrequently accessed data, not the immutable-storage authorization mechanism. Archived blobs have retrieval and rehydration limitations, but access-tier selection alone does not create a time-based WORM retention guarantee. It also cannot replace a version-level retention policy for newly uploaded evidence.

C:

Blob soft delete retains deleted blobs for potential recovery during the configured retention period; it is not equivalent to preventing deletion or modification. Without the required immutability policy, an authorized write can still alter data. Version-level WORM protection must be designed separately from soft-delete recovery features.

D:

An ARM CanNotDelete lock protects supported control-plane deletion requests, but Azure Blob data operations use separate data-plane interfaces. Such a lock does not substitute for a blob immutability policy on versions. It also does not establish a 90-day content-retention rule on each uploaded evidence object.

Question 285

A workload requires premium Azure block-blob performance, but its proposed account is a standard StorageV2 account. No data has been deployed. What must the administrator change before provisioning the workload?

  1. Enable GRS on the standard StorageV2 account and assume redundancy changes its performance tier to Premium.
  2. Add a private endpoint to the standard account; Private Link automatically converts standard storage performance to Premium.
  3. Provision an eligible Premium block-blob storage account and choose only supported regional redundancy settings for that type.
  4. Turn on the Archive access tier at account creation; Archive provides the premium low-latency transaction tier.

Explanation

Correct Answer

C:

The workload specifies a premium block-blob account type. Choose that account type before creating it and verify supported redundancy and regional availability; existing storage account types cannot be converted in place.

Incorrect Answers

A:

GRS adds asynchronous replication to a secondary region, not Premium block-blob storage performance. The account kind and performance requirements must match.

B:

Private endpoints change network connectivity and exposure. They do not convert a general-purpose standard account into a premium block-blob account.

D:

Archive is an offline, low-cost Blob access tier, not premium transaction performance. It would undermine the low-latency workload.

Question 286

An analytics team is creating a new standard Azure Storage account for a data lake. Its application needs Data Lake Storage Gen2 directory operations and directory-level ACLs rather than only flat Blob names. Which creation setting enables those capabilities?

  1. Create a standard StorageV2 account and leave Hierarchical namespace disabled; add directory ACLs to blob prefixes afterward.
  2. Create a Premium FileStorage account using SMB shares and expect the Data Lake filesystem endpoint to be available.
  3. Enable Blob public anonymous access on the storage account; this automatically enables Data Lake directory semantics.
  4. Create a standard StorageV2 account with Hierarchical namespace enabled and configure directory-level access appropriately.

Explanation

Correct Answer

D:

Microsoft documents enabling Hierarchical namespace on a standard general-purpose v2 (or supported premium block-blob) account to unlock Azure Data Lake Storage Gen2 capabilities. This creates the intended directory structure and supports directory/file access controls, subject to correct permissions.

Incorrect Answers

A:

A standard StorageV2 account can store block blobs, but the flat namespace does not by itself provide Data Lake Storage Gen2 hierarchical directory and ACL behavior. Blob prefixes are naming conventions, not full hierarchical filesystem directories with the requested Data Lake APIs.

B:

Premium FileStorage targets Azure Files workloads, not the Data Lake Storage Gen2 namespace and filesystem endpoint. SMB share features do not substitute for enabling a hierarchical namespace on an eligible Blob-capable account.

C:

Anonymous Blob access controls whether public unauthenticated reads are allowed; they do not create hierarchical directories, filesystem APIs, or POSIX-style ACLs. This setting would also expand exposure without satisfying the data-lake requirement.

Question 287

A government agency is creating a standard general-purpose v2 storage account for logs in a zone-enabled Azure region. Its data residency contract prohibits copying logs outside that region, but service must remain usable if one availability zone fails. Which redundancy setting best meets both constraints?

  1. Locally redundant storage (LRS), because its replicas are automatically written synchronously across three availability zones.
  2. Geo-redundant storage (GRS), because asynchronously replicating to a paired region complies with the no-out-of-region requirement.
  3. Zone-redundant storage (ZRS), subject to storage account type and regional availability support.
  4. Read-access geo-zone-redundant storage (RA-GZRS), because a secondary region is necessary for zone-only failures.

Explanation

Correct Answer

C:

ZRS writes storage replicas synchronously across three or more Azure availability zones inside the primary region. This protects against a zone failure without creating a geo-replicated secondary-region copy. It is therefore the appropriate redundancy selection when the agency requires in-region residency together with zonal availability. Confirm that the chosen region and general-purpose v2 account support ZRS, and separately validate application retry behavior during service transitions after an outage.

Incorrect Answers

A:

LRS stores the storage account replicas within a single physical location in the selected region. It guards against local hardware failures but cannot guarantee that the data remains available after that entire zone fails. The case explicitly requires surviving an availability-zone outage while retaining data in the one allowed region, so an LRS account is insufficient.

B:

GRS replicates data to a secondary geographic region, which violates the agency’s explicit residency restriction. Its primary-region replication uses locally redundant storage and therefore is not the zone-redundant primary-region design asked for. A secondary copy can be valuable for regional disaster recovery in other contracts, but is prohibited by this case.

D:

RA-GZRS combines primary-region zone redundancy with asynchronous replication to another region and secondary read access. Although it provides additional resilience, the extra geographic copy breaches the agency’s mandatory single-region data residency rule. The requested failure domain is one availability zone, not loss of the whole region; ZRS covers the stated requirement without off-region replication.

Question 288

Before a possible Azure-region outage, an application team wants its standard blob account to maintain an asynchronously replicated secondary-region copy. Secondary read access before failover is not required, and a nonzero replication lag is acceptable. Which redundancy selection is sufficient?

  1. RA-GRS is mandatory; GRS does not copy any data to another region unless read-access is enabled.
  2. Locally redundant storage (LRS), because LRS automatically copies all data asynchronously to a paired region.
  3. Zone-redundant storage (ZRS) alone, because zone replication always creates a replica in another Azure region.
  4. Geo-redundant storage (GRS) for asynchronous replication to the paired region.

Explanation

Correct Answer

D:

GRS meets the stated cross-region durability requirement by asynchronously replicating from the LRS-backed primary to the paired region. The team must accept possible lag and nonzero RPO.

Incorrect Answers

A:

RA-GRS adds read access to a secondary geo replica; it is not required merely to create that replica. GRS already replicates asynchronously.

B:

LRS protects data within a single physical datacenter in the primary region. It has no secondary-region replica.

C:

ZRS synchronously replicates within availability zones of one primary region. It does not provide geo replication to a second region.

Question 289

An Azure Blob account must support read-only reports from the paired secondary-region endpoint before any account failover. No write access to the secondary is needed. Which replication option provides that read capability?

  1. Use ordinary GRS and assume its secondary endpoint is open for client reads before failover.
  2. Use ordinary ZRS; its other availability zones expose a separate cross-region read endpoint.
  3. Use read-access geo-redundancy, such as RA-GRS or RA-GZRS where supported.
  4. Use GZRS without read access and assume the secondary region is readable as soon as objects are copied.

Explanation

Correct Answer

C:

RA-GRS and RA-GZRS enable read access at the secondary endpoint while writes continue to go to the primary. Secondary reads may lag because geo replication is asynchronous.

Incorrect Answers

A:

GRS creates a secondary-region copy but does not make it readable before failover. The RA feature is the deciding requirement.

B:

ZRS provides zone-level redundancy in the same region and cannot offer a paired secondary-region read endpoint.

D:

GZRS has geo redundancy but does not expose its secondary for reads before failover unless the account uses the RA-GZRS variant.

Question 290

A noncritical test blob workload has an approved requirement for replicas only inside one primary Azure datacenter and prioritizes minimum redundancy cost. Which option matches that failure-domain acceptance?

  1. ZRS, which places synchronous copies across separate availability zones and costs more than LRS.
  2. RA-GRS, which enables a read-only distant secondary endpoint through geo-replication.
  3. LRS, which maintains locally redundant copies within the primary physical location.
  4. GZRS, which combines primary zonal resilience and a geographically separate secondary copy.

Explanation

Correct Answer

C:

Locally redundant storage keeps replicas in the primary region’s local physical location and is the fitting low-cost option when zonal/geo risks are accepted.

Incorrect Answers

A:

ZRS protects across independent availability zones, which exceeds the stated single-datacenter requirement.

B:

RA-GRS introduces cross-region asynchronous copies and secondary reads beyond the low-cost local-copy requirement.

D:

Geo-zone-redundant storage extends durability across zones and regions, creating unnecessary redundancy for the stated minimal-cost local scenario.