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 15

Question 140

A deployment identity has Owner at subscription scope, but a new VM is rejected with RequestDisallowedByPolicy for an unapproved size. What should the team do first?

  1. Inspect the applicable Azure Policy assignment and its allowed-size parameters, then use an approved VM size or authorized exemption.
  2. Disable Microsoft Entra authentication for the deployment identity.
  3. Add Storage Blob Data Owner on the resource group.
  4. Assign a second Owner role directly to the VM.

Explanation

Correct Answer

A:

Azure Policy with a deny effect can reject resource create or update requests that violate assigned governance requirements, even if the deploying principal has broad Azure RBAC Owner rights. The error identifies a policy decision rather than a missing resource-management permission. Inspect the effective policy at subscription and management-group scopes, confirm the allowed VM SKUs, and correct the deployment or request a documented exception where permitted. Adding more RBAC roles will not override a valid deny policy.

Incorrect Answers

B:

Changing authentication mechanisms cannot make a policy-prohibited VM size compliant with Azure resource governance. The deployment request is reaching Azure Policy and being rejected by its deny condition. The fix concerns the policy parameters, selected SKU, or a properly authorized exemption, not a reduction in identity authentication controls.

C:

Storage Blob Data Owner governs blob-data operations and has no bearing on whether an Azure Policy permits a VM size. Granting it would expose unrelated storage data privileges without resolving the deployment denial. The administrator should examine the applicable policy and choose an approved VM SKU instead.

D:

Adding another Owner allow assignment does not neutralize Azure Policy's deny evaluation, and a rejected VM may not exist as an assignable resource. The identity already has extensive management rights. The deployment is blocked because the selected SKU violates governance settings, so the team must address the policy requirement or approved exception process.

Question 141

A compliance report lists principals and Azure role names but omits assignment scope and whether grants are inherited. Why is that insufficient for interpreting effective resource permissions?

  1. Every Azure RBAC role assignment is automatically subscription-wide.
  2. A report needs only the tenant's resource tags to calculate RBAC access.
  3. Role names alone uniquely determine every resource that can be accessed.
  4. The report must include each grant's scope and inheritance path to determine where its actions apply.

Explanation

Correct Answer

D:

Azure RBAC evaluation depends on three essential dimensions: principal, role definition, and assignment scope. Two principals with the same role name may have very different effective reach when one assignment is at a management group and another is at a single resource. A report that omits scope and inherited status cannot identify which resources are actually covered. Add the assignment's scope and parent hierarchy, and review group memberships, conditions, and deny assignments where necessary for a complete interpretation.

Incorrect Answers

A:

Azure RBAC supports management-group, subscription, resource-group, and individual-resource scopes. Assignments inherit downward only from their actual placement, so many roles are far narrower than the subscription. Omitting the scope would lose the most important distinction needed to interpret effective privileges in the compliance report.

B:

Azure resource tags are metadata used for governance, cost classification, and querying, not substitutes for authorization assignments. Tags do not reveal the principal, role, or scope of RBAC grants. A meaningful access report must include the actual role-assignment hierarchy and relevant identities rather than infer access from labels.

C:

A role definition describes possible actions, but the assignment scope determines the resources on which those actions can apply. Reader at one VM and Reader at subscription scope have very different reach. Without scope information, an auditor cannot conclude which child resources the principal can view or where the grant was inherited from.

Question 142

An application has Storage Blob Data Reader with an Azure ABAC condition requiring an Azure Private Link endpoint for data reads. It tries to read through the storage account's public endpoint, and no other grant applies. What should happen?

  1. The condition denies this read because the request is not through the required private endpoint.
  2. Assign ARM Reader to the storage account to override the failed data-plane condition.
  3. Switch blob storage redundancy to ZRS, allowing all public endpoint reads.
  4. Data Reader always permits all reads regardless of a condition on the assignment.

Explanation

Correct Answer

A:

Azure role-assignment conditions can constrain supported blob operations using attributes such as the network path that services the request. Here the data read reaches the public endpoint rather than the specified Private Link endpoint, so the condition is not satisfied for this grant. The app should use the required private network path and matching DNS configuration, not broaden RBAC. Other independent grants would have to be considered separately, but none exist in this scenario.

Incorrect Answers

B:

ARM Reader grants visibility into resource metadata and does not bypass an ABAC condition on the Blob Data Reader assignment. The application is attempting a content read through a public endpoint, not trying to enumerate ARM properties. Correct the network path or authorized condition rather than adding unrelated management-plane Reader permissions.

C:

Zonal redundancy changes how data is replicated within a region; it does not rewrite Azure RBAC conditions or the authorization context of a public endpoint request. Altering redundancy would leave the private-link condition unmet while creating unrelated availability and cost changes. Preserve authorization controls and use the required endpoint path.

D:

The role definition supplies potential DataActions, but a condition on a supported role assignment further limits when those actions are authorized. Possessing the correct role name does not cancel the private-link requirement. A request using the forbidden public route can fail despite an otherwise eligible principal.

Question 143

A deployment request returns Azure AuthorizationFailed. The cloud team needs to determine which principal and effective permissions were evaluated before changing any roles. What evidence should it collect?

  1. The caller's object ID, requested action and resource scope, direct/group/inherited role assignments, and applicable denies or conditions.
  2. Only the user's display name and the resource's tag values.
  3. Only the subscription's list of virtual machines.
  4. Assign Owner temporarily to reproduce the request and then remove it.

Explanation

Correct Answer

A:

Azure authorization decisions depend on the authenticated principal, the operation being attempted, and the target scope. To diagnose AuthorizationFailed, identify the exact principal object ID and failing resource provider action from the error or Activity Log, then review all direct and inherited role assignments, group memberships, and applicable deny or conditional grants. These checks distinguish missing permissions from an unexpected identity or wrong scope. Escalating to subscription Owner before tracing the effective access path would create unnecessary risk and obscure the actual defect.

Incorrect Answers

B:

Display names and ordinary resource tags are insufficient to determine which Azure RBAC principal was evaluated or which actions it may perform. Authorization requires stable identity information, actual role definitions, scopes, and any deny or condition. The team needs the failing operation and principal object ID, not just human-readable labels.

C:

A VM inventory cannot show whether the denied operation involved storage, policy, networking, or another resource provider. It also omits the caller's effective role assignments and the requested action. Begin with the specific AuthorizationFailed event and trace the identity and scope through relevant Azure RBAC assignments and constraints.

D:

Granting Owner before understanding the authorization failure can mask the missing permission and expose broad resource and role-assignment capabilities. A controlled investigation should first enumerate the caller, exact failed action, scope, inherited or group grants, and applicable restrictions. Escalation is not a safe substitute for analyzing the original denial evidence.

Question 144

New storage accounts must be blocked during deployment if they leave public network access enabled. Existing role assignments should not be changed. Which Azure governance control most directly enforces this requirement?

  1. Assign an Azure Policy definition with a deny effect that evaluates storage account network properties.
  2. Add a CanNotDelete lock to the resource group.
  3. Give deployment identities a Reader role instead of Contributor.
  4. Assign an audit-only Azure Policy definition.

Explanation

Correct Answer

A:

An Azure Policy definition using the deny effect can evaluate storage account properties during Azure Resource Manager creation or update requests. If the requested configuration violates the public network access requirement, Azure rejects the noncompliant operation before resource provisioning. The policy must be assigned at the desired management group, subscription, or resource-group scope and use supported aliases for the evaluated property. This enforces an organization-wide configuration rule without changing individual users' Azure RBAC permissions.

Incorrect Answers

B:

A CanNotDelete management lock protects existing resources against certain deletion requests; it does not evaluate the public network access setting of a newly requested account. A deployment with the wrong network configuration can still violate the standard. A targeted deny-effect Azure Policy is the correct preventive governance mechanism.

C:

Removing deployment write permissions would indiscriminately block resource creation, including compliant storage accounts. The request is to enforce a property-specific storage security standard rather than prohibit all deployments. Azure Policy deny can test the network setting while allowing properly configured resources to be created by authorized principals.

D:

An audit effect identifies noncompliant resources and records their state but ordinarily does not block the attempted deployment. The business requirement explicitly calls for denying new accounts with public access enabled. Use a policy with a deny effect for the supported property instead of accepting a noncompliant deployment and merely reporting it later.

Question 145

The operations team wants to identify existing Azure resources that violate a configuration standard, but deployments must remain permitted during the observation period. Select TWO actions that meet this requirement.

  1. Configure a modify-effect policy to silently rewrite every existing resource.
  2. Review the assignment's Azure Policy compliance results for the evaluated resources.
  3. Assign a relevant Azure Policy definition using the audit effect.
  4. Configure a deny-effect policy to reject future noncompliant create requests.
  5. Exempt every resource from the assigned policy before evaluation.

Explanation

Correct Answers

B:

A policy assignment does not itself communicate which existing resources failed the rule until its compliance state is evaluated and inspected. The Azure Policy compliance experience identifies relevant noncompliant resources and supports follow-up decisions during the observation phase. Reviewing results is an independently necessary operational step alongside assigning an audit-effect policy. It allows the team to verify the control's targeting and make remediation plans without blocking current deployments.

C:

The audit effect evaluates resource compliance without serving as a preventive deployment denial for the matched condition. Assigning the definition at the intended governance scope lets operations assess resources against the standard while continuing the observation-only phase. The definition must target the appropriate resource types and properties so the results are meaningful. Audit is therefore the suitable policy behavior when the organization wants visibility before deciding whether to enforce restrictions.

Incorrect Answers

A:

A modify policy and associated remediation can change resource properties when supported, rather than merely inventorying compliance status. The team has requested no automatic remediation or disruption during the observation period. Audit-based evaluation supplies evidence without modifying the affected resources, which is the correct initial governance posture.

D:

A deny effect is designed to prevent matched noncompliant resource requests, which conflicts with the explicit instruction that deployments remain permitted. It may be useful later after the observation period, but it is not the right action for an audit-only pilot. Use the audit effect and inspect its results instead.

E:

Exempting all resources defeats the intended observation program because compliant and noncompliant resources would no longer be assessed normally. The organization needs evidence of which resources fail the standard. A correctly scoped audit policy followed by compliance review provides that information without requiring blanket exemptions.

Question 146

Existing Azure resources are missing required CostCenter tags. The organization also wants future eligible resources to receive those tags automatically where supported. Which policy approach should be evaluated?

  1. Use a suitable modify-effect policy with a managed identity and remediation task for existing resources.
  2. Assign Reader to the policy managed identity.
  3. Use audit only and expect all missing tags to be written automatically.
  4. Apply a CanNotDelete lock to every resource.

Explanation

Correct Answer

A:

Azure Policy's modify effect can add or alter supported resource properties such as tags when its definition, aliases, and evaluation mode permit the operation. The policy assignment typically needs a managed identity with appropriate permissions for modification or remediation, and existing noncompliant resources require an explicit remediation task rather than retroactive assumptions. Future evaluated create or update operations can be modified according to the policy's conditions. Validate the identity's role assignment and test the policy against relevant resource types before organization-wide enforcement.

Incorrect Answers

B:

Reader allows viewing resource metadata but does not provide the write operations necessary for a managed identity to perform policy-based remediation. The identity must have the permitted role and actions described by the policy definition's role requirements. Without that authorization, a remediation task can fail even though the policy detects missing tags.

C:

The audit effect records compliance state but does not automatically write missing tag values to existing resources or modify future deployments. It can identify the problem, yet the request includes supported remediation of noncompliant metadata. A modify-effect policy and authorized remediation workflow are required for automatic tag changes.

D:

Management locks restrict certain resource management operations and do not create tags or populate tag values. A lock could complicate future remediation while leaving all CostCenter omissions intact. The requested capability is governance-based property modification, which is provided by a properly configured modify policy where the resource provider supports it.

Question 147

A company wants every new eligible resource to have a diagnostic setting deployed when one is missing, and older resources must be remediated. Which Azure Policy effect is most appropriate?

  1. deny, because denial installs the required diagnostic settings.
  2. Add subscription Owner to every application operator.
  3. audit, because it automatically creates missing diagnostic settings.
  4. deployIfNotExists with a managed identity and a remediation task for existing resources.

Explanation

Correct Answer

D:

Azure Policy's deployIfNotExists effect can identify an absent related configuration and deploy the required resource or extension using a template when conditions and permission prerequisites are satisfied. The policy assignment needs an identity that can create the diagnostic setting and any required dependent resources. Existing resources are not guaranteed to be retroactively changed just because the policy was assigned; use a remediation task for those that are eligible and noncompliant. Validate the diagnostic destination and supported resource types before rollout.

Incorrect Answers

A:

A deny effect blocks noncompliant resource create or update operations; it does not deploy a diagnostic setting as a remedy. The organization wants the missing related configuration to be created. A deployIfNotExists policy with correctly authorized deployment identity supports that outcome, whereas deny would simply reject requests.

B:

Expanding application operators' Azure RBAC permissions does not automatically attach diagnostics to resources and introduces unnecessary management authority. Azure Policy deployment of a related resource requires a definition, assignment identity, and template-based deployment workflow. Operator privileges should remain separate from governance remediation mechanics.

C:

The audit effect records noncompliance without deploying a missing diagnostic setting. It is useful for inventory, but the stated requirement includes automatic installation of the related configuration. deployIfNotExists is designed for that deployment behavior and can be paired with remediation to address existing eligible resources.

Question 148

The governance team has five related Azure Policy definitions for storage security. The team wants to manage and assign those definitions together at a management group. Select TWO required actions.

  1. Add all five policies as tags on the management group.
  2. Create a separate subscription for each policy definition.
  3. Create an Azure Policy initiative that references the five definitions.
  4. Assign a Reader role to every VM in the management group.
  5. Assign the initiative at the intended management-group scope.

Explanation

Correct Answers

C:

An Azure Policy initiative, also called a policy set definition, groups related policy definitions under one logical governance package. It can supply shared parameters and a consistent compliance view while preserving each included definition's effect. Creating the initiative is necessary because the team wants to administer several related controls as one set rather than maintaining disconnected individual assignments. The initiative's definition should be reviewed to ensure all five required policies are included and parameterized correctly.

E:

Creating an initiative definition alone does not make its controls apply to resources. The team must also create an assignment at the approved management group so that evaluation can reach descendant subscriptions and resources as intended. This step is independent of constructing the initiative and controls where the grouped standards take effect. Review exclusions, inherited policy assignments, and policy evaluation results after the assignment to avoid accidentally applying the controls more broadly than authorized.

Incorrect Answers

A:

Tags are descriptive metadata rather than executable Azure Policy definitions. Tagging a management group with policy names would not evaluate storage resources or enforce the associated effects. A real initiative groups policy definitions, and an initiative assignment attaches their evaluation to the intended Azure governance scope.

B:

Subscriptions are billing, resource, and governance boundaries; creating five new subscriptions would not solve the desire to manage several policy definitions together. Azure Policy initiatives are expressly designed to group related controls for a single assignment. Reorganizing subscriptions would add complexity without creating the required policy set.

D:

Azure RBAC Reader governs resource visibility, not the grouping or evaluation of five Azure Policy definitions. Per-VM role grants would neither create an initiative nor apply storage standards to descendant resources. The correct operations are to define the policy set and assign it at the management-group scope.

Question 149

A legacy project has approval to temporarily diverge from one Azure Policy rule. The exception must be scoped, documented, and expire automatically. How should governance record it?

  1. Apply a CanNotDelete management lock to the legacy resource.
  2. Create a scoped Azure Policy exemption with justification and expiration.
  3. Edit the global policy definition so the rule no longer applies to anyone.
  4. Assign Owner to the project's deployment identity.

Explanation

Correct Answer

B:

Azure Policy exemptions let a resource or resource hierarchy be exempted from a specific assigned policy or initiative control where supported and authorized. The exemption can record the business justification, metadata, and expiration so the deviation is visible and time-bounded rather than hidden. Its assignment reference and scope should match only the approved legacy project; other resources must remain evaluated normally. This separates an authorized temporary exception from weakening the global policy or changing user permissions to evade compliance.

Incorrect Answers

A:

A management lock protects against accidental deletion or modification depending on its type, but it does not authorize an exception to an Azure Policy rule. It can even complicate approved remediation work. Use the policy exemption mechanism with the correct scope and expiry rather than an unrelated resource lock.

C:

Changing the shared policy definition would weaken governance for all consumers, not only the approved legacy workload. The authorization is temporary and limited in scope. A policy exemption can document the deviation for the specific assignment and resource while preserving the original organization-wide control for other projects.

D:

Broad Azure RBAC rights do not turn a noncompliant resource into a compliant one or create a policy exception. A deny policy can still block requests from an Owner. The organization needs an explicit, documented Azure Policy exemption, not a privilege escalation that fails to record the authorized deviation.

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.