Topic 09 Practice Test 2 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
At Tailspin Toys, the organization is replacing a shared registry password for a runtime identity that never publishes images. What should be configured? 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. Tailspin Toys must grant pull-only access to a non-ABAC Azure Container Registry using least privilege. This is the precise operational fit.
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. Tailspin Toys must grant pull-only access to a non-ABAC Azure Container Registry using least privilege. This is not the requested capability.
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. Tailspin Toys must grant pull-only access to a non-ABAC Azure Container Registry using least privilege. Its purpose differs from that need.
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. Tailspin Toys must grant pull-only access to a non-ABAC Azure Container Registry using least privilege. That behavior does not fit here.
Question 2
An Azure administrator at Proseware learns that the organization is auditing registry permissions and finds a workload identity with unnecessary push rights even though it only consumes images. What should the administrator do? 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. Proseware must grant pull-only access to a non-ABAC Azure Container Registry using least privilege. That capability fits the scenario directly.
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. Proseware must grant pull-only access to a non-ABAC Azure Container Registry using least privilege. It would leave the requirement unmet.
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. Proseware must grant pull-only access to a non-ABAC Azure Container Registry using least privilege. Its function is different in this case.
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. Proseware must grant pull-only access to a non-ABAC Azure Container Registry using least privilege. The feature solves a different problem.
Question 3
- Datum is applying least privilege to a deployment pipeline that legitimately needs both read and write access to registry images. Which option is appropriate? 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. A. Datum must allow a build identity to push and pull images in a non-ABAC Azure Container Registry. It therefore matches the requested 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. A. Datum must allow a build identity to push and pull images in a non-ABAC Azure Container Registry. That behavior does not fit here.
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. A. Datum must allow a build identity to push and pull images in a non-ABAC Azure Container Registry. The option targets another design goal.
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. A. Datum must allow a build identity to push and pull images in a non-ABAC Azure Container Registry. This does not satisfy that condition.
Question 4
Litware is removing the registry admin credential from a release process that must still publish new image tags. Choose the best change. 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. Litware must allow a build identity to push and pull images in a non-ABAC Azure Container Registry. It is the strongest fit here.
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. Litware must allow a build identity to push and pull images in a non-ABAC Azure Container Registry. The feature solves a different problem.
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. Litware must allow a build identity to push and pull images in a non-ABAC 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. Litware must allow a build identity to push and pull images in a non-ABAC Azure Container Registry. Its purpose differs from that need.
Question 5
An Azure administrator at Fourth Coffee learns that the organization is migrating registry authorization from legacy non-ABAC roles to repository-scoped permissions for read-only workloads. What should the administrator do? 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. Fourth Coffee must grant repository read and pull access on an ABAC-enabled Azure Container Registry. The service behavior matches the constraint.
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. Fourth Coffee must grant repository read and pull access on an ABAC-enabled 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. Fourth Coffee must grant repository read and pull access on an ABAC-enabled Azure Container Registry. It would leave the requirement unmet.
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. Fourth Coffee must grant repository read and pull access on an ABAC-enabled Azure Container Registry. Its function is different in this case.
Question 6
A cloud engineer at Contoso is working with an environment that is reviewing an ABAC registry and wants the current repository-scoped read role rather than a legacy pull role. Select the correct configuration. 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. Contoso must grant repository read and pull access on an ABAC-enabled Azure Container Registry. This meets the stated administration goal.
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. Contoso must grant repository read and pull access on an ABAC-enabled Azure Container Registry. Its purpose differs from that need.
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. Contoso must grant repository read and pull access on an ABAC-enabled Azure Container Registry. That behavior does not fit here.
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. Contoso must grant repository read and pull access on an ABAC-enabled Azure Container Registry. The option targets another design goal.
Question 7
In Adventure Works’s Azure environment, the organization is designing credential-free image pulls from a non-ABAC registry for an Azure Container Apps deployment. What is required? 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. Adventure Works 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 aligns with the required Azure 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. Adventure Works 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.
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. Adventure Works 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 feature solves a different problem.
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. Adventure Works 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 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. Adventure Works 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.
Question 8
Fabrikam is hardening a private-image deployment by removing reusable credentials while keeping least-privilege image pull access. Which option is appropriate? 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. Fabrikam 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.
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. Fabrikam 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 service behavior matches the constraint.
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. Fabrikam 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 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. Fabrikam 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.
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. Fabrikam 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 function is different in this case.
Question 9
A cloud engineer at Tailspin Toys is working with an environment that has a migration container that should enter a completed state after a successful run. Select the correct configuration. 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. Tailspin Toys must run a successful one-time Azure Container Instances task once and leave it completed instead of starting it again. This is the precise operational fit.
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. Tailspin Toys must run a successful one-time Azure Container Instances task once and leave it completed instead of starting it again. This is not the requested capability.
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. Tailspin Toys 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 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. Tailspin Toys 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.
Question 10
Proseware needs a disposable task container whose successful process exit should end the execution lifecycle. 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: 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. Proseware must run a successful one-time Azure Container Instances task once and leave it completed instead of starting it again. That capability fits the scenario directly.
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 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 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. Proseware 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.
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. Proseware must run a successful one-time Azure Container Instances task once and leave it completed instead of starting it again. The feature solves a different problem.
Question 11
- Datum is replacing the Always policy because completed jobs must stop but failed jobs should be retried. Which action 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. A. Datum must retry an Azure Container Instances batch process only when the process exits with a failure. It therefore matches the requested 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. A. Datum must retry an Azure Container Instances batch process only when the process exits with a failure. That behavior does not fit here.
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. A. Datum must retry an Azure Container Instances batch process only when the process exits with a failure. The option targets another design goal.
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. A. Datum must retry an Azure Container Instances batch process only when the process exits with a failure. This does not satisfy that condition.
Question 12
In Litware’s Azure environment, the organization wants successful batch executions to remain complete while failed executions are automatically attempted again. What is required? 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. Litware must retry an Azure Container Instances batch process only when the process exits with a failure. It is the strongest fit here.
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. Litware must retry an Azure Container Instances batch process only when the process exits with a failure. The feature solves a different problem.
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. Litware must retry an Azure Container Instances batch process only when the process exits with a failure. This is not the requested capability.
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. Litware must retry an Azure Container Instances batch process only when the process exits with a failure. Its purpose differs from that need.
Question 13
Fourth Coffee has a single diagnostic container that does not require revisions, ingress routing, or application autoscaling. Which Azure feature fits? 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. Fourth Coffee must run a simple isolated container without managing virtual machines or a container orchestration cluster. The service behavior matches the constraint.
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. Fourth Coffee must run a simple isolated container without managing virtual machines or a container orchestration cluster. This does not satisfy that condition.
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. Fourth Coffee must run a simple isolated container without managing virtual machines or a container orchestration cluster. It would leave the requirement unmet.
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. Fourth Coffee must run a simple isolated container without managing virtual machines or a container orchestration cluster. Its function is different in this case.
Question 14
At Contoso, the organization is moving a one-off container task off a VM and does not need a long-running app platform. What should be configured? 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. Contoso must run a simple isolated container without managing virtual machines or a container orchestration cluster. This meets the stated administration goal.
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. Contoso must run a simple isolated container without managing virtual machines or a container orchestration cluster. Its purpose differs from that need.
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. Contoso must run a simple isolated container without managing virtual machines or a container orchestration cluster. That behavior does not fit here.
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. Contoso must run a simple isolated container without managing virtual machines or a container orchestration cluster. The option targets another design goal.
Question 15
Adventure Works is selecting a platform for long-running microservices where KEDA-backed scaling and revision management are required. Choose the best change. 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. Adventure Works must host a containerized application with managed ingress, revisions, and event-driven horizontal scaling. It aligns with the required Azure 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. Adventure Works must host a containerized application with managed ingress, revisions, and event-driven horizontal scaling. Its function is different in this case.
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. Adventure Works must host a containerized application with managed ingress, revisions, and event-driven horizontal scaling. The feature solves a different problem.
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. Adventure Works must host a containerized application with managed ingress, revisions, and event-driven horizontal scaling. This is not the requested capability.
Question 16
Fabrikam needs a serverless container application that can split traffic during releases and scale with events. Which action 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. Fabrikam must host a containerized application with managed ingress, revisions, and event-driven horizontal scaling. The option supplies the needed behavior.
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. Fabrikam must host a containerized application with managed ingress, revisions, and event-driven horizontal scaling. The option targets another design goal.
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. Fabrikam must host a containerized application with managed ingress, revisions, and event-driven horizontal scaling. This does not satisfy that condition.
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. Fabrikam must host a containerized application with managed ingress, revisions, and event-driven horizontal scaling. It would leave the requirement unmet.
Question 17
At Tailspin Toys, the organization must guarantee that an idle revision retains one ready replica. What should be configured? 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. Tailspin Toys must keep at least one Azure Container Apps replica running even when there is no traffic. This is the precise operational fit.
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. Tailspin Toys must keep at least one Azure Container Apps replica running even when there is no traffic. This is not the requested capability.
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. Tailspin Toys must keep at least one Azure Container Apps replica running even when there is no traffic. Its purpose differs from that need.
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. Tailspin Toys must keep at least one Azure Container Apps replica running even when there is no traffic. That behavior does not fit here.
Question 18
An Azure administrator at Proseware learns that the organization accepts automatic scale-out but requires the revision to keep one replica during quiet periods. What should the administrator do? 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. Proseware must keep at least one Azure Container Apps replica running even when there is no traffic. That capability fits the scenario directly.
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. Proseware must keep at least one Azure Container Apps replica running even when there is no traffic. It would leave the requirement unmet.
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. Proseware must keep at least one Azure Container Apps replica running even when there is no traffic. Its function is different in this case.
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. Proseware must keep at least one Azure Container Apps replica running even when there is no traffic. The feature solves a different problem.
Question 19
- Datum wants the platform to add replicas when simultaneous HTTP requests cross a configured threshold. Which option is appropriate? 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. A. Datum must scale an Azure Container Apps revision according to concurrent HTTP request load. It therefore matches the requested 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. A. Datum must scale an Azure Container Apps revision according to concurrent HTTP request load. That behavior does not fit here.
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. A. Datum must scale an Azure Container Apps revision according to concurrent HTTP request load. The option targets another design goal.
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. A. Datum must scale an Azure Container Apps revision according to concurrent HTTP request load. This does not satisfy that condition.
Question 20
Litware needs an autoscale trigger based on request concurrency rather than a queue or CPU metric. Choose the best change. 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. Litware must scale an Azure Container Apps revision according to concurrent HTTP request load. It is the strongest fit here.
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. Litware must scale an Azure Container Apps revision according to concurrent HTTP request load. The feature solves a different problem.
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. Litware must scale an Azure Container Apps revision according to concurrent HTTP request load. This is not the requested capability.
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. Litware must scale an Azure Container Apps revision according to concurrent HTTP request load. Its purpose differs from that need.
