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 58

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.

Question 571

A Standard-tier Azure App Service plan runs three worker instances during daytime peaks, but needs one worker overnight. Its capacity must reduce every evening and increase again each morning automatically, without changing the hosting tier. Which configuration meets the recurring time-based requirement?

  1. Scale up to a larger VM size while keeping the same three workers at every hour.
  2. Manually set the plan to three workers during the day and leave that fixed count in place overnight without autoscale.
  3. Configure plan-level Azure Monitor autoscale recurring profiles with the intended night/day instance counts and capacity limits.
  4. Upgrade the plan to a Premium tier and enable HTTP-traffic-driven automatic scaling with no scheduled profiles.

Explanation

Correct Answer

C:

Azure Monitor autoscale supports recurring time-based profiles for Standard-tier App Service plans. Configure a nighttime one-worker profile and daytime capacity profile with appropriate minimum and maximum values; the plan scales without a manual daily operation.

Incorrect Answers

A:

Scaling up changes worker compute capacity; it does not reduce the number of paid workers at the required recurring overnight time. This case requires scheduled changes to worker count, not larger instances.

B:

A permanently fixed count leaves three workers running overnight and does not provide automatic evening scale-in or morning scale-out. Manual adjustment is not a recurring schedule.

D:

App Service automatic scaling is HTTP-traffic-based and differs from plan-level scheduled autoscale; it is available on Premium v2/v3/v4, not required for this Standard-tier schedule. Upgrading solely to use a traffic-based mechanism does not implement the requested time profiles.

Question 572

An App Service plan has three existing web apps that share its worker pool. Operations proposes to increase the PLAN-level worker instance count only for one web app, without changing the other apps or relying on per-app HTTP-traffic-driven automatic scaling. What is the correct approach for independent PLAN-level worker scaling?

  1. Create or choose a compatible Linux App Service plan; don't mix OS types on one plan.
  2. Put the web app that needs an independent plan-level worker count in its own compatible App Service plan, with appropriate capacity and permissions.
  3. Use allowed autoscale/schedule or planned scale adjustments mindful of plan tier.
  4. Upgrade to an eligible App Service plan tier then configure autoscale rules.

Explanation

Correct Answer

B:

Manual scaling and Azure Monitor autoscale change the worker count of the App Service plan shared by all hosted apps. To guarantee a different PLAN-level capacity for one app while retaining independent capacity for its peers, move that app to its own compatible plan. Eligible Premium tiers also offer HTTP-traffic-driven per-app automatic scaling, but that is a separate mechanism excluded by this question.

Incorrect Answers

A:

The OS compatibility of an App Service plan determines which app runtimes may share its workers. Changing or adding a Linux plan without moving the intended workload does not isolate a plan-level scale change for that one web app.

C:

A recurring Azure Monitor autoscale profile still changes the shared App Service plan capacity for all apps on its workers. Scheduling that profile does not give only one of the existing apps a distinct independent plan-level worker pool.

D:

Upgrading the shared plan and enabling CPU-based Azure Monitor autoscale provides more scaling capability, but its resulting worker count still applies to the plan hosting all three apps. It does not meet the requirement to scale only one app at the PLAN level.

Question 573

An App Service Basic plan has only manual scale-out. The owner requires automatic increase/decrease of workers based on CPU without operator action. Which change is needed?

  1. Keep Basic and assume an Azure Monitor alert email automatically scales the app.
  2. Manually increase the Basic plan’s instance count each time a CPU alert fires.
  3. Change only the DNS name to increase app capacity automatically.
  4. Upgrade to an autoscale-capable tier such as Standard, then configure metric-based Azure Monitor autoscale rules.

Explanation

Correct Answer

D:

Azure Monitor CPU-metric autoscale requires an eligible App Service plan on Standard or higher, whereas Basic supports manual worker scale-out without an unattended CPU-rule autoscale profile. Upgrade the plan and configure metric thresholds, minimum/maximum worker counts and scale-in/out rules on the plan. Do not confuse this with Premium traffic-driven automatic scaling, which does not use CPU metric rules.

Incorrect Answers

A:

An alert alone does not execute an automatic plan-scaling action on Basic.

B:

Manual instance adjustments contradict the unattended metric-based requirement.

C:

DNS names are unrelated to VM worker count and autoscale plan support.

Question 574

A developer has source code and wants continuous deployment into a web app. What is the most appropriate next administrative decision?

  1. Configure App Service settings/Key Vault references and managed identity as appropriate.
  2. Deploy to an App Service deployment slot supported by the hosting tier.
  3. Configure App Service deployment integration and authorized build/deploy pipeline.
  4. Choose the appropriate App Service runtime stack and compatible plan OS.

Explanation

Correct Answer

C:

App Service continuous deployment integrates the web app with an authorized source repository or CI/CD pipeline that builds and deploys changes. Configure the source, branch, identity and build/deployment actions, and validate that a controlled commit reaches the intended app or slot. Runtime stack and app settings are prerequisites where applicable, not themselves a deployment pipeline.

Incorrect Answers

A:

App settings and Key Vault references configure runtime values and protect secrets for a deployed app. They do not automatically build source code, run tests or release each commit. Connect the application to supported continuous deployment with an authorized repository/build pipeline and deployment target.

B:

Deployment slots provide an isolated target for staging and swapping application releases; creating a slot does not connect a source repository or trigger builds on commits. To implement continuous deployment, configure Deployment Center or an authorized pipeline to deploy changes to the intended app or slot.

D:

Choosing a supported application runtime and plan operating system ensures the code can execute after deployment. It does not connect a source repository to an authenticated deployment workflow or automatically publish commits. Set up App Service's supported deployment source or CI/CD pipeline with suitable deployment credentials and build settings.

Question 575

An app must run a specific supported .NET runtime version. Which administrative action most directly meets the requirement?

  1. Configure App Service deployment integration and authorized build/deploy pipeline.
  2. Start the app and review deployment/runtime health before changing the DNS record.
  3. Deploy to an App Service deployment slot supported by the hosting tier.
  4. Choose the appropriate App Service runtime stack and compatible plan OS.

Explanation

Correct Answer

D:

App Service runtime selection determines which supported .NET version runs the deployed application. Set the runtime stack and compatible Windows/Linux hosting configuration to match the app; adding a custom domain or restarting the site cannot install an incompatible framework version.

Incorrect Answers

A:

A CI/CD connection can publish application files, but it does not select a compatible .NET runtime on the App Service worker. The app needs its runtime stack and hosting OS configured to support the specified version, regardless of its deployment pipeline.

B:

Starting an App Service and checking deployment health verifies whether the existing app responds, but does not select the .NET runtime used by the worker. Set a supported .NET stack and compatible plan OS to meet the actual version constraint.

C:

Deployment slots provide isolated staging endpoints for versions of the same application where the hosting tier supports slots. Slots are not a mechanism for selecting the .NET runtime version. Configure an App Service runtime stack and compatible Windows/Linux plan that actually supports the application's target .NET release.

Question 576

A supported .NET web app runs in Azure App Service. The team deploys a prebuilt, self-contained published ZIP artifact directly to a SINGLE production slot, and policy prohibits introducing staging slots. Extracting updates into the active wwwroot has caused file-lock errors and briefly mixed old and new files. The app does not write to its content directory, and a restart during deployment is acceptable. Which deployment configuration addresses the specific file-consistency failure?

  1. Set WEBSITE_RUN_FROM_PACKAGE=1 and deploy a ZIP containing the published app files at its root; App Service mounts the complete ZIP as read-only wwwroot and restarts the app.
  2. Use ordinary extracted ZIP deployment into the existing writable wwwroot and disable application restart; this guarantees that all files become visible simultaneously.
  3. Configure only a GitHub Actions build pipeline while keeping extracted deployment to the live writable content directory; source-control integration itself removes file locks.
  4. Change the App Service runtime stack or scale up the worker CPU without changing how deployment files are copied to the serving content directory.

Explanation

Correct Answer

A:

Microsoft App Service run-from-package mode mounts the deployed ZIP directly as the read-only wwwroot rather than extracting files into the live app directory. WEBSITE_RUN_FROM_PACKAGE=1 with a correctly rooted, already-built .NET package avoids mixed-version and file-lock conflicts. The deployment restarts the app, which the scenario permits, and writes to wwwroot would fail, which the app does not require.

Incorrect Answers

B:

Standard extracted ZIP deployment unpacks files into the same writable wwwroot used at runtime; file locks and partial file replacement are the failures being corrected. Disabling restarts is not a guarantee of atomic content replacement. Use supported run-from-package mounting instead of repeating the implicated extraction approach.

C:

CI/CD orchestration can authorize and automate deployments but is separate from the runtime packaging mechanism. A pipeline that still extracts files into live wwwroot can encounter the same file-lock conflicts. The question already supplies a prebuilt artifact, so the missing control is package mounting rather than a repository or build trigger.

D:

Runtime and worker sizing affect application compatibility and capacity, not how a ZIP archive is made available to running instances. Without switching from extracted deployment to read-only run-from-package, the file-copy consistency hazard remains. No scale or .NET stack change is required by the stated failure.

Question 577

A web app needs connection strings without committing credentials. What should the administrator do to resolve this specific case?

  1. Start the app and review deployment/runtime health before changing the DNS record.
  2. Configure App Service settings/Key Vault references and managed identity as appropriate.
  3. Deploy to an App Service deployment slot supported by the hosting tier.
  4. Choose the appropriate App Service runtime stack and compatible plan OS.

Explanation

Correct Answer

B:

App Service application settings or supported Key Vault references inject connection configuration at runtime rather than storing credentials in source control. When using Key Vault references, the app's managed identity must have permission to read the intended secret.

Incorrect Answers

A:

Starting a stopped application and checking health is troubleshooting availability, not credential hygiene. It doesn't supply connection strings securely or prevent credentials from being committed to source. Store application configuration securely using App Service app settings or Key Vault references with a properly authorized managed identity.

C:

An App Service deployment slot separates staged application versions; it does not secure connection strings against disclosure in source control. Use protected app settings or authorized Key Vault references with the app identity instead of embedding credentials in code.

D:

A compatible OS and application runtime permit the web app code to execute, but they are unrelated to secret storage for connection strings. Use App Service application settings or authorized Key Vault references to avoid placing credentials in the source repository or deployment artifact.

Question 578

An operator sees a stopped web app and mistakes that for a DNS issue. Which change addresses the stated situation most precisely?

  1. Start the app and review deployment/runtime health before changing the DNS record.
  2. Choose the appropriate App Service runtime stack and compatible plan OS.
  3. Use supported A/ALIAS/ANAME solution and ownership verification depending on DNS provider.
  4. Deploy to an App Service deployment slot supported by the hosting tier.

Explanation

Correct Answer

A:

The constraint is: An operator sees a stopped web app and mistakes that for a DNS issue. Start the app and review deployment/runtime health before changing the DNS record. To distinguish neighboring Azure features, remember that app Service deployment can use supported packages/pipelines, runtime stacks and slots; a successful upload is distinct from a healthy app. Verify deployment logs, startup settings, runtime and configuration at the intended app/slot.

Incorrect Answers

B:

Selecting a supported runtime is important for a running web app but does not start an App Service application that is currently stopped. Check the app’s running state and restart it before altering public DNS or assuming the hostname is incorrect.

C:

A DNS A/ALIAS/ANAME mapping or ownership record determines how clients resolve an App Service hostname. The problem explicitly says the web app process is stopped, so changing DNS cannot start its worker or repair deployment health. Start the app and inspect platform/runtime state first.

D:

Creating a staging slot would provide an additional App Service deployment endpoint but would leave the existing production app stopped. Start the affected web app and inspect application health first; a slot does not repair its stopped state.

Question 579

The custom hostname `payments.example.net` is already validated and bound to a paid App Service app. The company uploads its own PFX certificate, which must protect HTTPS traffic for that hostname. What configuration is still required?

  1. Changing the App Service plan from Standard to Premium automatically installs and binds the uploaded certificate.
  2. Create a TLS/SSL binding between the uploaded certificate and the specific custom hostname using a supported binding mode.
  3. Add a storage container SAS to the web app; it authorizes browser TLS handshakes.
  4. Changing the HTTP port to 8080 installs the PFX for all clients automatically.

Explanation

Correct Answer

B:

A TLS/SSL certificate must be bound to the intended custom hostname so the web front end presents the correct certificate during TLS negotiation.

Incorrect Answers

A:

Scaling the plan does not establish a hostname-specific TLS binding for a customer-supplied certificate.

C:

Storage SAS controls Azure Storage data requests and is unrelated to App Service custom-domain certificate presentation.

D:

An HTTP listening port does not create a secure TLS binding to the uploaded certificate.

Question 580

An application needs managed certificate renewal for a supported custom domain. Which administrative action most directly meets the requirement?

  1. Enable HTTPS Only along with certificate and TLS binding requirements.
  2. Configure hostname binding and DNS ownership before expecting HTTPS to work.
  3. Bind the certificate to the App Service custom host and enable appropriate TLS settings.
  4. Evaluate App Service managed certificate eligibility and automate renewal monitoring.

Explanation

Correct Answer

D:

An App Service managed certificate must be supported for the app and verified hostname. Validate eligibility and hostname binding, then monitor certificate state and renewal behavior so the custom domain keeps a valid TLS binding; a generic minimum-TLS setting does not renew a certificate.

Incorrect Answers

A:

Enforcing HTTPS Only redirects HTTP requests once a valid HTTPS configuration exists. It does not determine whether an App Service managed certificate is supported for the custom domain or manage its renewal. Review managed-certificate eligibility and current binding/renewal conditions instead of using an HTTP redirect as a renewal mechanism.

B:

Custom hostname binding and DNS verification identify the host; they do not install a working certificate or enforce TLS policy by themselves.

C:

Binding a valid certificate to a custom hostname enables HTTPS traffic but is distinct from a managed certificate lifecycle. It does not by itself establish App Service managed certificate eligibility or verify that automated renewal will succeed for the requested hostname.