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 21

Question 200

A company must open a ticket whenever an Azure subscription budget crosses an actual-cost threshold. A manual email is insufficient. What integration should be evaluated?

  1. Enable a Virtual Machine Scale Set autoscale rule for the subscription's financial threshold.
  2. Create an Azure Policy deny assignment that blocks resource deployment whenever a ticket is missing.
  3. Export an Azure Cost Analysis CSV every year and import it into the ticketing tool.
  4. Attach a supported Action Group to the budget notification and route it to an approved ticketing workflow.

Explanation

Correct Answer

D:

Cost Management budgets can integrate with Azure Monitor action groups for supported automated notifications and actions. Configure the actual-spend threshold, select the action group, and connect its supported mechanism, such as a webhook or Logic App, to the ticketing system. Verify permissions and payload handling in the workflow. The budget still detects cost thresholds rather than performing ticket creation itself; the action group and integration supply the missing automated response.

Incorrect Answers

A:

Autoscale rules react to supported performance or schedule signals for a particular scalable resource, not the aggregated subscription budget event described here. Increasing or reducing VM instances is a different operational response from filing a ticket. Configure budget notification with an action group that invokes the ticket workflow.

B:

A policy deny effect evaluates resource requests against policy rules, not the Cost Management budget threshold event. It cannot replace the budget's spend comparison and ticket integration. Such a policy could also block unrelated deployments without generating the desired incident record. Use the budget notification workflow to create tickets.

C:

An annual CSV export is too infrequent to act when a monthly cost threshold is crossed. A report also requires another process to detect and dispatch the event, defeating the requested automated notification. Budget thresholds and a supported action group provide the event-driven mechanism.

Question 201

Operations suspects that several Azure VMs are consistently underutilized, but an application owner must verify performance before any resizing. Which Azure feature should the team review first?

  1. Azure Policy compliance results for allowed deployment regions only.
  2. Azure Advisor cost recommendations for VM right-sizing opportunities.
  3. An Azure Backup retention policy with fewer recovery points.
  4. A new Network Security Group that blocks outbound web requests.

Explanation

Correct Answer

B:

Azure Advisor examines available resource usage and configuration signals to suggest cost optimizations, including potential right-sizing of underutilized virtual machines. Review each recommendation with workload owners, compare observed performance and required capacity, then schedule a validated size change rather than blindly applying it. Advisor identifies candidate savings; it does not guarantee that a smaller SKU will satisfy every workload or that a recommendation should automatically be implemented.

Incorrect Answers

A:

A location policy can report or enforce where resources are deployed, not identify machines that are overprovisioned for their actual workloads. Although policy governance matters, it does not replace utilization-based cost guidance. Azure Advisor is the better discovery source for VM right-sizing candidates.

C:

Backup retention settings concern recoverability and storage use, not whether the running VM's CPU and memory capacity are excessive. Arbitrarily reducing retention may violate recovery requirements without fixing overprovisioned compute. Start with utilization-driven Azure Advisor recommendations and validate any proposed compute-size changes.

D:

Network Security Groups enforce traffic filtering and do not assess whether a VM SKU is larger than the workload requires. Blocking outbound connections could degrade the application while leaving compute charges unchanged. Use Advisor's cost optimization findings to evaluate suitable right-sizing opportunities instead.

Question 202

An Azure administrator creates a monthly Cost Management budget and promises management it will fire exactly when a transaction causes the cost to exceed a threshold, within seconds. What is the correct expectation?

  1. Budget alerts are emitted synchronously with each billable Azure API request.
  2. Budget evaluations depend on processed cost data and are not a real-time transaction control.
  3. Creating a ReadOnly resource lock converts Cost Management data to real-time usage events.
  4. Adding more email recipients makes the budget evaluator run every second.

Explanation

Correct Answer

B:

Cost Management budget notifications are based on cost data processing and scheduled evaluation rather than every new charge being applied instantly. Usage ingestion, calculation, and forecasting introduce delays before a threshold becomes visible. Communicate that budget alerts are financial monitoring signals, not a guaranteed per-second metering or spend cutoff mechanism. If precise operational controls are required, use separate limits and automation while retaining budget tracking for aggregated costs.

Incorrect Answers

A:

The Cost Management budget service does not block or intercept each charge-generating operation as a synchronous transaction processor. Cost data becomes available after ingestion and calculation. Claiming an immediate event on every API request would overstate both the timing guarantee and the enforcement role of a budget.

C:

Resource locks act on Azure Resource Manager control-plane operations. They neither accelerate usage ingestion nor change Cost Management budget evaluation frequency. A lock can prevent certain management actions but is unrelated to the timing of cost notifications. Treat the budget as delayed financial monitoring.

D:

Recipient lists control where threshold notifications go, not how often Azure calculates, imports, or evaluates cost information. More recipients do not remove billing-data latency. The administrator should communicate the service's evaluation characteristics rather than configure a larger distribution list as a timing fix.

Question 203

A project resource group routinely exceeds its allocated budget even though the containing Azure subscription remains under its total budget. The project manager wants a warning specific to this group. What should be configured?

  1. Increase the subscription-level budget until the project is no longer reported as over budget.
  2. A Cost Management budget scoped to that resource group, or an equivalent supported cost filter.
  3. Use a VM CPU metric alert on the largest machine in the group.
  4. Add a CanNotDelete lock to the project resource group.

Explanation

Correct Answer

B:

Cost Management budgets can be scoped and filtered to isolate cost responsibilities rather than tracking only the aggregate subscription. Configure the budget for the project resource group, confirm supported scope and filters, and set its own threshold and recipients. Then the project can trigger an alert independently of whether total subscription spending is acceptable. The organization's broader subscription budget should remain separate because it answers a different financial question.

Incorrect Answers

A:

Raising the entire subscription budget changes the comparison for all resources, but it does not create a specific cost limit or alert for the project resource group. It may also mask an overrun by one team. Define the budget at the intended cost boundary instead of diluting a broader threshold.

C:

CPU utilization of one machine is not a measure of combined charges for disks, network transfer, databases, and all other project resources. The project could exceed its budget while that VM remains idle. Cost Management provides the appropriate aggregated cost scope and threshold.

D:

A deletion lock protects resources from certain management deletion operations; it does not aggregate usage charges or emit spending alerts for that resource group. The desired behavior is financial monitoring, not deletion prevention. Set a resource-group-scoped budget and appropriate notification instead.

Question 204

Subscription spending increases despite a stable VM count. Finance suspects retained unattached managed disks and additional reserved capacity charges. Which investigation is most appropriate?

  1. Compare only the number of running VMs and disregard storage charges.
  2. Disable subscription budget alerts so that cost reports stop increasing.
  3. Delete every disk not currently attached to a VM before reviewing its contents.
  4. Use Azure Cost Analysis to group spending by service/resource and correlate it with Advisor findings and billing records.

Explanation

Correct Answer

D:

Cost Analysis exposes Azure charge breakdowns by supported dimensions such as service, resource and time. Inspect storage, disk, and compute charge lines instead of assuming VM quantity alone explains spending, and cross-check recommendations or cost details for orphaned disks and reservation-related charges. Advisor can identify optimization candidates, but the bill and cost breakdown establish what is actually charged. This evidence-led approach distinguishes retained resources from accounting differences before deletion or purchases are considered.

Incorrect Answers

A:

Azure bills for resource families beyond active VM compute, including allocated managed disks and other retained services. A constant VM count therefore cannot establish constant spending. The scenario already names other possible charge sources. Use Cost Analysis groupings and detailed billing data to investigate those components.

B:

Budget alerts communicate spend thresholds; disabling them does not change charges from disks, reservations, or any deployed service. It would remove an important warning without addressing the underlying billing change. The correct next action is to investigate charge composition using Cost Analysis.

C:

An unattached managed disk may hold deliberate retention, migration, disaster-recovery, or forensic data. Blind deletion risks data loss and may not explain unrelated reserved-capacity charges. First inspect billed resource categories, ownership, recovery requirements, and Advisor suggestions. Only retire unused disks through an approved lifecycle process.

Question 205

An Azure subscription under a Microsoft Customer Agreement (MCA) has resource group rg-delta tagged Project=Delta. Its VMs have no resource-level Project tag, and Cost Analysis currently cannot group their usage under Project=Delta. Finance wants to filter a new Cost Management budget by the inherited Project value without writing tags to every VM. Which action addresses this cost-data issue?

  1. Add a CanNotDelete management lock to rg-delta so the cost records inherit Project=Delta.
  2. Enable Cost Management tag inheritance for the eligible subscription using resource-group tags, allow the usage-record refresh, and then configure the Project=Delta budget filter.
  3. Create an Azure Monitor metric alert on virtual-machine CPU and use its tag field to rewrite historical billing records.
  4. Assign subscription Reader to every VM managed identity so Cost Management automatically copies its resource-group tag into each resource.

Explanation

Correct Answer

B:

For eligible MCA scopes, Cost Management tag inheritance can apply resource-group or subscription tags to child resource usage records without changing the underlying Azure resources. Enable the appropriate inherited-tag setting, allow the documented usage-data refresh (typically 8–24 hours), and make a budget filtered on Project=Delta when those inherited tags are available. This differs from merely creating another actual-spend percentage alert.

Incorrect Answers

A:

Management locks limit management-plane delete or write operations; they do not cause resource group tags to appear on Cost Management usage records. The missing Project dimension is a billing-data classification issue, not a resource-deletion risk.

C:

A VM CPU metric alert uses performance telemetry and cannot populate billing usage records with inherited tags or rewrite prior-month charges. Azure Cost Management handles cost allocation metadata independently of VM metrics.

D:

Subscription Reader permits management-plane viewing; granting it to workload identities neither copies resource-group tags nor changes the MCA billing scope’s tag inheritance configuration. The explicit Cost Management setting controls inherited usage tags.

Question 206

A finance analyst sees a sharp one-day change in reported Azure costs following a commitment purchase. Which comparison best avoids misleading conclusions about steady service consumption?

  1. Set a higher budget until both reporting views display the same figure.
  2. Compare actual cost with amortized cost views where supported and inspect commitment charges separately.
  3. Hide reservation and savings-plan items entirely from the cost report.
  4. Use only actual cost on the purchase day and attribute the entire amount to one VM's increased CPU.

Explanation

Correct Answer

B:

Actual cost and amortized cost views can present reservation or savings-plan purchases and their allocated benefits differently. Inspect both where supported to distinguish a payment or commitment accounting event from changes in underlying resource usage. This avoids treating a single purchase date as proof that workloads suddenly grew. Reconcile the view with the billing arrangement and eligible benefit allocation before drawing trend or right-sizing conclusions.

Incorrect Answers

A:

Changing a budget threshold alters alerts and comparisons but does not change how actual or amortized costs are calculated. The two perspectives intentionally answer different accounting questions. Reconcile their components rather than attempting to force equality by editing the budget amount.

C:

Excluding commitment costs may make a chart appear smoother but conceals genuine spending and prevents reconciling allocation against invoices. The goal is to understand cost accounting, not remove inconvenient transactions. Compare supported cost views and distinguish commitments from resource consumption transparently.

D:

A commitment purchase is a financial transaction, not proof of a particular VM suddenly consuming additional processor capacity. Actual-cost views may show purchase treatment that differs from amortized allocation. Review both cost perspectives and item categories before claiming a workload utilization spike.

Question 207

A business unit owns six Azure subscriptions. Security wants one place to apply a common subscription-level Azure Policy and baseline RBAC inheritance without duplicating configuration in each subscription. What hierarchy should be created?

  1. Make one shared storage account the parent of the subscriptions.
  2. Create a resource group above the six subscriptions.
  3. Create a management group for the business unit and place the six subscriptions beneath it.
  4. Create a virtual network and peer all subscription networks together.

Explanation

Correct Answer

C:

Azure management groups organize subscriptions beneath a governance hierarchy. Appropriate Azure Policy assignments and RBAC grants at the management group can flow down to the associated subscriptions and their contained resources according to the relevant scope and rules. This provides a single logical unit for business-level governance without creating duplicate subscription policies. Confirm the business unit's management group parent and inherited controls before associating production subscriptions.

Incorrect Answers

A:

Storage accounts are resources inside subscriptions, not top-level organizational containers. Their permissions and settings cannot become the administrative parent of unrelated subscriptions. Azure management groups are designed for cross-subscription organization and inherited governance, so the shared storage approach targets the wrong resource hierarchy.

B:

Azure resource groups live within subscriptions and contain resources, not sibling subscriptions. They cannot serve as a governance parent for multiple Azure subscriptions. Management groups are the hierarchy construct used to apply policy and role assignments over several subscriptions. This cannot be corrected by changing the resource group's region or display name.

D:

VNet peering connects network address spaces under supported conditions, not subscription governance or shared RBAC and policy inheritance. It would change network connectivity but does not provide a parent scope for the six subscriptions. Use an Azure management group hierarchy.

Question 208

A subscription is moved into a management group where an assigned policy denies public network access on new storage accounts. A deployment that worked yesterday now fails. What should be investigated first?

  1. Check the inherited management-group policy assignment and its effective deny conditions for the deployment.
  2. Grant Owner to the deployment identity on the subscription.
  3. Recreate the storage account with the same settings in another resource group under that subscription.
  4. Enable a Delete management lock on the new storage account.

Explanation

Correct Answer

A:

Azure Policy assignments at management-group scope can affect subscriptions placed beneath that group. Moving the subscription can therefore change the set of effective policies, and a deny effect may reject a previously permitted deployment. Inspect the inherited assignment, applicable parameters, policy evaluation and any approved exclusions before changing the resource request. The failure is a governance scope change, not automatic proof of missing ARM Contributor permission.

Incorrect Answers

B:

Owner is a broad Azure RBAC privilege but does not by itself bypass a deny-effect Azure Policy. Increasing role permissions could create unnecessary administrative exposure while the policy still rejects the storage configuration. Investigate inherited policy evaluation after the subscription hierarchy change.

C:

A management-group policy can govern all relevant resources in every descendant resource group of the subscription. Changing the local resource group does not inherently evade the ancestor assignment. Confirm policy scope, valid exemptions and the configuration requirement instead of assuming a resource-group move solves it.

D:

A Delete lock concerns protection from resource deletion, while this deployment fails because of a deny rule on public network exposure. The account may not even exist yet to lock. The inherited Azure Policy assignment is the appropriate source of the deployment error.

Question 209

An auditing team has Reader at management group mg-corp. A newly created Azure subscription is placed below mg-corp and should have the same read-only oversight. Which statement is correct?

  1. The new subscription has no inherited Reader rights until an individual assignment is copied to every VM.
  2. The Reader role converts to Owner for all new subscriptions in the hierarchy.
  3. The inherited grant applies only to resources physically located in the same Azure region as mg-corp.
  4. The ancestor Reader assignment is inherited by the new subscription through management-group scope.

Explanation

Correct Answer

D:

Azure RBAC assignments at management-group scope apply to eligible descendant subscriptions and resources. After the new subscription is associated with mg-corp, its effective Reader permissions should include the inherited management-group grant. Confirm the hierarchy and the principal's effective assignments rather than manually copying redundant grants. This inherited scope is the design advantage of assigning the appropriate baseline role at a common ancestor.

Incorrect Answers

A:

Management-group RBAC inheritance applies down the governance hierarchy; it is not restricted to preexisting subscriptions or manually copied VM-level grants. The team should verify effective access, but a new subscription placed under the existing ancestor assignment need not automatically receive hundreds of duplicate role assignments.

B:

Role inheritance preserves the assignment's defined permissions and does not elevate Reader into Owner. Read-only visibility remains separate from management write or role-assignment authority. The auditing team should not gain broad mutation rights simply because a new subscription was added beneath mg-corp.

C:

A management group organizes subscriptions as a control-plane governance hierarchy, not as a regional deployment location. Its inherited RBAC scope is not limited by the geographic region of workloads in the descendant subscription. Verify the ancestor/subscription relationship instead of changing resource regions.

Question 210

A management group named mg-legacy still contains subscription sub-lab and child management group mg-archive. Governance has approved retiring mg-legacy; both child scopes must remain managed under mg-current without deleting their subscriptions or resources. An attempted deletion of mg-legacy is blocked. What is the required sequence?

  1. With the necessary hierarchy permissions, move sub-lab and mg-archive to approved parent management groups, confirm mg-legacy has no children, and then delete mg-legacy.
  2. Delete mg-legacy first; Azure automatically deletes its child subscriptions but retains their VMs in the tenant root.
  3. Remove only the policy assignments from mg-legacy; management groups with child subscriptions can then be deleted without moving the children.
  4. Change mg-legacy's display name to mg-current; this empties the former management group and removes the original group ID automatically.

Explanation

Correct Answer

A:

Azure cannot delete a management group while child subscriptions or management groups remain. Authorized administrators must move those child scopes to their approved parents, account for inherited governance and hierarchy permissions, verify the target group is empty, and only then delete mg-legacy. This preserves the child resources and tests deletion prerequisites, not initiative assignment.

Incorrect Answers

B:

Deleting a management group with children is blocked; the platform does not silently delete subscriptions or relocate their VMs as a consequence of a management-group delete. Moving the children first is required.

C:

Removing policy assignments changes governance, not the hierarchy. The remaining child management group and subscription still prevent deleting mg-legacy even if its policies have all been unassigned.

D:

The display name is not the same as management-group identity or child membership. Renaming does not move sub-lab or mg-archive or meet the empty-group precondition for deletion.