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 17

Question 160

A platform team wants all resources currently in resource group rg-secure, and resources created there later, to inherit the same deletion protection. Where should a CanNotDelete lock be applied?

  1. On the tenant's Microsoft Entra directory.
  2. On one storage account inside rg-secure.
  3. On the resource group rg-secure itself.
  4. Only to the VMs that currently exist in rg-secure.

Explanation

Correct Answer

C:

Azure management locks assigned to a parent scope are inherited by resources contained in that scope, including resources added after the lock is created. Applying CanNotDelete at rg-secure therefore gives consistent management-plane deletion protection without separately attaching a lock to each present and future resource. Review which child resource types and related extension resources will be affected. The lock does not restrict authorized data-plane deletion for services such as Blob Storage, so data lifecycle protection requires additional controls.

Incorrect Answers

A:

Microsoft Entra directory roles and settings are not the Azure Resource Manager scope for locking a resource group's infrastructure. The deletion restriction must be applied in the Azure management hierarchy that contains rg-secure. A lock on the group is inherited by its resources; a directory configuration would not substitute for it.

B:

A lock on an individual storage account applies to that resource and relevant descendants or extension resources, not to sibling VMs or future resources elsewhere in the group. The team wants group-wide deletion protection. Put the CanNotDelete lock on rg-secure rather than on an arbitrary child resource.

D:

Individual VM locks would protect those current resources but would not automatically cover newly created storage accounts, databases, or other resources in the group. The requirement explicitly includes future descendants. A resource-group-level CanNotDelete lock provides inherited protection at the intended common scope.

Question 161

A service principal has Contributor on a VM but receives a lock-related error when deleting it. The VM has a ReadOnly lock and the service principal is not permitted to manage locks. What should occur?

  1. Delete the VM through a different Azure portal blade while retaining the lock.
  2. Give the service principal another Contributor assignment.
  3. Convert the VM's managed disk to another performance tier.
  4. An authorized lock administrator must review and remove or adjust the lock before any approved deletion.

Explanation

Correct Answer

D:

A ReadOnly management lock blocks both updates and deletion through Azure Resource Manager, regardless of the service principal's otherwise permitted Contributor actions. The principal cannot bypass it and does not have the lock-management permission necessary to alter the protection. If deletion is approved, a properly authorized administrator must adjust the lock through the controlled process before retrying. Granting unrelated resource roles would not resolve the blocker, and the system should reject the operation when no approval exists.

Incorrect Answers

A:

The lock is enforced by Azure resource management APIs rather than only by a particular user interface. Moving the same delete request to another portal page does not bypass a ReadOnly lock. The user must obtain authorized lock removal or keep the resource protected.

B:

The existing Contributor grant already permits many resource-management operations. The denial comes from the ReadOnly lock, an independent restriction that a second identical role cannot remove. The appropriate response is lock governance by an authorized principal rather than adding redundant Azure RBAC assignments.

C:

Disk tier changes affect storage performance and cost, not whether the VM's ARM delete operation is blocked by a management lock. The principal must not perform unrelated infrastructure changes while the protection remains active. A lock-authorized administrator should handle any approved exception or deletion workflow.

Question 162

A diagnostic setting attached to a locked Azure resource cannot be modified even though the engineer has monitoring configuration rights. What should the engineer inspect?

  1. Whether an unrelated VM can be restarted.
  2. The inherited resource lock and how it applies to the diagnostic setting extension resource.
  3. Only the engineer's Storage Blob Data Reader role.
  4. Whether the diagnostic setting name contains uppercase letters.

Explanation

Correct Answer

B:

Azure diagnostic settings are extension resources associated with a parent Azure resource. Management locks can be inherited by extension resources, so a ReadOnly or other applicable lock on the parent may block the diagnostic setting's ARM update or deletion. The engineer should inspect the effective locks on the parent and confirm the failed operation before asking a lock-authorized administrator to adjust protection for an approved change. Adding monitoring permissions alone will not override an inherited management lock.

Incorrect Answers

A:

An unrelated VM restart does not determine which locks affect the diagnostic setting attached to the protected resource. Azure resource locks are scoped and inherited through resource hierarchies. Inspect the locked parent and extension's operation to identify the actual restriction before attempting any configuration change.

C:

Blob Data Reader controls data retrieval from storage containers, not the management write required to change Azure Monitor diagnostic settings. The engineer already has relevant monitoring rights, and the error concerns inherited management protection. The correct investigation is the resource lock affecting the extension resource.

D:

The casing of a diagnostic setting's display name is not a general mechanism for bypassing a ReadOnly management lock. The update is blocked because the extension resource inherits protection from its parent. Investigate the effective lock and the exact ARM operation rather than changing cosmetic resource naming.

Question 163

An approved maintenance window requires updating an Azure extension resource, but its parent's ReadOnly lock rejects the management-plane update. What procedure preserves change control?

  1. Change the operator's Microsoft Entra display name.
  2. Assign subscription Owner to the extension resource operator and leave the lock.
  3. Delete the entire parent resource so its lock disappears.
  4. Have a lock-authorized administrator temporarily adjust the effective lock, perform the update, and restore protection.

Explanation

Correct Answer

D:

A ReadOnly management lock blocks ARM updates on the protected resource and applicable extension resources, even for otherwise authorized writers. Because the maintenance change is approved, a principal with lock-management permissions can temporarily adjust the effective protection in a controlled window, carry out the specific change, validate it, and reapply the required lock. This avoids permanent weakening of protections or broad RBAC escalation. The team should document the temporary exposure and ensure no inherited ancestor lock remains unresolved.

Incorrect Answers

A:

A user's display name has no effect on an ARM management lock or its inheritance to extension resources. The denial is due to a resource protection rule, not a string attached to the principal. The lock-authorized workflow is necessary to permit the approved update.

B:

Owner is an Azure RBAC allow role, but it does not bypass a ReadOnly management lock. Escalating the operator's privileges would not make the blocked ARM update succeed and would add unnecessary access-management powers. The authorized lock must be adjusted through the existing change-control process.

C:

Deleting the parent resource is destructive and may itself be blocked by the same ReadOnly lock. The maintenance request concerns only a controlled extension update, not removing the underlying workload. Use an authorized temporary lock adjustment and restore protection after confirming that the specific change succeeded.

Question 164

A storage account is protected with a CanNotDelete management lock. An application nevertheless deletes an Azure Files share by using an authorized data-plane API. Which statement explains the result?

  1. The storage account must be locally redundant for the lock to apply.
  2. The lock guards control-plane deletion, while certain authorized data-plane share deletion requests remain possible.
  3. The application automatically became subscription Owner by deleting the share.
  4. CanNotDelete locks guarantee that no Azure Files share can ever be deleted.

Explanation

Correct Answer

B:

Azure resource management locks apply to ARM control-plane operations rather than to every storage service data-plane request. Azure Files exposes operations through different management and service APIs, so a share delete performed through an authorized data endpoint can succeed even when a management-plane delete would be blocked. Administrators must use storage-specific safeguards, appropriate share-level access restrictions, backup, and soft-delete behavior where supported to protect content. A storage account management lock alone should never be treated as universal data protection.

Incorrect Answers

A:

Storage redundancy influences durability and replica placement, not whether ARM locks apply to management requests. Switching between LRS and other redundancy options cannot turn a management lock into a data-plane authorization control. Protect share data with appropriate storage service safeguards and permissions.

C:

Performing a data-plane delete does not grant Azure RBAC subscription Owner. Authorization for storage share operations can use other credentials and data permissions. The result is explained by the separation of API planes, not a silent elevation of the application's Azure management role.

D:

A CanNotDelete lock protects supported Azure Resource Manager deletion operations, not all data-plane requests to Azure Files. Share deletion through an authorized storage service API may remain possible. The observed outcome does not prove the lock is broken; it proves that management-plane and data-plane protection are distinct.

Question 165

A subscription has a ReadOnly management lock. One child resource has a separate CanNotDelete lock. An administrator wants to update the child resource through ARM. Which restriction applies?

  1. The inherited ReadOnly lock is the effective stronger restriction and blocks the update.
  2. The child CanNotDelete lock always overrides the subscription ReadOnly lock.
  3. Azure RBAC Contributor on the child permits the update despite both locks.
  4. The locks apply only to storage blob data and have no effect on ARM updates.

Explanation

Correct Answer

A:

Azure management locks are inherited from parent scopes, and the most restrictive applicable lock controls the resource. ReadOnly blocks management-plane updates as well as deletion, whereas CanNotDelete generally allows ordinary updates while blocking deletion. Because the subscription's ReadOnly protection flows down to the child, the resource-specific Delete lock does not make writes permissible. A lock-authorized administrator must resolve the inherited ReadOnly restriction before performing any approved management update.

Incorrect Answers

B:

Azure does not use a 'closest lock wins' rule that replaces stricter ancestor restrictions with a weaker child lock. The most restrictive applicable lock takes precedence. A child CanNotDelete lock cannot restore management-write operations that are blocked by the inherited subscription ReadOnly lock.

C:

Contributor can grant management-write actions, but management locks are independent restrictions that can block those actions even for Owner. The subscription ReadOnly lock remains effective on the child regardless of Contributor's ordinary permissions. Adjusting RBAC is not a substitute for an authorized lock change.

D:

Azure resource management locks primarily restrict control-plane operations; that includes ARM updates on the protected child resource. Blob data-plane behavior is a separate issue. The stated update uses Azure Resource Manager, so the inherited ReadOnly lock is directly relevant and blocks the attempted modification.

Question 166

Finance requires every new eligible Azure resource to include a CostCenter tag from the approved catalog. Deployment should fail if the tag is missing. What should administrators implement?

  1. An Azure Policy tag requirement with an appropriate deny effect, plus tagged deployment templates.
  2. A CanNotDelete lock on the subscription.
  3. A resource-group tag named CostCenter without any policy.
  4. A subscription Reader role for all developers.

Explanation

Correct Answer

A:

Azure Policy can evaluate the presence or approved value of a resource tag and deny noncompliant create or update requests where the resource type supports that enforcement. Assign the policy at the necessary governance scope and parameterize the allowed CostCenter values. Including the tag in ARM or Bicep templates makes compliant deployments predictable, while the policy prevents accidental omissions through other provisioning paths. Check tag support and exclusions before enabling the rule across resource types that may not expose the same tag properties.

Incorrect Answers

B:

A CanNotDelete lock protects against certain resource deletions, not against omission of CostCenter during provisioning. It has no tag-validation logic and could create unrelated operational constraints. Use Azure Policy to enforce the property requirement rather than applying a management lock unrelated to cost classification.

C:

Resources do not automatically inherit tags from their parent resource group or subscription. Adding CostCenter only to the group does not guarantee that each new resource carries the required value. A policy or explicit tagging in deployments is needed to enforce the metadata on eligible child resources.

D:

Reader would prohibit most resource deployments, whether they contain valid CostCenter tags or not. The business rule is a conditional metadata standard, not a blanket ban on creating resources. An Azure Policy deny condition can inspect the tag property and reject only requests that violate the requirement, while suitably authorized deployments continue.

Question 167

An Azure resource group is tagged Environment=Production. A newly created VM in that group has no Environment tag. What explains this, and how can the organization enforce inheritance?

  1. The VM must automatically inherit the tag, so the portal is showing a temporary error.
  2. Rename the resource group to Production so the VM acquires the tag.
  3. Resource-group tags do not automatically propagate; add tags to the VM or use a supported Azure Policy inheritance rule.
  4. Assign Reader to the VM to reveal the inherited tag.

Explanation

Correct Answer

C:

Azure resource groups and the resources inside them have separate tag collections. Creating a VM within a tagged resource group does not automatically copy the group's metadata to the VM. An administrator can supply the tag during deployment or assign a supported Azure Policy modify rule such as inheriting a tag from the resource group. Existing VMs may need a remediation task. This preserves the distinction between a container's labels and the tags used on each billable resource.

Incorrect Answers

A:

Azure does not provide implicit resource-level tag inheritance from every resource group. The missing VM tag is expected unless the deployment or an inheritance policy explicitly populates it. Treating the absence as a portal refresh issue would fail to implement the desired cost and governance metadata.

B:

Resource group names and tag key-value pairs are independent metadata concepts. Renaming a group is not a supported way to populate child-resource tags, and resource groups cannot be renamed directly through ARM. Add the tag to the VM or configure supported policy-based tag inheritance instead.

D:

An Azure RBAC Reader assignment controls configuration visibility, not whether tag metadata exists on a VM. The resource remains untagged regardless of which principal views it. Apply the desired tag through a deployment or an Azure Policy inheritance rule rather than changing the viewer's permissions.

Question 168

Resource groups rg-prod and rg-test carry Environment=Prod and Environment=Test, respectively. Existing child resources in both groups are missing the Environment tag, while some child resources have a deliberately different Environment value that must remain unchanged. New resources must inherit their own group's value only when the tag is absent. Which policy configuration meets these conditions, including old resources?

  1. Assign an Azure Policy append rule that copies the group tag and rely on it to remediate old resources automatically.
  2. Assign the built-in Inherit a tag from the resource group policy that replaces even deliberately different child values.
  3. Assign Inherit a tag from the resource group if missing using modify, grant its assignment identity remediation rights, and run a remediation task.
  4. Assign a deny policy to block untagged resources, and assume it will add inherited tags to existing resources.

Explanation

Correct Answer

C:

Azure Policy offers a modify-effect built-in definition named Inherit a tag from the resource group if missing. It reads the Environment value from each resource's parent group instead of injecting one global constant, while preserving deliberately populated child tags. The modify rule handles eligible future create or update requests. Existing missing tags need a separate remediation task executed using the assignment's managed identity with sufficient write permissions. Check indexed-mode applicability and tag support for the target resource types before applying it broadly.

Incorrect Answers

A:

Append evaluates eligible create or update requests, but it does not itself run the corrective operation on resources that were deployed previously. Those resources would remain without the inherited Environment value until separately updated or addressed. The requirement explicitly includes existing resources, so the modify-based built-in policy and a remediation task are better aligned with the stated lifecycle.

B:

The replace-style inheritance policy is useful when all child tags must continuously match the parent resource group. That conflicts with the exception in this case: a resource already carrying a deliberate Environment value must retain it. Selecting the if-missing variant is crucial because it only writes the inherited value when the child tag is absent.

D:

Deny can prevent noncompliant new requests from succeeding, but it is an enforcement decision rather than a tag-writing action. It neither derives the Environment value from each parent group nor corrects existing child resources that already lack tags. A deny-only policy can therefore block deployments while leaving the original historical tagging gap unresolved.

Question 169

A production resource is moved from one resource group to another. The destination group's CostCenter tag differs from the source's. What should the finance automation verify after the move?

  1. The moved resource's own tags, because group membership does not automatically replace resource tag values.
  2. The moved resource must always inherit the new group's tag immediately.
  3. Whether the operator has Microsoft Entra Directory Readers.
  4. Only the destination resource group's display name.

Explanation

Correct Answer

A:

Azure resource tags are stored on the resources that support them, separately from the tags on their containing resource groups. Moving a supported resource between groups does not establish a general rule that its CostCenter tag must become the destination group's value. Finance should inspect the resource's existing metadata and apply an authorized update or a policy-based inheritance rule if the billing model requires destination alignment. This avoids assuming that an organizational move automatically rewrites resource classification.

Incorrect Answers

B:

Azure does not automatically copy resource-group tags to child resources. A moved resource can retain its own tag values even when the destination group uses a different CostCenter. If consistency is required, deploy a suitable policy or update the resource explicitly rather than rely on implicit propagation.

C:

Directory Readers concerns visibility into identity objects, not the tag value stored on an Azure resource after a move. The issue is resource metadata and policy-driven inheritance behavior. The finance process should check the resource's CostCenter tag and any applicable Azure Policy rather than directory inspection rights.

D:

Resource group names help organize management containers but are not substitutes for the resource's actual tag values used by reporting workflows. Finance must inspect CostCenter metadata on the resource itself. A name change or group move does not reliably tell the billing system which tag was applied to the resource.

Question 170

A finance analyst needs monthly Azure spending grouped by Project tags across eligible resources. How should the team prepare the tagging data for Cost Management?

  1. Rely exclusively on the current VM names as the Project cost dimension.
  2. Assign subscription Owner to every finance analyst.
  3. Standardize Project tag names and values on resources, then group or filter costs by the supported tag dimensions.
  4. Disable tags and use a CanNotDelete lock for billing classification.

Explanation

Correct Answer

C:

Azure Cost Management can use resource tag metadata for supported cost allocation and grouping. To obtain meaningful project totals, administrators should standardize the Project tag key, define consistent allowed values, and apply those values to cost-accruing resources. They must also account for services that do not emit all tag dimensions in billing data and use supported cost inheritance features where appropriate. Grouping by a reliable Project tag is more meaningful than inferring project ownership from arbitrary VM display names.

Incorrect Answers

A:

VM names do not consistently represent project ownership across different Azure resource families or shared workloads. Cost reports may also include disks, networking, and services without matching naming conventions. Standardized Project tags and supported Cost Management grouping provide a more systematic metadata-based cost classification.

B:

Azure RBAC Owner grants broad infrastructure and access management permissions, not a standardized project cost dimension. It would create unnecessary privilege while leaving inconsistent tags unresolved. Finance needs permitted cost-report access and reliable resource metadata, which should be managed separately from subscription ownership.

D:

Management locks protect control-plane resource operations and do not provide a Project dimension for cost allocation. Removing tags would make the desired grouping harder, not easier. Standardize and retain relevant resource tags, then use supported Cost Management reporting views and filters.