Topic 09 Practice Test 1 covers Azure Containers for Microsoft Azure Administrator AZ-104 and maps to the objective: Provision and manage containers in the Azure portal. For broader exam preparation, review the Microsoft AZ-104 Exam Dumps. Every option includes focused technical reasoning explaining both the Azure concept and its fit to the scenario.
Question 1
Adventure Works runs a production container host that only downloads approved images from a non-ABAC private registry. Which action fits? Choose ONE.
- Assign AcrPull on the non-ABAC registry
- Assign AcrPush on the non-ABAC registry
- Enable the ACR admin account
- Assign Container Registry Repository Reader on the ABAC-enabled registry
Correct Answer: A
Correct Answer
Answer A is correct because For a non-ABAC Azure Container Registry, AcrPull grants pull-only access and is the least-privilege built-in role when a workload only needs to download images. Adventure Works must grant pull-only access to a non-ABAC Azure Container Registry using least privilege. The service behavior matches the constraint.
Incorrect Answers
Answer B is incorrect because For a non-ABAC Azure Container Registry, AcrPush allows both image push and pull operations, making it suitable for build or release identities that publish images. Adventure Works must grant pull-only access to a non-ABAC Azure Container Registry using least privilege. This does not satisfy that condition.
Answer C is incorrect because The ACR admin account is a registry-wide credential intended mainly for limited administrative scenarios; managed identities and scoped role assignments are preferred for Azure workloads. Adventure Works must grant pull-only access to a non-ABAC Azure Container Registry using least privilege. It would leave the requirement unmet.
Answer D is incorrect because For an ABAC-enabled Azure Container Registry, Container Registry Repository Reader provides repository read and pull capability instead of the legacy AcrPull role model. Adventure Works must grant pull-only access to a non-ABAC Azure Container Registry using least privilege. Its function is different in this case.
Question 2
Woodgrove Bank has a deployment service that receives authorization failures while pulling from a non-ABAC registry but does not need write access. Choose the best change. Choose ONE.
- Assign AcrPush on the non-ABAC registry
- Assign AcrPull on the non-ABAC registry
- Enable the ACR admin account
- Assign Container Registry Repository Reader on the ABAC-enabled registry
Correct Answer: B
Correct Answer
Answer B is correct because For a non-ABAC Azure Container Registry, AcrPull grants pull-only access and is the least-privilege built-in role when a workload only needs to download images. Woodgrove Bank must grant pull-only access to a non-ABAC Azure Container Registry using least privilege. This meets the stated administration goal.
Incorrect Answers
Answer A is incorrect because For a non-ABAC Azure Container Registry, AcrPush allows both image push and pull operations, making it suitable for build or release identities that publish images. Woodgrove Bank must grant pull-only access to a non-ABAC Azure Container Registry using least privilege. Its purpose differs from that need.
Answer C is incorrect because The ACR admin account is a registry-wide credential intended mainly for limited administrative scenarios; managed identities and scoped role assignments are preferred for Azure workloads. Woodgrove Bank must grant pull-only access to a non-ABAC Azure Container Registry using least privilege. That behavior does not fit here.
Answer D is incorrect because For an ABAC-enabled Azure Container Registry, Container Registry Repository Reader provides repository read and pull capability instead of the legacy AcrPull role model. Woodgrove Bank must grant pull-only access to a non-ABAC Azure Container Registry using least privilege. The option targets another design goal.
Question 3
An Azure administrator at Wingtip Toys learns that the organization has a build agent that can pull base images but fails when pushing the finished image to a non-ABAC registry. What should the administrator do? Choose ONE.
- Assign AcrPull on the non-ABAC registry
- Enable the ACR admin account
- Assign AcrPush on the non-ABAC registry
- Assign Container Registry Repository Writer on the ABAC-enabled registry
Correct Answer: C
Correct Answer
Answer C is correct because For a non-ABAC Azure Container Registry, AcrPush allows both image push and pull operations, making it suitable for build or release identities that publish images. Wingtip Toys must allow a build identity to push and pull images in a non-ABAC Azure Container Registry. It aligns with the required Azure outcome.
Incorrect Answers
Answer A is incorrect because For a non-ABAC Azure Container Registry, AcrPull grants pull-only access and is the least-privilege built-in role when a workload only needs to download images. Wingtip Toys must allow a build identity to push and pull images in a non-ABAC Azure Container Registry. Its function is different in this case.
Answer B is incorrect because The ACR admin account is a registry-wide credential intended mainly for limited administrative scenarios; managed identities and scoped role assignments are preferred for Azure workloads. Wingtip Toys must allow a build identity to push and pull images in a non-ABAC Azure Container Registry. The feature solves a different problem.
Answer D is incorrect because For an ABAC-enabled Azure Container Registry, Container Registry Repository Writer grants repository write capability needed to publish images while retaining repository-scoped authorization. Wingtip Toys must allow a build identity to push and pull images in a non-ABAC Azure Container Registry. This is not the requested capability.
Question 4
At Proseware, the organization uses a CI pipeline that builds images and publishes them to a non-ABAC private registry. What should be configured? Choose ONE.
- Assign AcrPull on the non-ABAC registry
- Enable the ACR admin account
- Assign Container Registry Repository Writer on the ABAC-enabled registry
- Assign AcrPush on the non-ABAC registry
Correct Answer: D
Correct Answer
Answer D is correct because For a non-ABAC Azure Container Registry, AcrPush allows both image push and pull operations, making it suitable for build or release identities that publish images. Proseware must allow a build identity to push and pull images in a non-ABAC Azure Container Registry. The option supplies the needed behavior.
Incorrect Answers
Answer A is incorrect because For a non-ABAC Azure Container Registry, AcrPull grants pull-only access and is the least-privilege built-in role when a workload only needs to download images. Proseware must allow a build identity to push and pull images in a non-ABAC Azure Container Registry. The option targets another design goal.
Answer B is incorrect because The ACR admin account is a registry-wide credential intended mainly for limited administrative scenarios; managed identities and scoped role assignments are preferred for Azure workloads. Proseware must allow a build identity to push and pull images in a non-ABAC Azure Container Registry. This does not satisfy that condition.
Answer C is incorrect because For an ABAC-enabled Azure Container Registry, Container Registry Repository Writer grants repository write capability needed to publish images while retaining repository-scoped authorization. Proseware must allow a build identity to push and pull images in a non-ABAC Azure Container Registry. It would leave the requirement unmet.
Question 5
- Datum enabled ABAC repository permissions on its registry and needs a runtime identity to consume images without write access. Choose the best change. Choose ONE.
- Assign Container Registry Repository Reader on the ABAC-enabled registry
- Assign AcrPull on the non-ABAC registry
- Assign Container Registry Repository Writer on the ABAC-enabled registry
- Enable the ACR admin account
Correct Answer: A
Correct Answer
Answer A is correct because For an ABAC-enabled Azure Container Registry, Container Registry Repository Reader provides repository read and pull capability instead of the legacy AcrPull role model. A. Datum must grant repository read and pull access on an ABAC-enabled Azure Container Registry. This is the precise operational fit.
Incorrect Answers
Answer B is incorrect because For a non-ABAC Azure Container Registry, AcrPull grants pull-only access and is the least-privilege built-in role when a workload only needs to download images. A. Datum must grant repository read and pull access on an ABAC-enabled Azure Container Registry. This is not the requested capability.
Answer C is incorrect because For an ABAC-enabled Azure Container Registry, Container Registry Repository Writer grants repository write capability needed to publish images while retaining repository-scoped authorization. A. Datum must grant repository read and pull access on an ABAC-enabled Azure Container Registry. Its purpose differs from that need.
Answer D is incorrect because The ACR admin account is a registry-wide credential intended mainly for limited administrative scenarios; managed identities and scoped role assignments are preferred for Azure workloads. A. Datum must grant repository read and pull access on an ABAC-enabled Azure Container Registry. That behavior does not fit here.
Question 6
Lucerne Publishing has an ABAC-enabled registry where a container runtime needs pull capability but no repository modification permissions. Which option is appropriate? Choose ONE.
- Assign AcrPull on the non-ABAC registry
- Assign Container Registry Repository Reader on the ABAC-enabled registry
- Assign Container Registry Repository Writer on the ABAC-enabled registry
- Enable the ACR admin account
Correct Answer: B
Correct Answer
Answer B is correct because For an ABAC-enabled Azure Container Registry, Container Registry Repository Reader provides repository read and pull capability instead of the legacy AcrPull role model. Lucerne Publishing must grant repository read and pull access on an ABAC-enabled Azure Container Registry. That capability fits the scenario directly.
Incorrect Answers
Answer A is incorrect because For a non-ABAC Azure Container Registry, AcrPull grants pull-only access and is the least-privilege built-in role when a workload only needs to download images. Lucerne Publishing must grant repository read and pull access on an ABAC-enabled Azure Container Registry. It would leave the requirement unmet.
Answer C is incorrect because For an ABAC-enabled Azure Container Registry, Container Registry Repository Writer grants repository write capability needed to publish images while retaining repository-scoped authorization. Lucerne Publishing must grant repository read and pull access on an ABAC-enabled Azure Container Registry. Its function is different in this case.
Answer D is incorrect because The ACR admin account is a registry-wide credential intended mainly for limited administrative scenarios; managed identities and scoped role assignments are preferred for Azure workloads. Lucerne Publishing must grant repository read and pull access on an ABAC-enabled Azure Container Registry. The feature solves a different problem.
Question 7
A cloud engineer at Northwind Traders is working with an environment that has a user-assigned workload identity but the private image pull still fails because registry authorization is missing. Select the correct configuration. Choose TWO.
- Configure a user-assigned managed identity for the container workload
- Enable the ACR admin account
- Assign AcrPush on the non-ABAC registry
- Assign AcrPull on the non-ABAC registry
- Assign Container Registry Repository Writer on the ABAC-enabled registry
Correct Answers: A, D
Correct Answers
Answer A is correct because A managed identity lets an Azure workload authenticate to supported services without embedding reusable credentials in application configuration. Northwind Traders must configure both a managed identity and the appropriate pull-only registry role so a Container Apps workload can pull a private image without stored credentials. It therefore matches the requested outcome.
Answer D is correct because For a non-ABAC Azure Container Registry, AcrPull grants pull-only access and is the least-privilege built-in role when a workload only needs to download images. Northwind Traders must configure both a managed identity and the appropriate pull-only registry role so a Container Apps workload can pull a private image without stored credentials. The option supplies the needed behavior.
Incorrect Answers
Answer B is incorrect because The ACR admin account is a registry-wide credential intended mainly for limited administrative scenarios; managed identities and scoped role assignments are preferred for Azure workloads. Northwind Traders must configure both a managed identity and the appropriate pull-only registry role so a Container Apps workload can pull a private image without stored credentials. The option targets another design goal.
Answer C is incorrect because For a non-ABAC Azure Container Registry, AcrPush allows both image push and pull operations, making it suitable for build or release identities that publish images. Northwind Traders must configure both a managed identity and the appropriate pull-only registry role so a Container Apps workload can pull a private image without stored credentials. This does not satisfy that condition.
Answer E is incorrect because For an ABAC-enabled Azure Container Registry, Container Registry Repository Writer grants repository write capability needed to publish images while retaining repository-scoped authorization. Northwind Traders must configure both a managed identity and the appropriate pull-only registry role so a Container Apps workload can pull a private image without stored credentials. It would leave the requirement unmet.
Question 8
An Azure administrator at Contoso learns that the organization uses a private image in a non-ABAC ACR and wants the Container Apps workload to authenticate without a registry password. What should the administrator do? Choose TWO.
- Enable the ACR admin account
- Configure a user-assigned managed identity for the container workload
- Assign AcrPush on the non-ABAC registry
- Assign Container Registry Repository Writer on the ABAC-enabled registry
- Assign AcrPull on the non-ABAC registry
Correct Answers: B, E
Correct Answers
Answer B is correct because A managed identity lets an Azure workload authenticate to supported services without embedding reusable credentials in application configuration. Contoso must configure both a managed identity and the appropriate pull-only registry role so a Container Apps workload can pull a private image without stored credentials. It is the strongest fit here.
Answer E is correct because For a non-ABAC Azure Container Registry, AcrPull grants pull-only access and is the least-privilege built-in role when a workload only needs to download images. Contoso must configure both a managed identity and the appropriate pull-only registry role so a Container Apps workload can pull a private image without stored credentials. This is the precise operational fit.
Incorrect Answers
Answer A is incorrect because The ACR admin account is a registry-wide credential intended mainly for limited administrative scenarios; managed identities and scoped role assignments are preferred for Azure workloads. Contoso must configure both a managed identity and the appropriate pull-only registry role so a Container Apps workload can pull a private image without stored credentials. This is not the requested capability.
Answer C is incorrect because For a non-ABAC Azure Container Registry, AcrPush allows both image push and pull operations, making it suitable for build or release identities that publish images. Contoso must configure both a managed identity and the appropriate pull-only registry role so a Container Apps workload can pull a private image without stored credentials. Its purpose differs from that need.
Answer D is incorrect because For an ABAC-enabled Azure Container Registry, Container Registry Repository Writer grants repository write capability needed to publish images while retaining repository-scoped authorization. Contoso must configure both a managed identity and the appropriate pull-only registry role so a Container Apps workload can pull a private image without stored credentials. That behavior does not fit here.
Question 9
Adventure Works runs a nightly data-conversion container that exits with code 0 after producing its output and must not repeat automatically. Which option is appropriate? Choose ONE.
- Use the Never restart policy in Azure Container Instances
- Use the Always restart policy in Azure Container Instances
- Use the OnFailure restart policy in Azure Container Instances
- Deploy the workload to Azure Container Instances
Correct Answer: A
Correct Answer
Answer A is correct because Never is intended for run-once Azure Container Instances tasks that should not restart after a successful exit, allowing a successfully completed container group to reach Succeeded. Adventure Works must run a successful one-time Azure Container Instances task once and leave it completed instead of starting it again. The service behavior matches the constraint.
Incorrect Answers
Answer B is incorrect because Always is the default Azure Container Instances restart policy and restarts containers after they exit, which fits long-running processes that should be kept running. Adventure Works must run a successful one-time Azure Container Instances task once and leave it completed instead of starting it again. This does not satisfy that condition.
Answer C is incorrect because OnFailure restarts an Azure Container Instances container only when its process exits with a nonzero code, which fits retryable batch work that should not rerun after success. Adventure Works must run a successful one-time Azure Container Instances task once and leave it completed instead of starting it again. It would leave the requirement unmet.
Answer D is incorrect because Azure Container Instances runs containers directly without managing virtual machines or a cluster and is well suited to simple isolated or task-oriented container groups. Adventure Works must run a successful one-time Azure Container Instances task once and leave it completed instead of starting it again. Its function is different in this case.
Question 10
In Woodgrove Bank’s Azure environment, the organization is troubleshooting a run-once container that keeps restarting after successful completion because it uses the default policy. What is required? Choose ONE.
- Use the Always restart policy in Azure Container Instances
- Use the Never restart policy in Azure Container Instances
- Use the OnFailure restart policy in Azure Container Instances
- Deploy the workload to Azure Container Instances
Correct Answer: B
Correct Answer
Answer B is correct because Never is intended for run-once Azure Container Instances tasks that should not restart after a successful exit, allowing a successfully completed container group to reach Succeeded. Woodgrove Bank must run a successful one-time Azure Container Instances task once and leave it completed instead of starting it again. This meets the stated administration goal.
Incorrect Answers
Answer A is incorrect because Always is the default Azure Container Instances restart policy and restarts containers after they exit, which fits long-running processes that should be kept running. Woodgrove Bank must run a successful one-time Azure Container Instances task once and leave it completed instead of starting it again. Its purpose differs from that need.
Answer C is incorrect because OnFailure restarts an Azure Container Instances container only when its process exits with a nonzero code, which fits retryable batch work that should not rerun after success. Woodgrove Bank must run a successful one-time Azure Container Instances task once and leave it completed instead of starting it again. That behavior does not fit here.
Answer D is incorrect because Azure Container Instances runs containers directly without managing virtual machines or a cluster and is well suited to simple isolated or task-oriented container groups. Woodgrove Bank must run a successful one-time Azure Container Instances task once and leave it completed instead of starting it again. The option targets another design goal.
Question 11
Wingtip Toys has an ACI task that must distinguish a successful exit from a failed exit when deciding whether to restart. Which Azure feature fits? Choose ONE.
- Use the Always restart policy in Azure Container Instances
- Use the Never restart policy in Azure Container Instances
- Use the OnFailure restart policy in Azure Container Instances
- Deploy the workload to Azure Container Instances
Correct Answer: C
Correct Answer
Answer C is correct because OnFailure restarts an Azure Container Instances container only when its process exits with a nonzero code, which fits retryable batch work that should not rerun after success. Wingtip Toys must retry an Azure Container Instances batch process only when the process exits with a failure. It aligns with the required Azure outcome.
Incorrect Answers
Answer A is incorrect because Always is the default Azure Container Instances restart policy and restarts containers after they exit, which fits long-running processes that should be kept running. Wingtip Toys must retry an Azure Container Instances batch process only when the process exits with a failure. Its function is different in this case.
Answer B is incorrect because Never is intended for run-once Azure Container Instances tasks that should not restart after a successful exit, allowing a successfully completed container group to reach Succeeded. Wingtip Toys must retry an Azure Container Instances batch process only when the process exits with a failure. The feature solves a different problem.
Answer D is incorrect because Azure Container Instances runs containers directly without managing virtual machines or a cluster and is well suited to simple isolated or task-oriented container groups. Wingtip Toys must retry an Azure Container Instances batch process only when the process exits with a failure. This is not the requested capability.
Question 12
A cloud engineer at Proseware is working with an environment that runs an import container that may fail transiently and should retry only after a nonzero exit. Select the correct configuration. Choose ONE.
- Use the Always restart policy in Azure Container Instances
- Use the Never restart policy in Azure Container Instances
- Deploy the workload to Azure Container Instances
- Use the OnFailure restart policy in Azure Container Instances
Correct Answer: D
Correct Answer
Answer D is correct because OnFailure restarts an Azure Container Instances container only when its process exits with a nonzero code, which fits retryable batch work that should not rerun after success. Proseware must retry an Azure Container Instances batch process only when the process exits with a failure. The option supplies the needed behavior.
Incorrect Answers
Answer A is incorrect because Always is the default Azure Container Instances restart policy and restarts containers after they exit, which fits long-running processes that should be kept running. Proseware must retry an Azure Container Instances batch process only when the process exits with a failure. The option targets another design goal.
Answer B is incorrect because Never is intended for run-once Azure Container Instances tasks that should not restart after a successful exit, allowing a successfully completed container group to reach Succeeded. Proseware must retry an Azure Container Instances batch process only when the process exits with a failure. This does not satisfy that condition.
Answer C is incorrect because Azure Container Instances runs containers directly without managing virtual machines or a cluster and is well suited to simple isolated or task-oriented container groups. Proseware must retry an Azure Container Instances batch process only when the process exits with a failure. It would leave the requirement unmet.
Question 13
In A. Datum’s Azure environment, the organization needs to execute a short-lived utility container with minimal platform administration. What is required? Choose ONE.
- Deploy the workload to Azure Container Instances
- Deploy the workload to Azure Container Apps
- Use Azure Container Registry (ACR)
- Use the Always restart policy in Azure Container Instances
Correct Answer: A
Correct Answer
Answer A is correct because Azure Container Instances runs containers directly without managing virtual machines or a cluster and is well suited to simple isolated or task-oriented container groups. A. Datum must run a simple isolated container without managing virtual machines or a container orchestration cluster. This is the precise operational fit.
Incorrect Answers
Answer B is incorrect because Azure Container Apps is a serverless container platform that supports revisions, ingress, event-driven KEDA scaling, and scale-to-zero for supported workloads. A. Datum must run a simple isolated container without managing virtual machines or a container orchestration cluster. This is not the requested capability.
Answer C is incorrect because Azure Container Registry is a managed private registry for container images and related artifacts, with Azure-integrated identity, access control, and image-distribution capabilities. A. Datum must run a simple isolated container without managing virtual machines or a container orchestration cluster. Its purpose differs from that need.
Answer D is incorrect because Always is the default Azure Container Instances restart policy and restarts containers after they exit, which fits long-running processes that should be kept running. A. Datum must run a simple isolated container without managing virtual machines or a container orchestration cluster. That behavior does not fit here.
Question 14
Lucerne Publishing wants the quickest Azure service for directly running a standalone container group. Which action fits? Choose ONE.
- Deploy the workload to Azure Container Apps
- Deploy the workload to Azure Container Instances
- Use Azure Container Registry (ACR)
- Use the Always restart policy in Azure Container Instances
Correct Answer: B
Correct Answer
Answer B is correct because Azure Container Instances runs containers directly without managing virtual machines or a cluster and is well suited to simple isolated or task-oriented container groups. Lucerne Publishing must run a simple isolated container without managing virtual machines or a container orchestration cluster. That capability fits the scenario directly.
Incorrect Answers
Answer A is incorrect because Azure Container Apps is a serverless container platform that supports revisions, ingress, event-driven KEDA scaling, and scale-to-zero for supported workloads. Lucerne Publishing must run a simple isolated container without managing virtual machines or a container orchestration cluster. It would leave the requirement unmet.
Answer C is incorrect because Azure Container Registry is a managed private registry for container images and related artifacts, with Azure-integrated identity, access control, and image-distribution capabilities. Lucerne Publishing must run a simple isolated container without managing virtual machines or a container orchestration cluster. Its function is different in this case.
Answer D is incorrect because Always is the default Azure Container Instances restart policy and restarts containers after they exit, which fits long-running processes that should be kept running. Lucerne Publishing must run a simple isolated container without managing virtual machines or a container orchestration cluster. The feature solves a different problem.
Question 15
At Northwind Traders, the organization has outgrown a simple container group because the workload now requires managed application ingress and autoscaling. What should be configured? Choose ONE.
- Deploy the workload to Azure Container Instances
- Use Azure Container Registry (ACR)
- Deploy the workload to Azure Container Apps
- Use the Always restart policy in Azure Container Instances
Correct Answer: C
Correct Answer
Answer C is correct because Azure Container Apps is a serverless container platform that supports revisions, ingress, event-driven KEDA scaling, and scale-to-zero for supported workloads. Northwind Traders must host a containerized application with managed ingress, revisions, and event-driven horizontal scaling. It therefore matches the requested outcome.
Incorrect Answers
Answer A is incorrect because Azure Container Instances runs containers directly without managing virtual machines or a cluster and is well suited to simple isolated or task-oriented container groups. Northwind Traders must host a containerized application with managed ingress, revisions, and event-driven horizontal scaling. That behavior does not fit here.
Answer B is incorrect because Azure Container Registry is a managed private registry for container images and related artifacts, with Azure-integrated identity, access control, and image-distribution capabilities. Northwind Traders must host a containerized application with managed ingress, revisions, and event-driven horizontal scaling. The option targets another design goal.
Answer D is incorrect because Always is the default Azure Container Instances restart policy and restarts containers after they exit, which fits long-running processes that should be kept running. Northwind Traders must host a containerized application with managed ingress, revisions, and event-driven horizontal scaling. This does not satisfy that condition.
Question 16
Contoso is deploying a public API that needs revisions and scale rules without operating Kubernetes. Which Azure feature fits? Choose ONE.
- Deploy the workload to Azure Container Instances
- Use Azure Container Registry (ACR)
- Use the Always restart policy in Azure Container Instances
- Deploy the workload to Azure Container Apps
Correct Answer: D
Correct Answer
Answer D is correct because Azure Container Apps is a serverless container platform that supports revisions, ingress, event-driven KEDA scaling, and scale-to-zero for supported workloads. Contoso must host a containerized application with managed ingress, revisions, and event-driven horizontal scaling. It is the strongest fit here.
Incorrect Answers
Answer A is incorrect because Azure Container Instances runs containers directly without managing virtual machines or a cluster and is well suited to simple isolated or task-oriented container groups. Contoso must host a containerized application with managed ingress, revisions, and event-driven horizontal scaling. The feature solves a different problem.
Answer B is incorrect because Azure Container Registry is a managed private registry for container images and related artifacts, with Azure-integrated identity, access control, and image-distribution capabilities. Contoso must host a containerized application with managed ingress, revisions, and event-driven horizontal scaling. This is not the requested capability.
Answer C is incorrect because Always is the default Azure Container Instances restart policy and restarts containers after they exit, which fits long-running processes that should be kept running. Contoso must host a containerized application with managed ingress, revisions, and event-driven horizontal scaling. Its purpose differs from that need.
Question 17
Adventure Works has a latency-sensitive API where scale-to-zero cold starts are unacceptable. Which action fits? Choose ONE.
- Set the minimum replica count to 1
- Allow the minimum replica count to remain 0
- Configure an HTTP scaling rule in Azure Container Apps
- Configure a custom KEDA-backed scaling rule in Azure Container Apps
Correct Answer: A
Correct Answer
Answer A is correct because Setting minReplicas to 1 or higher keeps at least one Container Apps replica running instead of allowing the revision to scale down to zero. Adventure Works must keep at least one Azure Container Apps replica running even when there is no traffic. The service behavior matches the constraint.
Incorrect Answers
Answer B is incorrect because A minimum replica count of 0 permits supported Container Apps workloads to scale to zero when no scaling rule requires a replica. Adventure Works must keep at least one Azure Container Apps replica running even when there is no traffic. This does not satisfy that condition.
Answer C is incorrect because An HTTP scaling rule scales a Container Apps revision according to concurrent HTTP request load, within configured minimum and maximum replica limits. Adventure Works must keep at least one Azure Container Apps replica running even when there is no traffic. It would leave the requirement unmet.
Answer D is incorrect because Container Apps supports custom event-driven scaling through KEDA-compatible triggers such as Service Bus, Event Hubs, Kafka, Redis, CPU, or memory metrics. Adventure Works must keep at least one Azure Container Apps replica running even when there is no traffic. Its function is different in this case.
Question 18
Woodgrove Bank is troubleshooting an app that scales completely to zero and wants a continuously running baseline instance. Choose the best change. Choose ONE.
- Allow the minimum replica count to remain 0
- Set the minimum replica count to 1
- Configure an HTTP scaling rule in Azure Container Apps
- Configure a custom KEDA-backed scaling rule in Azure Container Apps
Correct Answer: B
Correct Answer
Answer B is correct because Setting minReplicas to 1 or higher keeps at least one Container Apps replica running instead of allowing the revision to scale down to zero. Woodgrove Bank must keep at least one Azure Container Apps replica running even when there is no traffic. This meets the stated administration goal.
Incorrect Answers
Answer A is incorrect because A minimum replica count of 0 permits supported Container Apps workloads to scale to zero when no scaling rule requires a replica. Woodgrove Bank must keep at least one Azure Container Apps replica running even when there is no traffic. Its purpose differs from that need.
Answer C is incorrect because An HTTP scaling rule scales a Container Apps revision according to concurrent HTTP request load, within configured minimum and maximum replica limits. Woodgrove Bank must keep at least one Azure Container Apps replica running even when there is no traffic. That behavior does not fit here.
Answer D is incorrect because Container Apps supports custom event-driven scaling through KEDA-compatible triggers such as Service Bus, Event Hubs, Kafka, Redis, CPU, or memory metrics. Woodgrove Bank must keep at least one Azure Container Apps replica running even when there is no traffic. The option targets another design goal.
Question 19
An Azure administrator at Wingtip Toys learns that the organization is replacing a fixed replica count with demand-based scaling for inbound HTTP traffic. What should the administrator do? Choose ONE.
- Configure a custom KEDA-backed scaling rule in Azure Container Apps
- Set the minimum replica count to 1
- Configure an HTTP scaling rule in Azure Container Apps
- Allow the minimum replica count to remain 0
Correct Answer: C
Correct Answer
Answer C is correct because An HTTP scaling rule scales a Container Apps revision according to concurrent HTTP request load, within configured minimum and maximum replica limits. Wingtip Toys must scale an Azure Container Apps revision according to concurrent HTTP request load. It aligns with the required Azure outcome.
Incorrect Answers
Answer A is incorrect because Container Apps supports custom event-driven scaling through KEDA-compatible triggers such as Service Bus, Event Hubs, Kafka, Redis, CPU, or memory metrics. Wingtip Toys must scale an Azure Container Apps revision according to concurrent HTTP request load. Its function is different in this case.
Answer B is incorrect because Setting minReplicas to 1 or higher keeps at least one Container Apps replica running instead of allowing the revision to scale down to zero. Wingtip Toys must scale an Azure Container Apps revision according to concurrent HTTP request load. The feature solves a different problem.
Answer D is incorrect because A minimum replica count of 0 permits supported Container Apps workloads to scale to zero when no scaling rule requires a replica. Wingtip Toys must scale an Azure Container Apps revision according to concurrent HTTP request load. This is not the requested capability.
Question 20
At Proseware, the organization has an HTTP API whose replica count should react directly to concurrent web requests. What should be configured? Choose ONE.
- Configure a custom KEDA-backed scaling rule in Azure Container Apps
- Set the minimum replica count to 1
- Allow the minimum replica count to remain 0
- Configure an HTTP scaling rule in Azure Container Apps
Correct Answer: D
Correct Answer
Answer D is correct because An HTTP scaling rule scales a Container Apps revision according to concurrent HTTP request load, within configured minimum and maximum replica limits. Proseware must scale an Azure Container Apps revision according to concurrent HTTP request load. The option supplies the needed behavior.
Incorrect Answers
Answer A is incorrect because Container Apps supports custom event-driven scaling through KEDA-compatible triggers such as Service Bus, Event Hubs, Kafka, Redis, CPU, or memory metrics. Proseware must scale an Azure Container Apps revision according to concurrent HTTP request load. The option targets another design goal.
Answer B is incorrect because Setting minReplicas to 1 or higher keeps at least one Container Apps replica running instead of allowing the revision to scale down to zero. Proseware must scale an Azure Container Apps revision according to concurrent HTTP request load. This does not satisfy that condition.
Answer C is incorrect because A minimum replica count of 0 permits supported Container Apps workloads to scale to zero when no scaling rule requires a replica. Proseware must scale an Azure Container Apps revision according to concurrent HTTP request load. It would leave the requirement unmet.
