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 57

Question 560

A CPU-bound job is currently a single Azure Container Instance, and increasing its CPU capacity is supported. Which next step is directly applicable?

  1. Enable VMSS autoscale settings on the ACI resource itself.
  2. Increase the container group’s CPU allocation within ACI limits, or redesign to an autoscaling service if horizontal elasticity is required.
  3. Change the registry image tag without updating resource requests.
  4. Enable Azure Files soft delete to add CPU cores to the container.

Explanation

Correct Answer

B:

ACI resource requests determine the container group’s CPU capacity; a new configuration/deployment may be needed for more resources.

Incorrect Answers

A:

Standalone ACI does not directly inherit VM Scale Set autoscale policy.

C:

Retagging an image does not increase allocated runtime CPU capacity.

D:

Storage recovery settings cannot increase available compute cores.

Question 561

Container App orders-api is in multiple-revision mode. The team updated its HTTP concurrency scale threshold and deployed the change, creating revision r2. Revision r1 is still active and continues to use its former threshold. An operator expects r1 to pick up the changed rule automatically. Which explanation is correct?

  1. The HTTP scaling rule is an application-wide secret, so update the secret to change every active revision.
  2. Scaling rules are revision-scoped; deploy and activate a new revision with the desired rule, and manage traffic away from r1 when appropriate.
  3. Increase CPU on the existing revision using in-place vertical scaling without creating a new revision.
  4. Disable HTTP ingress globally because it is the only supported method of applying scale settings to an old revision.

Explanation

Correct Answer

B:

Azure Container Apps revisions are immutable snapshots of revision-scoped settings. The scale configuration belongs to that scope, so changing an HTTP concurrency threshold produces a new revision rather than rewriting r1. In multiple-revision mode, r1 can remain active with its original rules while r2 has the new threshold. Operations should direct traffic to a suitable new revision, validate scaling and then deactivate the old revision when safe. There is no mechanism to mutate r1 in place.

Incorrect Answers

A:

Container Apps secrets are application-scoped configuration, but scale rules live in the revision template. Changing a secret value does not update the scale rule embedded in an immutable revision. The operator must distinguish globally applied configuration from properties that trigger a new revision.

C:

Vertical scaling of an existing container app revision is not the supported way to apply a new HTTP scale rule. Moreover, Azure Container Apps documents that revision-level changes produce new revision snapshots, and vertical scaling is not supported as a live replacement for that lifecycle. CPU sizing and concurrency-based replica scaling solve different decisions.

D:

Ingress configuration is application-scoped, and disabling ingress would prevent the intended HTTP API traffic instead of applying r2 rules to r1. It would also remove the HTTP traffic signal used for supported concurrency-based autoscaling. Retain the required ingress path and manage revision activation and traffic explicitly.

Question 562

A Container Apps revision has desired capacity of eight replicas but only five are currently ready. What should be checked first?

  1. Assume scale targets guarantee immediate readiness and ignore failures.
  2. Delete all deployment revisions with fewer replicas than desired.
  3. Inspect replica readiness, quota/capacity, scale rule conditions and revision diagnostics.
  4. Remove the private DNS zone for the app to force instant scale-out.

Explanation

Correct Answer

C:

Capacity, readiness, quota and scaler inputs explain why active healthy replicas may lag the desired amount.

Incorrect Answers

A:

Desired replica count is a scaling objective, not proof that every replica has provisioned and passed readiness.

B:

Deleting healthy partial capacity risks reducing service availability before diagnosing the shortfall.

D:

DNS deletion is unrelated to workload scheduler capacity and can disrupt access.

Question 563

A Container Apps team requires more memory per replica. It expects an in-place vertical resize of all running replicas with guaranteed zero interruption. What is the accurate deployment plan?

  1. Change a static DNS record to grow each running container’s RAM instantly.
  2. Increase maximum replicas and assume that doubles memory available to each individual process.
  3. Edit the registry image name without changing revision template resource requests.
  4. Update the revision-scoped CPU/memory template and coordinate a new revision rollout with readiness/traffic planning.

Explanation

Correct Answer

D:

Container Apps resource request changes create a revised deployment; continuity needs controlled revision rollout rather than instant in-place resize.

Incorrect Answers

A:

DNS does not govern container resource requests.

B:

More replicas increase aggregate capacity but do not increase memory assigned to one instance.

C:

Changing an image reference alone does not apply a larger CPU/memory allocation.

Question 564

A Windows ASP.NET application must be hosted in Azure App Service with predictable dedicated compute capacity. Which hosting plan matches its OS requirement?

  1. Create only a Linux App Service plan and assume a Windows app can share its workers.
  2. Run the app as Azure Container Instances with no App Service plan.
  3. Choose a free App Service tier even though dedicated CPU/memory has been stipulated.
  4. Create a Windows App Service plan in the required region with suitable supported tier and capacity.

Explanation

Correct Answer

D:

Windows App Service plans supply the compatible Windows runtime hosting and worker tier sizing needed here.

Incorrect Answers

A:

App Service worker plans have OS compatibility; a Windows code app does not simply run on Linux workers.

B:

Container Instances is another hosting product and does not create an App Service plan for this app.

C:

Free/shared tiers do not provide the stipulated dedicated worker capacity.

Question 565

A .NET Linux app must run on the same App Service plan as two existing Linux apps in a compatible region. What is the required compatibility check?

  1. Choose a Windows-only App Service plan and assume the OS type automatically converts.
  2. Assign VM Reader to the app identity to make the plan compatible.
  3. Use a compatible Linux App Service plan with supported runtime and region, accounting for its shared worker capacity.
  4. Move the app to a managed disk without hosting any running web process.

Explanation

Correct Answer

C:

Compatible apps on the same Linux plan share underlying compute capacity and must meet OS/region constraints.

Incorrect Answers

A:

Windows and Linux App Service plans do not share the same operating system worker pool.

B:

Azure resource visibility permissions do not change the plan operating system.

D:

A managed disk is storage rather than a web hosting plan.

Question 566

A production web app runs in an eligible Premium App Service plan and already has six named nonproduction deployment slots. Finance tries to scale the plan down to Standard without removing any slots, but the portal blocks the change. The app's CPU demand would fit Standard. What is the relevant platform constraint?

  1. The Standard tier never supports deployment slots; the app must delete all six slots before using Standard.
  2. Standard supports only five deployment slots per app; reduce the number of slots to five or fewer before downgrading, or retain a tier that supports the existing count.
  3. Set each of the six slots to 0% production traffic and Standard will allow them all because idle slots do not count toward the slot limit.
  4. Change the app's TLS minimum version from 1.2 to 1.0; that removes the App Service plan deployment-slot-count restriction.

Explanation

Correct Answer

B:

The official App Service deployment-slot guidance states that Standard supports five deployment slots, and specifically says an app with more than five cannot scale down to Standard. An existing app with six named nonproduction slots therefore exceeds the Standard tier's slot allowance even if the CPU and RAM fit. Remove a slot under change control or keep a supporting plan.

Incorrect Answers

A:

Standard supports deployment slots, but the supported number is limited. The official deployment-slot documentation specifies a limit of five slots on Standard, so requiring zero slots is unnecessarily destructive and factually wrong. Remove only the number required for the target tier or keep a higher-capacity tier.

C:

Routing zero user traffic to a slot does not remove that deployment slot resource from the app or stop it counting against plan-tier limits. A slot remains a separately addressable live app with its own hostname and configuration. Actual slot count, not current production traffic distribution, is the limitation that blocks the downgrade.

D:

TLS minimum version is an HTTPS security control and is independent of the number of deployment slots allowed by an App Service plan tier. Lowering TLS weakens transport security without changing the tier limit. The permitted administrative actions are to reduce the slot count or retain a tier with adequate slot capacity.

Question 567

Two small web apps in the SAME region and operating system can share App Service compute to reduce cost. They do not require independent scale boundaries. What should be configured?

  1. Create a separate Premium App Service plan for each app regardless of load.
  2. Host both apps in one compatible App Service plan while monitoring aggregate resource consumption.
  3. Deploy two standalone VMs and disable App Service management.
  4. Add two CNAME records, which automatically causes the apps to share workers.

Explanation

Correct Answer

B:

Apps in one App Service plan share worker instances, capacity and scaling behavior, which is efficient if compatible.

Incorrect Answers

A:

Separate Premium plans add distinct billed compute pools without matching the shared-budget requirement.

C:

Standalone VMs are unnecessary to obtain the requested App Service plan sharing.

D:

DNS aliases do not determine which Azure App Service plan hosts an app.

Question 568

A running Windows App Service web app is hosted by plan asp-old in resource group rg-web in East US. The team has provisioned compatible Windows plan asp-new in the SAME resource group and region. The app currently has regional VNet integration configured. Which action is required to move this existing app to asp-new through the supported Change App Service plan process?

  1. Disable the app's VNet integration, change to asp-new in the same resource group, region and OS type, then restore the required integration settings.
  2. Select a Linux plan in a different Azure region; App Service migrates the Windows app and all integrations automatically.
  3. Leave VNet integration enabled and change to any other plan in the subscription regardless of its resource group and webspace.
  4. Change the pricing tier of asp-old and treat that as moving the app to asp-new, without changing the app's hosting plan.

Explanation

Correct Answer

A:

App Service supports changing an existing app to a compatible plan in the same resource group, geographical region and OS type. Configured VNet integration must be disabled before the Change App Service plan operation and can be re-established on the supported target configuration afterward.

Incorrect Answers

B:

Changing a Windows app directly to a Linux App Service plan, or moving to a plan in another region, is not supported by the Change App Service plan operation. It also cannot preserve arbitrary network integration automatically.

C:

App Service plan moves are limited by resource-group, region, OS and underlying webspace compatibility; existing VNet integration must be disabled first. An arbitrary plan in the subscription does not meet these prerequisites.

D:

Scaling asp-old changes that plan's size or capacity, not the app's plan association. The requirement is to transfer the existing app to the separately created asp-new plan.

Question 569

An App Service app has saturated CPU on each worker, and profiling shows each request needs MORE CPU per worker rather than additional instances. Which change is appropriate?

  1. Scale out by increasing worker count without improving per-worker CPU size.
  2. Change only the app’s custom DNS alias.
  3. Increase an unrelated Azure Files share quota.
  4. Scale up the App Service plan to a suitable larger worker tier/size.

Explanation

Correct Answer

D:

Scaling up changes the worker size/tier to supply more resources to each instance.

Incorrect Answers

A:

Horizontal scale-out adds worker instances but does not increase CPU available to one process on one worker.

B:

DNS changes do not provide more worker CPU capacity.

C:

Storage quota changes are unrelated to compute saturation.

Question 570

An App Service Standard plan currently runs ONE worker. A load test starts now; operations must add instances immediately without upgrading the tier or setting automatic rules. What action meets the request?

  1. Manually increase the App Service plan instance count to scale out within the Standard tier.
  2. Schedule scale-in during the load test to reduce worker count.
  3. Switch to a single-instance separate plan and claim it adds capacity.
  4. Configure a new metric-based autoscale rule instead of adding capacity immediately as requested.

Explanation

Correct Answer

A:

Manual scale-out increases the number of workers on the existing eligible plan without changing its tier.

Incorrect Answers

B:

Scaling in reduces rather than adds the requested capacity.

C:

Replacing one instance with another one-instance plan does not increase the number of worker instances.

D:

Autoscale may respond after metric evaluation, but this case explicitly requires an immediate manual instance change.