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 19

Question 180

An operations manager asks to move a resource group itself, with all its contents, into a different Azure subscription as a single resource. What is the supported Azure Resource Manager approach?

  1. Use the Move command on the resource-group object without examining its resources.
  2. Create or select a target resource group and move eligible contained resources to it after validating dependencies.
  3. Grant Reader at the destination subscription and assume the entire group moves automatically.
  4. Rename the source resource group to the target subscription ID.

Explanation

Correct Answer

B:

Azure Resource Manager does not support moving a resource-group container itself into another subscription as an atomic object. Instead, an administrator can move supported resources from the original group into an existing or newly created target group in the destination subscription, subject to same-tenant, service, identity, lock, and dependency constraints. Resource IDs change where the subscription or group segment changes, and source group settings such as tags and RBAC assignments are not simply carried over. Plan and verify those details before executing the move.

Incorrect Answers

A:

Resource-group containers do not have a universal cross-subscription move operation equivalent to moving eligible resources. The contents must be validated and moved to a destination group through the supported resource move workflow. Ignoring move restrictions and dependencies risks failures and broken references after the attempted management change.

C:

Azure RBAC Reader changes management visibility but does not move resources or resource groups. Cross-subscription changes require explicit resource-move operations and checks, not simply assigning a role. Create the target group, verify tenant and provider support, and move the eligible contained resources through the supported workflow.

D:

Changing a group name cannot relocate it between subscriptions, and Azure resource groups cannot be directly renamed. The subscription is part of the hierarchical resource identifier. To change ownership of supported resources, select a target group in the destination subscription and perform a validated resource move.

Question 181

A decommissioning engineer needs to delete one verified empty resource group in a subscription. Several other active groups have similar names. What is the safest direct action?

  1. Delete every resource group with a matching name prefix.
  2. Change the resource group's tags and assume Azure removes it automatically.
  3. Confirm the exact subscription and resource-group ID, then delete only the verified empty group with authorization.
  4. Delete the entire subscription because the target group is empty.

Explanation

Correct Answer

C:

Resource-group deletion is scoped to the selected Azure subscription and group identifier. Before deleting anything, the engineer should verify the intended resource group's full identity and current contents, including hidden or recently created resources and inherited locks. If the group is truly empty and the deletion is authorized, deleting that exact group does not require touching similarly named active groups. Use the resource ID and subscription context rather than relying solely on a short display name in an unfiltered list.

Incorrect Answers

A:

Similar naming does not establish a shared decommissioning authorization. Other groups with that prefix may contain production workloads. The requirement names one verified empty management container, so bulk deletion based on a string prefix would introduce unnecessary data-loss risk. Confirm and delete only the exact authorized group.

B:

Tags are descriptive metadata and do not trigger a general automatic resource-group deletion when edited. The empty group remains until an authorized delete operation is performed. Verify the group identity and contents and then delete that exact management container through Azure Resource Manager.

D:

A subscription can contain many unrelated groups and services. Deleting or canceling it is far broader than removing one empty resource group and could disrupt billing and workloads. The engineer should address the identified group at its precise scope, not change the lifecycle of the parent subscription.

Question 182

Subscription sub-pay already contains an Azure resource group named rg-payroll. An administrator tries to create another resource group named RG-PAYROLL in the same subscription so a different team can use a separate lifecycle boundary. Azure reports that the name already exists. Which explanation and correction are accurate?

  1. Create the second resource group in a different Azure region with the same letters; region alone makes the name unique within the same subscription.
  2. Rename the first resource group in place to rg-payroll-old so its existing resources remain under an unchanged resource-group ID.
  3. Retry with an alternative casing such as Rg-PayRoll because resource-group names compare as case-sensitive strings.
  4. Choose a genuinely different resource-group name: resource-group names are case-insensitive within a subscription, and altering capitalization cannot create a second group.

Explanation

Correct Answer

D:

Resource group names are unique within a subscription under case-insensitive comparison. Because rg-payroll and RG-PAYROLL are the same name for this purpose, use a genuinely distinct string such as rg-payroll-analytics to create the separate group. The fact does not imply names must be unique across unrelated subscriptions.

Incorrect Answers

A:

Changing the resource-group metadata region does not give another name namespace within the same Azure subscription. Resource group names are compared without regard to letter case at that scope. The requested second group must have a different actual name; selecting another region for the same name does not solve the conflict.

B:

Azure Resource Manager does not support directly renaming an existing resource group while retaining its group identity. A rename-like migration entails creating a new group and moving eligible resources with changed resource IDs. That is unnecessary here, where the desired operation is simply to create a second distinctly named group.

C:

Microsoft documents that resource-group names are case-insensitive, including comparisons such as ResourceGroup1 and resourcegroup1. A capitalization-only variant therefore refers to an existing name in the subscription and cannot create an independent lifecycle group. Choose a different actual name.

Question 183

Subscription sub-app already contains resource group rg-portfolio. A team proposes creating rg-orders as a child resource group *inside* rg-portfolio so that rg-orders has a separate lifecycle but automatically inherits only the parent resource group's Reader assignment and CanNotDelete lock. Which statement about this design is accurate?

  1. Create rg-orders as a nested child of rg-portfolio; all resource-group management locks automatically inherit to the child group but not its resources.
  2. Apply a tag ParentResourceGroup=rg-portfolio to rg-orders; Azure Resource Manager then implements parent-child RBAC and lock inheritance between these groups.
  3. Resource groups are not nested Azure management scopes. Create rg-orders as a separate group under the subscription and use supported common ancestor scope or separate assignments for shared governance.
  4. Create rg-orders in a different Azure region; Azure treats resource groups in different regions as child groups of the first group with the matching subscription.

Explanation

Correct Answer

C:

Azure Resource Manager organizes scopes as management group, subscription, resource group and resource. Sibling resource groups under the same subscription are independent lifecycle containers; one resource group cannot nest inside another. Governance intended to cover both must be assigned at a permitted shared ancestor such as the subscription (which may also affect other groups) or explicitly on each group according to the policy boundary.

Incorrect Answers

A:

Azure resource groups are direct containers in a subscription, not containers for other resource groups. A parent-child resource-group scope is not supported, so the proposed RG-to-RG inheritance of locks or Reader grants cannot be created. The group and its resources can inherit access from higher scopes such as a subscription, but that is a different hierarchy.

B:

Azure resource tags are labels and do not create parent-child Azure Resource Manager scopes, RBAC inheritance, or lock inheritance between resource groups. Assigning ParentResourceGroup metadata to an RG might help external reporting but does not grant its members the parent group's protections. Use actual supported hierarchy scopes and explicit assignments.

D:

The location selected for a resource group defines where its management metadata is stored, not its place in a hierarchy. Changing a group's location does not establish child membership in another resource group, and sibling groups can exist with different locations. The team must model shared RBAC and management locks using genuine supported scopes.

Question 184

An auditor asks which Azure Resource Manager operations changed resources in rg-finance during the last seven days. Where should the administrator begin?

  1. Query the Azure Activity Log scoped to rg-finance, then inspect relevant resource diagnostic logs if needed.
  2. Review only current VM CPU metrics.
  3. Inspect only the resource group's tags.
  4. Assign subscription Owner to the auditor and ask them to remember changes.

Explanation

Correct Answer

A:

Azure Activity Log records subscription-level control-plane events such as resource creation, update, deletion, and administrative operations. Filtering it by the specific resource group and time range gives the auditor the starting evidence for ARM management changes. Resource diagnostic settings and service logs may be needed for deeper data-plane or application activity, which is not the same as Activity Log history. Preserve appropriate retention and access permissions before treating the resulting events as a complete audit trail.

Incorrect Answers

B:

CPU metrics track runtime workload behavior, not which Azure Resource Manager operations changed the resource group. A VM can have high CPU without any management change and can be updated while idle. Use Activity Log for control-plane audit events and follow with resource-specific diagnostics when necessary.

C:

Tags describe resource metadata and may identify a business owner, but they do not record a chronological log of ARM operations. The auditor needs evidence of who performed management actions and when. Azure Activity Log, filtered to the group and time window, is the appropriate initial data source.

D:

Subscription Owner would expose broad administrative rights without generating better historical evidence. Audit requests should use recorded platform events, not memory or unnecessarily powerful role grants. Give the auditor suitable read permissions and inspect the scoped Azure Activity Log for the requested period.

Question 185

A resource migration to a new Azure resource group fails validation because the service's resource type does not support that move scenario. What is the appropriate next step?

  1. Assign Owner to the migration identity and assume all resource types become movable.
  2. Check the service's published move limitations and dependencies, then plan a supported redeployment or migration alternative.
  3. Ignore validation and force the move by editing the resource ID string.
  4. Delete the original resource before taking any backup.

Explanation

Correct Answer

B:

Azure Resource Manager move support varies by resource provider and resource type, so a failed validation result can indicate an unsupported source, target, or dependency combination. The team should inspect the provider's documented move restrictions and the exact validation error before attempting anything further. If direct movement is not supported, plan an approved migration or redeployment method that preserves necessary data, identity references, network connectivity, and access assignments. Retrying the identical unsupported move repeatedly will not change the service capability.

Incorrect Answers

A:

Missing RBAC permissions can cause some move failures, but the scenario explicitly identifies an unsupported resource-type move. Owner does not change the technical capabilities of the resource provider or bypass service dependency requirements. The team needs a supported alternative rather than broad role escalation.

C:

Azure resource IDs are managed identifiers, not editable fields that force a resource provider to accept unsupported moves. Changing a local string or template reference does not transfer the underlying service resource. The correct response is to follow documented move support or design a supported migration path.

D:

Deleting the source before planning a supported migration could destroy data or interrupt services, especially when the direct move is unavailable. The engineer must assess backup, replication, configuration reconstruction, and cutover requirements first. Unsupported moves call for careful migration planning, not destructive shortcuts.

Question 186

A deployment identity has Contributor only on rg-existing. Its new IaC process must create future resource groups, but security will not allow broad subscription resource-management privileges. What permission should be delegated?

  1. Reassign Contributor on rg-existing with a second entry.
  2. A custom role with Microsoft.Resources/subscriptions/resourceGroups/write at subscription scope, where authorized.
  3. Assign Storage Blob Data Contributor to the identity at subscription scope.
  4. Set an Azure Policy audit assignment on rg-existing.

Explanation

Correct Answer

B:

Creating a resource group is an ARM operation on the subscription-level resourceGroups collection. A narrowly defined custom role can include the required Microsoft.Resources/subscriptions/resourceGroups/write operation at an authorized subscription scope rather than broad subscription Contributor. Review the entire custom role for other required read/list permissions and its assignable scopes before assigning it. This addresses creation of new groups without changing the existing resource-group-scoped Contributor role or granting unrelated write privileges.

Incorrect Answers

A:

Role assignments do not become more powerful by being duplicated at an unchanged scope. The deployment identity would still lack permission to create a sibling resource group above rg-existing in the subscription hierarchy. The missing operation needs subscription-scope authorization or a pre-created destination, not a repeated child-scope grant.

C:

Blob Data Contributor grants storage blob data operations and is unrelated to creating Azure resource groups through the Microsoft.Resources provider. It would broaden data access without providing the required resourceGroups/write control-plane action. Delegate the specific ARM resource-group creation permission through a suitable scoped role.

D:

Audit-effect policy reports evaluation results and does not create a new role grant or enable subscription-scope resource-group creation. The identity is missing an ARM authorization action, not a compliance report. Address the custom-role permission at the scope where new resource groups are created.

Question 187

Two departments share one Microsoft Entra tenant but need separate Azure billing, resource-management, and RBAC boundaries. Which organization design best supports the separation?

  1. Grant both departments Owner on the shared subscription.
  2. Put all workloads into a single resource group with different VM tags.
  3. Use separate Azure subscriptions and place them under suitable management groups for shared governance.
  4. Create two different Azure regions but keep all resources under one subscription.

Explanation

Correct Answer

C:

Azure subscriptions provide independent resource and cost management boundaries while remaining associated with the same Microsoft Entra tenant for identity. Separate departmental subscriptions can have their own budgets, resource policies, quotas, and Azure RBAC assignments without requiring separate identity tenants. Management groups can apply common governance across both when authorized, but inherited grants should be reviewed carefully. This creates explicit operational and financial boundaries instead of trying to separate all department spending only through resource group names or tags.

Incorrect Answers

A:

Giving each department Owner on one shared subscription allows broad resource management and role delegation across the other's resources. It undermines the requested boundaries. Distinct subscriptions with correctly scoped roles and optional parent management-group policy inheritance provide more defensible separation.

B:

One resource group is too narrow to provide independent subscription-level billing and quota boundaries for two departments. Tags can assist cost allocation but do not create separate subscription ownership or governance limits. Separate subscriptions within the existing tenant better match the specified financial and management separation requirements.

D:

Regions define workload placement, not subscription-level billing or authorization boundaries. Resources in multiple regions can still share one subscription's management roles, quotas, and cost ownership. The departments need independent subscription contexts, so distributing VMs geographically does not solve their organizational separation.

Question 188

An Azure subscription Owner has approval to move subscription sub-dev from Microsoft Entra tenant A to tenant B using Change directory. The destination tenant permits incoming transfers, the destination administrator is available to accept, and all other transfer prerequisites have been reviewed. However, tenant A has a subscription policy configured to disallow subscriptions from leaving its directory, and the request is blocked. What administrative action addresses this specific policy block?

  1. Assign Reader at the subscription scope to every member of tenant B; this overrides the source tenant transfer policy.
  2. Remove the resource group CanNotDelete locks; these locks are the setting that authorizes directory transfers.
  3. Move sub-dev from a Production to a Test management group in tenant A; management-group hierarchy changes bypass tenant transfer policy.
  4. Ask an authorized directly assigned Global Administrator of tenant A to approve and configure the applicable outgoing subscription-transfer policy or allowed exemption, then complete the authorized change-directory workflow.

Explanation

Correct Answer

D:

Microsoft documents independent policies controlling subscriptions entering and leaving a Microsoft Entra directory. An outgoing deny in tenant A blocks the approved transfer even when the subscription Owner and destination acceptor are ready. The directly assigned Global Administrator responsible for tenant A must approve any permitted change or exemption using the supported subscription policy controls, after which the two-party Change directory workflow can continue. This is different from changing management-group placement inside one tenant.

Incorrect Answers

A:

Reader is a read-only Azure resource management role. Granting it to principals does not modify Microsoft Entra directory-level subscription transfer policies. The reported failure is a source tenant outgoing-transfer deny, not lack of permission to inspect Azure resources in the destination directory.

B:

CanNotDelete locks govern supported Azure resource management deletion operations. They do not authorize a subscription to leave one Microsoft Entra directory for another. The source tenant subscription transfer policy must be changed by authorized directory governance before the approved request can proceed.

C:

Changing a subscription's parent management group affects inherited Azure Policy and RBAC within its current tenant hierarchy. It does not override the independent policy that blocks moving subscriptions out of the Microsoft Entra directory. The scenario requires an outgoing tenant-transfer policy authorization, not a management-group reparent operation.

Question 189

A team has Contributor on a subscription but cannot create resources after the subscription enters a spending-restricted or disabled state. Which issue should be checked first?

  1. Apply a CanNotDelete lock to the subscription.
  2. Change the virtual network's DNS servers.
  3. Assign another Contributor role on the resource group.
  4. The subscription's billing offer, state, spending limit, and authorization to restore service.

Explanation

Correct Answer

D:

Azure RBAC Contributor describes permitted resource-management actions, but those rights do not override a subscription that is disabled or restricted by billing conditions. The administrator should inspect subscription state and offer details, including applicable spending limits or payment issues, and follow the provider's supported reactivation process. An additional Contributor or Owner assignment will not by itself restore resources if the subscription is not active for deployment. Separate the billing control from access-control failures before changing roles.

Incorrect Answers

A:

A deletion lock restricts selected Azure Resource Manager operations and would not pay an outstanding balance or lift an offer's spending limit. It may make management more restrictive. The team needs billing or subscription-state remediation through the supported administrative workflow, not an unrelated management lock.

B:

VNet DNS configuration affects name resolution for connected workloads; it does not determine whether the Azure subscription can provision new resources under a spending restriction. Adjusting DNS cannot remove a billing hold. Inspect the subscription offer and state to identify the actual platform limitation.

C:

Repeating a role grant does not change the subscription's billing state, payment status, or spending limit. The principal already has suitable resource permissions, but the platform is preventing new usage for a different reason. Investigate billing and subscription reactivation rather than adding redundant Azure RBAC assignments.

Question 190

A company's Azure subscription is being transferred to a new billing owner, while existing resource operators should keep appropriate management rights where supported. Which process is required?

  1. Follow the supported Azure billing ownership transfer workflow and separately verify Azure RBAC access afterward.
  2. Assign the new billing owner Reader on the subscription.
  3. Add the new billing owner to an Entra security group with Resource Group Contributor.
  4. Rename the subscription to the new owner's company name.

Explanation

Correct Answer

A:

Billing ownership determines who is financially responsible for an Azure subscription and may be managed through billing accounts and offer-specific transfer workflows. Changing an Azure RBAC Owner assignment does not automatically transfer the billing relationship. The organization must use the supported subscription or billing transfer process, check eligibility and tenant consequences, and review role assignments after the transfer. Azure resource permissions and financial ownership are related but distinct administrative concerns that should not be conflated.

Incorrect Answers

B:

Reader permits viewing Azure resource configuration but does not transfer billing accountability or payment ownership. The subscription would remain attached to its previous billing arrangement unless the supported financial transfer process is completed. Use the billing ownership workflow rather than treating Azure resource read rights as financial ownership.

C:

A resource-group Contributor assignment controls resource operations in the selected group, not the subscription's billing ownership. Even a broader RBAC role would not substitute for an offer-specific account transfer. The organization must address billing directly and then verify the resulting Azure management access.

D:

A subscription display name is presentation metadata and is not the legal or technical billing ownership relationship. Renaming the subscription does not change payment responsibility or account linkage. Complete the supported transfer process and separately review management roles and identity requirements.