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 39

Question 380

A log-ingestion service writes continually to an Azure append blob using Append Block. Blob versioning is enabled on the account, but compliance expects an automatically generated previous version for every append. What should the administrator explain and recommend?

  1. Each Append Block call creates a separate immutable previous version, so no other control is necessary.
  2. Blob versioning must be disabled for every block blob because the account also contains an append blob.
  3. Changing the append blob metadata after ingestion automatically recreates every intermediate pre-append state as individual versions.
  4. Append Block does not create an automatic blob version for each append; use a supported explicit snapshot or another history/capture strategy when individual append states must be retained.

Explanation

Correct Answer

D:

Microsoft lists Append Block among write operations that do not trigger creation of an automatic blob version. If the business requires a recoverable state after each append, take supported explicit snapshots or implement another separately recorded history mechanism.

Incorrect Answers

A:

Azure Blob versioning does not create a new version for every Append Block operation. Assuming that each append automatically preserves a recoverable pre-append state can leave gaps in the organization’s required history.

B:

Blob versioning can still be enabled for the account and can retain prior versions when eligible write operations occur. The presence of an append blob does not force versioning off for all block blobs in the account.

C:

Setting blob metadata cannot retroactively reconstruct each earlier append state. An additional metadata write changes metadata but does not recreate the historical byte sequences that were never independently captured.

Question 381

Blob versioning has been enabled on a storage account for the past year. An analyst needs a read-only inventory of the earlier versions of one block blob, including their version IDs and timestamps. Which operation should be used?

  1. Restore or copy a previous blob version if versioning was enabled.
  2. Distinguish explicitly taken snapshots from automatically maintained previous versions.
  3. Copy the chosen previous version to the base blob following supported restore semantics.
  4. List previous versions with timestamps and verify which version contains required data.

Explanation

Correct Answer

D:

When Blob versioning was active for the relevant writes, the storage service records identifiable versions of the object. Enumerate the blob with versions included and inspect version IDs, timestamps and relevant properties. Use authorized data-plane listing and the correct container and blob name; versions created before the feature was enabled cannot be assumed to exist.

Incorrect Answers

A:

Restoring an earlier blob version changes what data are available from the current blob, whereas the analyst only wants to inventory historical writes. Starting a restore would introduce an unnecessary data change and would not generate the complete version-and-timestamp report being requested.

B:

Snapshots and automatically generated versions differ in how they are created. That distinction is useful background, but it does not enumerate the historical versions of this specific blob or show their version IDs and timestamps.

C:

Copying a previous version into the base blob creates another write and may change the current state of the object. The analyst has asked for a read-only inventory rather than a rollback, so promoting data is not the correct operation.

Question 382

A blob was overwritten at 09:00 while blob versioning was disabled. Versioning was enabled at 10:00, and the team now asks to recover the content from before the 09:00 overwrite. No previous version is listed. Which conclusion and next investigation are justified by Azure Blob versioning behavior?

  1. List previous versions with timestamps and verify which version contains required data.
  2. Restore or copy a previous blob version if versioning was enabled.
  3. Recognize that older history may not exist; inspect other backups.
  4. Distinguish explicitly taken snapshots from automatically maintained previous versions.

Explanation

Correct Answer

C:

Azure Blob versioning does not retroactively capture data overwritten before the feature was enabled. The missing 09:00 state therefore cannot be restored from a nonexistent version; investigate separately retained snapshots, soft-delete recovery when applicable, or an external backup. If none exists, the earlier bytes may be unrecoverable.

Incorrect Answers

A:

Listing versions is appropriate when historical versions may exist, but the administrator has already verified that none exists for this overwrite. Because the 09:00 operation preceded activation of versioning, another version-list request cannot reconstruct the earlier content. Check any independently retained recovery mechanism instead.

B:

A prior blob version can be copied to the current version only if that historical version was recorded. Here versioning was disabled at the 09:00 overwrite and no previous version exists. A copy operation has no recoverable source version, so it cannot be promised as a fix for this loss.

D:

Snapshots and versions are different recovery objects, but simply classifying them does not find a recovery point for this overwrite. Only a snapshot already retained independently of versioning, or another eligible backup/recovery state, could supply the pre-overwrite content.

Question 383

An Azure Storage account with hierarchical namespace disabled has Blob versioning enabled. Before a release, a client explicitly took a snapshot of block blob `audit.csv`; its snapshot timestamp is `2026-10-29T10:15:00.0000000Z`. A later write created a separate automatic blob version ID. An auditor needs to retrieve the bytes of the earlier explicit snapshot without changing the current blob. Which request identifies the correct historical object?

  1. GET the base blob URI with `?versionid=2026-10-29T10:15:00.0000000Z`, assuming an explicit snapshot timestamp is always a blob version ID.
  2. Copy the most recent automatic blob version over the current base blob, then GET the base URL without a query parameter.
  3. GET the base blob URI with `?snapshot=<later automatic version ID>`, because snapshot and version identifiers are interchangeable.
  4. GET the base blob URI with `?snapshot=2026-10-29T10:15:00.0000000Z` to read the explicitly captured, read-only snapshot without changing the current blob.

Explanation

Correct Answer

D:

Microsoft documents an explicit Blob snapshot as a point-in-time, read-only copy addressed by adding `snapshot=<snapshot timestamp>` to the base blob URI. The client can GET this snapshot while the live base blob and any automatically created versions remain untouched. This differs from enumerating previous versions or using a `versionid` selector.

Incorrect Answers

A:

The `versionid` query parameter targets a system-maintained blob version, not an explicitly created Blob snapshot. Even if both identifiers resemble timestamps, they are different objects with different URI parameters; substituting `versionid` for the documented snapshot timestamp does not correctly address this saved snapshot.

B:

Copying an automatic version over the live blob would create a new write and could change the production data, which the auditor is forbidden to do. The later version also does not identify the earlier explicit point-in-time snapshot. A read-only GET of the snapshot, not a restoration or copy, is required.

C:

A Blob snapshot is addressed by the `snapshot` timestamp parameter, while an automatically maintained version is selected using its distinct `versionid` identifier. Feeding a later version ID into the snapshot selector conflates two different history mechanisms and does not ensure retrieval of the specified earlier snapshot.

Question 384

A development app should use an old version's contents without changing current production blob. What is the most appropriate next administrative decision?

  1. Restore a previous version directly over the current production base blob.
  2. Copy the chosen previous version to the base blob following supported restore semantics.
  3. List previous versions with timestamps and verify which version contains required data.
  4. Read/download by version ID instead of promoting it to current.

Explanation

Correct Answer

D:

Azure Blob Storage supports read operations against a specific retained version ID. Give the authorized development workflow that ID and download or read that version without replacing the current blob. The production URL without a version selector continues to refer to the current state, and the previous version remains immutable.

Incorrect Answers

A:

A restore or copy may be useful if the goal is to overwrite the production base blob with historical content. Here the development application only needs access to an older value. Promoting an earlier version could disrupt the current application even though no production change is requested.

B:

Copying an old version to the base blob changes the current state and can create an additional version. That is appropriate for a deliberate rollback, not for reading historical content without changing the production object.

C:

Listing the blob's versions helps find the correct version ID but does not by itself let the development application consume the historical bytes. The client must request the specific version rather than implicitly reading the current blob.

Question 385

An Azure StorageV2 account has blob versioning enabled. A developer updates only the metadata of an existing block blob with Set Blob Metadata, leaving its content bytes unchanged. What is the versioning effect?

  1. Metadata-only writes change the current version in place without creating a previous version, because the content is unchanged.
  2. Set Blob Metadata creates a new current blob version, and the former current version becomes an immutable previous version.
  3. Azure Storage creates a new version only when an administrator explicitly takes a blob snapshot.
  4. Updating metadata automatically deletes all previous versions unless the account also has container soft delete enabled.

Explanation

Correct Answer

B:

The Set Blob Metadata write creates a new current version even when only metadata changes, preserving the earlier current state as a previous immutable version. This behavior can increase stored versions and associated costs.

Incorrect Answers

A:

Azure Blob versioning tracks certain write operations, not just changes to the payload bytes. Set Blob Metadata is documented as a version-creating operation when versioning is enabled.

C:

A snapshot is a separate manually created point-in-time copy. Automatic versioning captures supported write operations such as Set Blob Metadata without requiring a snapshot.

D:

Versioning preserves previous versions after a metadata update; it does not automatically delete the full history when container soft delete is absent. Retention/deletion policies are separate controls.

Question 386

An account's version count produces growing storage charges. Which Azure configuration or procedure is the best fit?

  1. Add retention/lifecycle rules for previous versions where business policy permits.
  2. List previous versions with timestamps and verify which version contains required data.
  3. Distinguish explicitly taken snapshots from automatically maintained previous versions.
  4. Restore or copy a previous blob version if versioning was enabled.

Explanation

Correct Answer

A:

Automatically generated blob versions may accumulate with writes and incur storage cost. A lifecycle policy can delete eligible previous versions after the organization-approved age or other supported conditions while keeping the current base blob intact. Verify legal retention and immutability before expiry; a cleanup rule is not a substitute for selecting the proper recovery period.

Incorrect Answers

B:

Listing versions identifies the objects that contribute to stored history, but enumeration alone does not stop old versions from accumulating. The policy needs an expiry or permitted cleanup mechanism rather than another report.

C:

Snapshots and blob versions differ in creation mechanisms, yet both can consume storage. Clarifying this distinction does not apply a retention limit to automatically created versions and therefore does not address the recurring cost increase.

D:

Restoring an old version creates or changes a current object state rather than expiring unneeded history. Using restoration to manage storage charges can increase the retained version count and is unrelated to enforcing the requested retention policy.

Question 387

An analyst already holds the Azure Reader management role on storage account `starchive`, and the account has Blob versioning enabled. Shared Key access is disabled; the analyst signs in through Microsoft Entra ID to list historical versions under container `audit`. Private DNS and network access are confirmed healthy, but the data-plane request returns `AuthorizationPermissionMismatch`. The analyst must list version IDs without writing Blob data. Which authorization change best meets the requirement?

  1. Assign Azure Reader again at the subscription scope; it automatically adds Blob data-plane read permission for OAuth calls.
  2. Assign Storage Blob Data Contributor at subscription scope to allow listing, even though the analyst is not authorized to write or delete blobs in unrelated accounts.
  3. Assign Storage Blob Data Reader to the analyst at the `audit` container scope, allow RBAC propagation, then retry an authorized list request with versions included.
  4. Enable anonymous container reads so the existing Reader role can enumerate versions without a data-plane grant.

Explanation

Correct Answer

C:

Storage Blob Data Reader grants supported Blob data-plane read and listing permissions to a Microsoft Entra principal. Assigning it at the `audit` container scope supplies the missing authorization without changing storage network controls or granting write access. Allow for RBAC propagation before retrying a listing request that includes versions.

Incorrect Answers

A:

The management-plane Reader role already provides Azure Resource Manager visibility but does not itself grant `blobs/read` data permissions for Microsoft Entra OAuth. Expanding the same management role from an account to its entire subscription still fails the specified data-plane authorization requirement.

B:

Storage Blob Data Contributor includes read access, but it also permits modifying or deleting blobs and granting it at subscription scope authorizes unrelated accounts. The case requires only read-only version enumeration of one container; Contributor over the whole subscription violates least privilege even if it can satisfy the requested read.

D:

Anonymous Blob access is not an Azure RBAC grant and would expose data beyond the named analyst. The account deliberately uses Microsoft Entra authorization and a private network path; allowing anonymous reads would weaken controls and does not resolve the least-privileged identity-based permission error.

Question 388

An ARM template defines a string parameter skuName, used by storageAccounts[0].sku.name. The parameter file supplies Standard_ZRS. What value is deployed for that storage account SKU?

  1. Standard_ZRS, because the resource SKU name references the supplied skuName parameter.
  2. Standard_LRS, because all storage account resource declarations silently override supplied SKU parameters.
  3. The subscription ID, because skuName is interpreted as a deployment-scope function.
  4. No storage account is deployed, because ARM parameters cannot be used inside resource properties.

Explanation

Correct Answer

A:

Resource property expressions can read parameter values; this resource receives Standard_ZRS at the referenced property.

Incorrect Answers

B:

ARM does not silently reset a supplied valid SKU value to LRS.

C:

A parameter reference is separate from scope/subscription expressions.

D:

ARM parameters are designed to supply resource configuration values during deployment.

Question 389

A Bicep file includes `resource app 'Microsoft.Web/sites@2024-04-01' = { name: 'web-prod' ... }`. An operator says that `app` becomes the Azure resource name. What is correct?

  1. `app` is the symbolic identifier within Bicep; `web-prod` is the deployed resource name and the type includes an API version.
  2. `app` is always the deployed site name, regardless of the name property.
  3. `2024-04-01` is a deployment date after which the resource is automatically deleted.
  4. `Microsoft.Web/sites` means the file declares a Microsoft Entra user rather than a Web App.

Explanation

Correct Answer

A:

The symbolic identifier is used for Bicep references; type@apiVersion selects the resource provider API, and name defines the deployed name.

Incorrect Answers

B:

The resource name comes from the name property, not from the symbolic name.

C:

The API version is not a resource expiry date.

D:

Microsoft.Web/sites refers to App Service web applications, not directory identities.

Question 390

An ARM template deploys a network interface and a virtual machine. The VM resource has `dependsOn` containing the network interface resource ID. How does this affect deployment?

  1. ARM schedules the NIC dependency before the VM resource rather than attempting the VM first.
  2. The NIC is deleted immediately after the VM is created.
  3. dependsOn converts the NIC into an existing-only resource declaration.
  4. The VM automatically receives a public IP even if the NIC has none.

Explanation

Correct Answer

A:

Explicit dependency ordering makes ARM wait for the dependent resource to complete before the VM deployment begins.

Incorrect Answers

B:

Dependency declarations do not delete prerequisite resources.

C:

dependsOn orders resources but does not change create/update declarations into existing references.

D:

IP assignment depends on the networking resources, not on dependsOn alone.