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 55

Question 540

An Azure Container Instances Linux group must have private IP connectivity in an approved VNet. Which network deployment approach is appropriate?

  1. Deploy the container group into a supported delegated Azure VNet subnet with the necessary routing/network configuration.
  2. Assign an Azure public DNS record and assume it places the group into the VNet.
  3. Create only a storage account service endpoint on a different subnet.
  4. Enable a VMSS network profile for an ACI resource.

Explanation

Correct Answer

A:

ACI VNet deployments require a supported subnet/network setup; public DNS is not a substitute for internal placement.

Incorrect Answers

B:

DNS records can resolve names but do not place Azure container group NICs in private subnets.

C:

A service endpoint allows selected subnet-to-PaaS traffic and does not attach a separate ACI instance to the subnet.

D:

VM Scale Set networking definitions do not deploy an Azure Container Instances group into a VNet.

Question 541

An ACI Linux container gets OOM-killed during a legitimate workload peak because the configured memory limit is too low. What should be changed?

  1. Change only the container-group DNS label.
  2. Enable a VMSS scale-out metric on the unrelated subscription.
  3. Increase requested/limited container-group memory within supported service and regional capacity.
  4. Grant the ACI identity an ACR push role.

Explanation

Correct Answer

C:

Insufficient memory causes OOM terminations; a supported resource request that fits the workload directly addresses it.

Incorrect Answers

A:

A DNS label has no bearing on the memory allocated to the container process.

B:

ACI does not use an unrelated VMSS scaling rule to increase per-container RAM.

D:

Image registry push permission does not allocate extra runtime memory.

Question 542

A basic Azure Container Instances web endpoint must be reachable publicly over an approved TCP port. What networking feature should the group use?

  1. Configure supported public IP/DNS label and expose the application port, with suitable ingress protection.
  2. Mount an Azure Files share and assume it automatically publishes the service.
  3. Give the image repository AcrPush permissions to open the container port.
  4. Create a private-only subnet attachment without a public ingress plan.

Explanation

Correct Answer

A:

ACI supports a public endpoint with specified ports and optional DNS label for a container group; security controls still matter.

Incorrect Answers

B:

A storage volume provides persistence but does not expose a public HTTP/TCP endpoint.

C:

ACR permissions authorize repository actions, not container-group network ingress.

D:

A private-only endpoint is not publicly routable without an additional inbound architecture.

Question 543

An ACI Linux application must retain generated files even when its container is restarted or recreated. Which storage attachment is appropriate?

  1. Rely exclusively on the writable layer of the short-lived container image.
  2. Use an Azure managed OS disk attached directly to the ACI container.
  3. Mount a compatible Azure Files share as persistent storage for the container group.
  4. Keep only temporary environment variables containing the file names.

Explanation

Correct Answer

C:

ACI supports persistent Azure Files mounts for retaining state beyond the container lifecycle on supported Linux groups.

Incorrect Answers

A:

The container writable filesystem is not a durable state store when the container group is replaced.

B:

ACI containers do not attach individual Azure VM managed OS disks like IaaS VMs.

D:

Environment variables store configuration, not durable binary file contents.

Question 544

A long-running Linux API runs in an existing Azure Container Instances group with restartPolicy Never, inherited from its former run-once workload. A liveness probe correctly detects a deadlocked process, but the group does not restart after the failed check. The team has an approved maintenance window and can recreate the group. Which plan provides automatic liveness recovery while respecting ACI update limits?

  1. Update restartPolicy from Never to Always in place by redeploying the same running group name; restart policy is a freely editable property.
  2. Save the required deployment settings, delete and recreate the ACI group with restartPolicy Always and the valid liveness probe, then validate startup and the resulting endpoint.
  3. Keep restartPolicy Never but make the liveness probe run every second; probe frequency overrides the group-level restart policy.
  4. Replace liveness with readiness alone; a readiness failure always restarts an ACI group despite a Never restart policy.

Explanation

Correct Answer

B:

Failed ACI liveness checks can restart a container when the restart policy permits. Never takes precedence over liveness restarts, and changing the group restart policy requires deletion and recreation. A maintenance-window recreation with Always and the retained liveness probe supports the desired automatic recovery; deployment and endpoint identity must be revalidated.

Incorrect Answers

A:

An ACI restart-policy change is not a supported in-place update: Microsoft lists restart policy among properties requiring container-group deletion and recreation. An in-place redeployment with this changed field is therefore not the valid plan.

C:

The liveness probe can detect failure more often, but its interval does not override restartPolicy Never. Without a compatible restart policy the unhealthy container will not automatically recover from the failed liveness test.

D:

Readiness determines whether a container should receive requests; it does not replace liveness-triggered process restart. Moreover, an ACI group configured Never does not become restartable merely by swapping probe types.

Question 545

An Azure Container Instances Linux group cg-orders is running two containers: an API and its logging sidecar. A revised API image tag is approved for deployment. The CPU, memory, restart policy and networking must not change, and a coordinated brief restart of both containers is acceptable. Which action updates the running group most directly?

  1. Use az container restart against only the API container inside cg-orders, leaving the sidecar running and changing the API image automatically.
  2. Redeploy the existing running container group using the same name with the new API image and all other required settings preserved; expect both containers in the group to restart and validate the endpoint afterward.
  3. Change CPU, memory and restart policy in place at the same time as the image because all ACI properties support in-place updates.
  4. Push a new image under the same Azure Container Registry tag and assume that already-running containers hot-swap their filesystem without any container-group deployment action.

Explanation

Correct Answer

B:

ACI permits updates to supported properties, including the image reference, by redeploying an existing running group with the same name and changed configuration. All containers restart together, so retain unchanged settings explicitly and validate the application/endpoint afterward; even the IP address is not absolutely guaranteed to remain the same.

Incorrect Answers

A:

ACI restart operations act on the entire container group, not only an individual member. A restart also does not express the intended revised image declaration as clearly as redeploying the group with the updated image reference.

C:

CPU, memory and restart policy are explicitly among ACI properties that require deletion and recreation. They are also outside the approved change, so combining them with a supported image update invalidates the proposed in-place operation.

D:

Pushing an image to ACR does not automatically replace image contents inside an already-running container. The ACI deployment must be updated or otherwise restarted/recreated through a supported lifecycle action to pull the desired revision.

Question 546

A retail API must handle unpredictable HTTP request bursts without virtual-machine administration. It currently runs as a container image, and its team wants Azure-managed ingress and replica autoscaling based on concurrent HTTP requests. Which TWO platform choices satisfy those requirements? Select TWO answers.

  1. Use only a CPU-based virtual-machine scale-set autoscale policy and keep operating the guest VM image.
  2. Configure an HTTP concurrency scaling rule with supported replica bounds for the Container App revision.
  3. Use an Azure Queue Storage event trigger but disable HTTP ingress for the public API.
  4. Deploy the image as an Azure Container App in a suitable environment with supported HTTP ingress enabled.
  5. Create a static Azure DNS CNAME record and assume it controls the number of running replicas.

Explanation

Correct Answers

B:

Container Apps can scale revisions by the number of concurrent HTTP requests, subject to configured minimum and maximum replica limits. An HTTP scale rule evaluates actual ingress demand and adds or removes replicas without requiring custom VM infrastructure. Choosing the correct HTTP concurrency threshold is essential: an unrelated CPU rule or queue backlog threshold would respond to a different demand signal. The rule belongs to the revision template and should be tested for cold-start and application latency behavior.

D:

Azure Container Apps provides managed container execution and supports ingress for HTTP services. Deploying the image into an eligible Container Apps environment supplies the runtime and ingress path that an HTTP autoscaler can observe. The deployment action and HTTP scaling-rule configuration are independently necessary to deliver the requested API. Neither DNS record creation nor a VM-based deployment provides both managed ingress and application-level replica scaling for the stated container workload.

Incorrect Answers

A:

A VM scale set can increase machine instances using metrics, but the team explicitly wants to avoid managing guest VMs and scale container replicas through Azure Container Apps HTTP ingress. Compute VM autoscale is not the requested managed serverless container execution model, even if it can handle some burst traffic.

C:

Queue-trigger scaling is suitable for a background worker consuming an event-driven queue, but the scenario’s demand signal is incoming HTTP requests to a public API. Disabling ingress would remove the requested HTTP entry point, and a queue trigger cannot replace the concurrency signal for this traffic pattern.

E:

DNS records resolve a host name to an endpoint; they do not measure HTTP concurrency or instruct Container Apps to add replicas. A CNAME may be part of custom-domain configuration but does not substitute for the runtime environment, enabled ingress, or supported scale rule.

Question 547

A background Azure Container Apps worker has no HTTP ingress and must scale when Azure Queue Storage accumulates messages. What scale rule should be configured?

  1. An HTTP concurrency trigger even though the worker receives no HTTP requests.
  2. A DNS TTL-based schedule that never queries Azure Queue Storage.
  3. An Azure Queue Storage event-driven scale rule with authorized queue access.
  4. A revision traffic-splitting rule with no queue metric.

Explanation

Correct Answer

C:

Container Apps supports event-driven scalers such as Azure Storage Queue, with managed identity or scoped secret authentication.

Incorrect Answers

A:

HTTP traffic does not reflect work for this queue-driven worker without ingress.

B:

DNS resolver caching does not measure queue length or create replicas.

D:

Routing between revisions handles releases and does not scale based on backlog.

Question 548

A Container Apps team must send 10% of live requests to v2 and keep 90% on v1 for comparison. Which revision configuration meets the requirement?

  1. Disable all revisions so a platform default chooses the version.
  2. Enable single-revision mode, which deactivates the old revision before splitting traffic.
  3. Only configure a replica memory limit; do not change traffic weights.
  4. Use multiple-revision mode with both revisions active and an explicit weighted traffic split.

Explanation

Correct Answer

D:

Multiple active revisions allow explicit percentage-based traffic distribution for canary or A/B tests.

Incorrect Answers

A:

Disabling revisions prevents the stated controlled live experiment.

B:

Single-revision mode keeps one active revision and does not support simultaneous weighted A/B traffic.

C:

Replica memory is a scaling/resource concern, not version-weighted HTTP routing.

Question 549

A service must never serve requests from two revisions simultaneously when a new Container Apps image is deployed. Which revision mode matches this policy?

  1. Multiple-revision mode with a 50/50 split during every deployment.
  2. Create a separate Azure Container Registry tag for each release only.
  3. Single-revision mode, which switches after readiness and deactivates the older revision.
  4. Scale the maximum replica count to one while retaining multiple active revisions.

Explanation

Correct Answer

C:

Single-revision mode has one active revision at a time with readiness-based traffic handoff.

Incorrect Answers

A:

Multiple-revision mode explicitly supports concurrent active revisions, conflicting with the policy.

B:

Image tags label artifacts but do not control runtime revision activation.

D:

Replica count is not the number of active revisions; one replica per revision can still yield two active versions.

Question 550

A Container Apps worker must connect outbound to a database exposed only on an internal Azure network; the database must not become public. What should be configured?

  1. Enable public anonymous ingress on the database to remove network restrictions.
  2. Use an appropriately connected Container Apps environment/VNet routing and private DNS to reach the backend.
  3. Configure an ACR webhook as the only network path to the database.
  4. Use single-revision mode without checking any subnet or private network configuration.

Explanation

Correct Answer

B:

Private VNet connectivity and correct routing/DNS are needed for outbound requests to an internal backend.

Incorrect Answers

A:

Public exposure contradicts the private-backend requirement and increases attack surface.

C:

ACR webhooks notify build events and do not provide database network routing.

D:

Revision mode governs deployment activity, not the private connectivity path.