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 16

Question 150

A resource deployment is denied by Azure Policy because an assignment parameter lists the wrong permitted region. The proposed region is actually allowed by the company's standard. What should the governance owner do?

  1. Assign subscription Owner to the deployment identity.
  2. Move the VM to another availability zone within the same denied region.
  3. Disable all Azure Policy assignments in the tenant.
  4. Correct the authorized policy assignment parameter or deploy to an actually permitted region.

Explanation

Correct Answer

D:

Azure Policy definitions can evaluate configured parameters such as allowed locations during request validation. A deny caused by an incorrect assignment value must be addressed by reviewing the effective policy and its approved region list, not by giving the deployment identity more Azure RBAC rights. If the company standard allows the proposed region, an authorized owner can correct the erroneous assignment parameter and re-evaluate. If it is not allowed, the deployment should use a compliant region or follow the formal exception process.

Incorrect Answers

A:

Azure RBAC Owner can authorize resource-management operations, but it does not override an Azure Policy deny effect. The deployment is blocked by the assignment's region condition, not by missing write permissions. Granting Owner would create unnecessary risk while leaving the invalid policy parameter and denied request unresolved.

B:

An availability zone is an isolated location within an Azure region; changing zones does not change the resource's region value. A policy that denies a particular region will still evaluate that region as unapproved. The solution is to correct the permitted-location parameter or choose a policy-allowed region.

C:

Blanket removal of governance controls would affect many unrelated projects and could permit genuinely disallowed deployments. The current incident has a specific incorrect region parameter. Correct only the approved assignment or make the deployment compliant, preserving all other policies and required standards.

Question 151

An Azure Policy modify assignment has been applied successfully, but existing resources without required tags are still noncompliant. How should the team address those older resources?

  1. Add Reader to the managed identity and rerun compliance assessment.
  2. Create an Azure Policy remediation task for the eligible noncompliant resources.
  3. Delete and recreate every noncompliant resource.
  4. Change the policy effect to audit and expect the tags to appear.

Explanation

Correct Answer

B:

Assigning a modify-effect policy does not automatically guarantee that all previously deployed resources have their tags rewritten immediately. Existing resources commonly require a remediation task, performed by the assignment's managed identity with the necessary role permissions. The team should verify that the definition supports the tag operation and the relevant resources, then review remediation results and remaining compliance findings. Future create or update requests can be evaluated under the active policy separately from that retroactive remediation process.

Incorrect Answers

A:

Reader cannot perform the resource write actions needed for modify remediation. Running another assessment might update compliance reporting but will not add missing tags. The assignment identity needs the appropriate specified permissions and an actual remediation operation to change eligible existing resources.

C:

Recreating workloads is disruptive and usually unnecessary when a supported modify policy can repair eligible tag metadata. It may also remove data or change dependencies. Use the targeted remediation task and validate the results instead of replacing production resources merely to trigger policy evaluation again.

D:

Audit-only policy evaluation reports whether resources meet the standard; it does not update missing properties. Changing modify to audit would remove remediation behavior rather than fixing older noncompliant resources. A supported remediation task using the assignment identity is the appropriate mechanism to modify existing resources.

Question 152

A security team wants an Azure Policy control to evaluate development subscriptions but explicitly exclude production subscriptions under the same tenant hierarchy. Which deployment design best respects that boundary?

  1. Assign Owner to development users instead of the policy.
  2. Apply a Delete lock to all production subscriptions.
  3. Assign the policy at the tenant root management group without exclusions.
  4. Assign the policy at an approved development scope and apply documented exclusions or exemptions where necessary.

Explanation

Correct Answer

D:

Azure Policy assignment scope determines which Azure resources are evaluated, with exclusions and exemptions available to narrow or document selected exceptions. To keep production outside the control, place the assignment on the development management group or subscriptions when possible and verify the effective hierarchy. If a broader ancestor scope is unavoidable, use approved non-scope or exemption configuration that protects production from evaluation as intended. This avoids unexpected governance impact while preserving standard enforcement in the development estate.

Incorrect Answers

A:

Azure RBAC Owner governs who can manage resources; it does not implement an Azure Policy compliance rule limited to a set of development subscriptions. The request concerns which resources are evaluated by a policy. Role escalation is unrelated to that governance boundary and would introduce unnecessary privilege.

B:

Delete management locks restrict certain destructive operations but do not stop a broadly scoped Azure Policy assignment from evaluating production resources. They also impose different operational side effects. The correct approach is to design the policy assignment and exclusion scope to include only development as intended.

C:

A tenant-root assignment would generally reach all descendant subscriptions, including production. That contradicts the business rule limiting the control to development. The governance owner should choose a narrower development scope or configure explicit exclusions, rather than trusting a blanket assignment to avoid production resources automatically.

Question 153

A security baseline requires Azure to reject creation of VMs whose sizes are not on an approved SKU list. What should the team deploy and validate?

  1. A cost budget alert at the subscription level.
  2. A deny-effect Azure Policy that checks permitted VM SKUs using supported aliases or built-in allowed-size controls.
  3. A CanNotDelete management lock on each VM.
  4. A Reader role on the VM's resource group.

Explanation

Correct Answer

B:

Azure Policy can evaluate a proposed VM resource's size through supported property aliases and reject noncompliant create or update requests with the deny effect. The team should use the current built-in allowed VM SKU policy or a correctly authored custom definition, parameterize the approved list, and test its assignment at the intended scope. This prevents unwanted VM families from being deployed even by principals who have management roles, while still allowing approved sizes through the normal provisioning workflow.

Incorrect Answers

A:

Budgets track consumption and can send notifications when cost thresholds are reached. They do not prevent a new VM from using an unapproved SKU at deployment time. Azure Policy is the control that evaluates a resource's proposed size and can deny the request before provisioning completes.

C:

A Delete lock protects existing resources against certain deletion operations; it does not evaluate the SKU of newly requested VMs. It cannot serve as an allowed-size validation rule. A targeted Azure Policy deny effect is the appropriate enforcement mechanism for the specified deployment standard.

D:

Reader would prohibit all deployments by principals who held only that role, rather than evaluating approved versus unapproved VM SKUs. It is an access-management tool, not a conditional governance standard. A deny policy with the correct VM-size comparison allows authorized users to deploy compliant sizes while rejecting the rest.

Question 154

An Azure Policy assignment reports that unrelated resource types violate a storage-specific standard. The definition may have an incorrect mode or if-condition. What should the policy author investigate?

  1. The policy mode, resource type filters, property aliases, and if-condition targeting before trusting compliance results.
  2. Grant every resource group Owner so evaluation becomes accurate.
  3. Ignore all compliance results and permanently exempt the subscriptions.
  4. Change all resources to the same Azure region.

Explanation

Correct Answer

A:

Azure Policy evaluates resources according to its configured mode, condition expression, and supported aliases. If a storage-specific policy is applied to unrelated resource types, the author should inspect the resource-type filters and conditions that determine which resources are in scope. Incorrect targeting can produce misleading noncompliance results or unexpected deployment decisions. Test the revised definition on representative storage and non-storage resources before using the compliance report to drive enforcement or remediation.

Incorrect Answers

B:

Azure RBAC Owner determines resource-management authorization and does not correct the matching logic of an Azure Policy definition. A malformed resource-type condition can still evaluate unintended resources. The fix is to edit the policy's mode, if expression, and aliases, not to change users' privileges.

C:

A blanket exemption would conceal genuine storage configuration violations along with the false positives. The governance team should first diagnose and repair the definition's targeting logic. Once the rule correctly selects relevant resources, compliance reporting can be trusted and legitimate exceptions can be handled individually.

D:

Moving resources between regions is disruptive and unrelated to a policy that is incorrectly targeting resource types. The compliance problem concerns expression evaluation, not geographic placement. Correct the policy filtering so the storage standard applies only to the intended provider types and properties.

Question 155

Developers must continue updating a critical storage account's configuration, but accidental deletion of the account must be prevented. Which Azure management lock should you choose?

  1. A Storage Blob Data Reader role on the account.
  2. Reader role for the developers.
  3. CanNotDelete (Delete) on the storage account.
  4. ReadOnly on the storage account.

Explanation

Correct Answer

C:

A CanNotDelete management lock permits otherwise authorized ARM management reads and updates while preventing deletion of the locked resource. It therefore preserves the developers' ability to change supported storage account settings without allowing accidental deletion through the management plane. Apply the lock at the account or an approved ancestor scope and verify its inheritance. It does not prevent authorized blob data-plane deletion, so application data still needs separate protections such as soft delete and data authorization controls.

Incorrect Answers

A:

Blob Data Reader controls access to blob contents, not deletion of the Azure Storage account resource through ARM. It also lacks account configuration write permissions. The team needs a management lock that affects storage-account resource deletion, not a data-role assignment unrelated to the resource lifecycle.

B:

Reader would remove the developers' management write permissions rather than selectively prevent deletion of the account for all principals. The requirement is a resource-level safety guard while authorized editors retain their ability to update configuration. Use a CanNotDelete management lock instead of downgrading the operational team to read-only RBAC.

D:

A ReadOnly lock blocks management-plane update and delete operations, not just deletion. The developers explicitly need to continue modifying account configuration, so ReadOnly would be overly restrictive and interfere with normal administration. CanNotDelete protects the account against management deletion while permitting authorized configuration updates.

Question 156

An archive VM resource must not be modified or deleted through Azure Resource Manager, even by users who would otherwise have write permission. It can still be inspected. Which lock is suitable?

  1. ReadOnly management lock on the VM or its approved parent scope.
  2. CanNotDelete lock on the VM.
  3. Reader on one operator's user account.
  4. Storage Blob immutability policy on a VM resource.

Explanation

Correct Answer

A:

An Azure ReadOnly management lock prevents supported control-plane update and deletion operations while allowing reads of the locked resource. It applies across authorized Azure RBAC roles, so an Owner cannot simply ignore it. If the lock is placed on a parent resource group or subscription, descendants inherit the restriction. The administrator should evaluate dependencies and extension operations before deployment, because some seemingly observational portal actions use POST requests that a ReadOnly lock can block.

Incorrect Answers

B:

CanNotDelete prevents resource deletion but continues to permit authorized configuration modifications. The archive requirement forbids both edits and deletion through Azure management APIs. ReadOnly is therefore the appropriate lock, provided the team accepts its impact on update and action operations.

C:

A Reader role would limit only that particular principal's Azure RBAC actions, not every other privileged user. The scenario calls for a resource-wide restriction that overrides authorized management roles. A ReadOnly management lock applies at the resource level and protects against writes from any otherwise permitted operator.

D:

Blob immutability policies govern stored blob objects, not general Azure VM control-plane operations. They cannot replace a management lock on Microsoft.Compute virtual machine resources. Use a ReadOnly Azure resource lock to restrict the VM's ARM updates and deletes, while addressing any guest OS access separately.

Question 157

A resource group has a CanNotDelete lock. An operator with Contributor tries to delete the resource group and receives an error. What is required to proceed with an authorized deletion?

  1. Have a principal with lock-management permission remove the relevant lock before deleting the group.
  2. Assign Contributor a second time on the resource group.
  3. Move one unrelated VM to a new resource group and then delete the locked group.
  4. Rename the resource group and retry deletion.

Explanation

Correct Answer

A:

A management Delete lock on a resource group prevents deletion of the group and its protected resources even when ordinary Azure RBAC allows the operator to manage resources. Contributor does not necessarily have permission to remove the lock, which is a separate Microsoft.Authorization operation. If deletion is approved, an authorized lock administrator must remove the effective lock, confirm dependencies and scope, and then perform the deletion. If approval is absent, the lock should remain in place.

Incorrect Answers

B:

A duplicate Contributor role assignment does not remove the CanNotDelete management lock or grant the necessary authorization to manage locks. Azure evaluates the lock as an independent protection after resource permissions. The operator must follow the approved lock-removal workflow or abandon the deletion rather than layering extra role grants.

C:

Moving unrelated resources does not remove a lock on the target resource group and could introduce outages. The attempted operation is blocked by the CanNotDelete restriction on the group itself. The correct action is to obtain authorized lock management, not to reorganize resources in hopes of bypassing the protection.

D:

Changing a display name is not a supported bypass for a management lock; resource-group names are part of Azure resource identifiers and cannot simply be rewritten to escape protection. The lock remains applicable to its scope. An authorized administrator must explicitly address the effective lock before the deletion request can succeed.

Question 158

A subscription Owner cannot update the configuration of a VM because the parent resource group has a ReadOnly lock. Which conclusion is correct?

  1. Owner always supersedes an inherited management lock.
  2. The VM must have a Storage Blob Data Contributor assignment.
  3. The inherited ReadOnly lock blocks the VM's management-plane update despite Owner's RBAC permissions.
  4. Assign Contributor directly to the VM and retry.

Explanation

Correct Answer

C:

Azure resource locks are evaluated separately from Azure role-based access and take precedence over ordinary allow roles for protected management operations. A ReadOnly lock on a resource group is inherited by contained resources, including the VM in this case. Subscription Owner does not bypass the restriction. To perform an approved update, a principal with appropriate lock-management rights must follow the organization's controlled change process and reinstate required protection afterward.

Incorrect Answers

A:

The purpose of a management lock is to restrict operations across users and roles, including Owner. A parent ReadOnly lock can prevent a VM management update even when the user's RBAC actions would otherwise allow it. The operator must address the lock through an authorized workflow rather than assume broad role permissions cancel its effect.

B:

Storage blob data permissions are unrelated to Azure VM configuration updates through Microsoft.Compute. Granting a storage data role would expose unnecessary blob write rights while leaving the inherited management lock intact. The failing control is a ReadOnly lock on the VM's parent scope, not a missing data-plane authorization.

D:

Contributor is weaker than Owner for many management and access-administration functions, and neither role bypasses a ReadOnly management lock. A direct VM Contributor grant cannot subtract the inherited restriction. The authorized administrator must adjust or remove the applicable lock if the change is permitted.

Question 159

A storage account has a ReadOnly ARM management lock, but an application with valid blob data credentials can still overwrite blob content. Why is this possible?

  1. An account-level ReadOnly lock must be inactive if any blob is writable.
  2. Resource management locks restrict control-plane operations, not supported blob data-plane requests.
  3. ReadOnly locks silently convert all applications to subscription Owner.
  4. Blob content changes are impossible whenever a management lock exists.

Explanation

Correct Answer

B:

An Azure ReadOnly management lock protects the storage account resource from many ARM update and delete operations. Blob content requests sent to the storage data endpoint use the data plane, where authorization relies on credentials, data roles, SAS, or keys as applicable. The management lock therefore does not automatically block an authorized application from writing blobs. To prevent data modification, enforce appropriate storage data permissions, immutability or versioning policies, and network restrictions, rather than relying on an account-level ARM lock alone.

Incorrect Answers

A:

ReadOnly locks can remain fully effective on ARM operations while data-plane blob writes continue under separate authorization. Writable blobs do not prove the lock is disabled. The administrator should distinguish the API endpoint and operation type before drawing conclusions from application write behavior.

C:

A lock does not create or elevate Azure RBAC role assignments. The application can write because its data-plane request remains authorized independently of the account's management-plane lock. There is no implicit conversion to Owner; the security gap is that control-plane resource protection is not the same as blob-content write protection.

D:

Azure explicitly distinguishes data plane and control plane operations. A resource lock prevents selected management requests but cannot be assumed to freeze all service data transactions. The app's valid data credentials may permit overwrites; use blob-specific protection and access controls when immutable or read-only content is required.

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.