AZ-204 Develop Azure compute solutions Practice Test 14 — 15 Questions

Question 1

Which THREE factors should you consider when choosing between Azure Container Instances (ACI) and Azure Kubernetes Service (AKS) for a containerized workload? (Choose three.)

Accepted Answer

The need for orchestration of multiple containers. AKS provides full orchestration capabilities for managing multiple containers across a cluster, including service discovery, load balancing, and scaling. ACI is designed for single-container or simple multi-container groups without native orchestration, making AKS the appropriate choice when complex orchestration is required (A).
Azure Container Instances (ACI) has specific maximum resource limits for a single container group (e.g., 16 vCPU, 112 GiB memory), making it suitable for smaller, burstable workloads. Azure Kubernetes Service (AKS) allows for much larger, distributed applications by scaling out across multiple nodes and pods, making the overall resource capacity a key differentiator (E).
The Azure Application Gateway Ingress Controller (AGIC) is an AKS-specific feature that allows Application Gateway to act as an Ingress controller for an AKS cluster. If a workload requires this specific ingress solution, AKS is the appropriate choice, whereas ACI does not offer this native integration (D).

Answer

The restart policy for containers

Answer

The need for GPU-accelerated compute

Question 2

Which TWO Azure services can be used to trigger an Azure Function when a new blob is added to an Azure Storage container? (Choose two.)

Accepted Answer

Azure Event Grid trigger. Option A (Azure Event Grid trigger) is correct because Azure Storage integrates with Event Grid to publish a BlobCreated event when a new blob is uploaded, and an Azure Function with an Event Grid trigger subscribes to that event to fire in near real time. Option C (Azure Blob Storage trigger) is correct because it is the native Azure Functions binding that monitors a specified storage container and invokes the function whenever a new or updated blob is detected. Option B (Azure Queue Storage trigger) is not correct because it fires on messages placed in a queue, not on blob creation, unless additional code writes such messages. Option D (Azure Cosmos DB trigger) is not correct because it reacts to changes in a Cosmos DB container's change feed, not to Azure Storage blobs. Option E (HTTP trigger) is not correct because it requires an inbound HTTP request and does not natively detect new blobs.

Answer

Azure Queue Storage trigger

Answer

Azure Cosmos DB trigger

Answer

HTTP trigger

Question 3

You are developing a web application that processes images uploaded by users. The images must be resized and analyzed for offensive content before being stored. You need to implement the solution with minimal latency and cost. What should you do?

Accepted Answer

Use an Azure Function triggered by Blob Storage, with Consumption plan.. Using an Azure Function triggered by Blob Storage on a Consumption plan provides a serverless, event-driven architecture that automatically scales to process each image upload with minimal latency and cost. The Consumption plan charges only for execution time and resources used, making it cost-effective for sporadic workloads, while the Blob Storage trigger ensures immediate processing upon upload without polling or additional infrastructure.

Answer

Use Azure Batch to process images in parallel.

Answer

Use Durable Functions to orchestrate the resizing and analysis.

Answer

Use Azure Logic Apps with a trigger for each upload.

Question 4

You are deploying a containerized application to Azure Container Instances. The application requires a custom domain name and SSL/TLS certificate. What should you do?

Accepted Answer

Place an Azure Application Gateway in front of the container group.. Azure Container Instances (ACI) does not natively support custom domain names or SSL/TLS termination. By placing an Azure Application Gateway in front of the container group, you can offload SSL/TLS termination at the gateway layer, map a custom domain via the gateway's frontend IP, and route traffic to the container group's private IP. This is the recommended pattern for adding HTTPS and custom domains to ACI workloads.

Answer

Configure the container to listen on port 443 and map a custom domain.

Answer

Upload the certificate to the container and configure the web server.

Answer

Use a private endpoint with a custom domain.

Question 5

You are developing a microservices application deployed on Azure Kubernetes Service (AKS). You need to ensure that service-to-service communication is encrypted using mutual TLS (mTLS) without modifying application code. What should you do?

Accepted Answer

Deploy Azure Service Mesh and enable mTLS.. Azure Service Mesh (e.g., Open Service Mesh or Istio-based) provides a transparent infrastructure layer that can automatically inject sidecar proxies into pods and enforce mTLS for all service-to-service communication without requiring any changes to application code. This meets the requirement of encrypting traffic with mutual TLS while keeping the application code untouched.

Answer

Use Azure Application Gateway Ingress Controller with mTLS.

Answer

Enable Azure Kubernetes Service (AKS) pod-to-pod encryption.

Answer

Configure Azure Network Security Groups to enforce encryption.

Question 6

You have an Azure App Service web app that experiences high CPU usage during peak hours. You need to scale out automatically based on CPU load. What should you configure?

Accepted Answer

Configure an autoscale rule to scale out based on CPU percentage.. Azure App Service autoscale rules allow you to scale out (increase instance count) based on a metric like CPU percentage. This automatically adds more instances when CPU exceeds a threshold, distributing the load and reducing CPU usage per instance during peak hours.

Answer

Manually increase the instance count during peak hours.

Answer

Configure an autoscale rule to scale up the App Service plan.

Answer

Use Azure Front Door to distribute load across multiple instances.

Question 7

Which TWO actions should you take to ensure high availability for a stateful ASP.NET application deployed on Azure App Service?

Accepted Answer

Enable ARR Affinity (client affinity) to maintain session state.. Enabling ARR Affinity (client affinity) ensures that all requests from a given client session are routed to the same instance, preserving in-memory session state. Without this, a stateful ASP.NET application would lose session data if subsequent requests are load-balanced to different instances, causing session state errors.

Answer

Scale up the App Service plan to a higher tier.

Answer

Store session state in Azure Files share.

Answer

Disable session state to allow any instance to handle requests.

Question 8

Which THREE factors should you consider when choosing between Azure Container Instances (ACI) and Azure Kubernetes Service (AKS) for a containerized workload? (Choose three.)

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Scaling behavior (automatic vs. manual).. Option A is correct because Azure Functions on the Consumption plan provides automatic, event-driven scaling (scale controller reacts to Service Bus queue depth), whereas Azure Container Instances requires manual scaling or external orchestration, which is a key decision factor for a background message processor. Option B is correct because the Consumption plan bills per execution plus GB-s (consumption-based), while ACI bills per second for allocated vCPU and memory, making the cost model a fundamental differentiator for steady vs. bursty workloads. Option D is correct because Azure Functions has a native Service Bus trigger binding that handles message polling, peek-lock, completion/abandon, and dead-lettering automatically, whereas ACI would require you to implement the Service Bus SDK logic yourself. Option C is not a differentiator here because ACI supports custom base images but Azure Functions also supports custom containers (on Premium/Dedicated or via containerized Functions), and it is not one of the primary factors for this scenario. Option E is not a primary factor because cold start latency is a performance consideration, not a core architectural factor for choosing between these two compute options for a Service Bus background job.

Answer

Ability to use custom base images.

Answer

Cold start latency.

Question 9

Refer to the exhibit. You run the Azure CLI command shown for an Azure Function app. What is the effect of this setting?

Accepted Answer

The function app runs from a deployment package in Azure Storage.. The `--run-from-package` flag in the Azure CLI command `az functionapp config appsettings set` sets the `WEBSITE_RUN_FROM_PACKAGE` app setting to `1`. This configures the function app to run from a deployment package (a .zip file) stored in Azure Blob Storage, which improves cold-start performance and ensures all files are consistent across instances. Option D correctly identifies this behavior.

Answer

The function app uses the latest runtime version.

Answer

Remote debugging is enabled for the function app.

Answer

The function app scales out to multiple instances.

Question 10

Refer to the exhibit. You deploy this ARM template to a resource group. The template fails with a 'ResourceNotFound' error. What is the most likely cause?

Accepted Answer

The App Service plan 'myplan' does not exist in the resource group.. The ARM template references an App Service plan named 'myplan' in the 'serverFarmId' property of the Microsoft.Web/sites resource. If 'myplan' does not exist in the same resource group, the deployment fails with a 'ResourceNotFound' error because Azure Resource Manager cannot resolve the dependency on a non-existent resource. The template does not include a definition for the App Service plan, so it must already exist in the resource group.

Answer

The 'apiVersion' is incorrect.

Answer

The template is missing the 'dependsOn' property.

Answer

The 'type' property is incorrect for a web app.

Question 11

Refer to the exhibit. You run this KQL query in Azure Resource Graph Explorer. The query returns no results. What is the most likely reason?

Accepted Answer

The resource type is incorrect; it should be 'microsoft.insights/components' in lowercase.. The KQL query uses the resource type 'Microsoft.Insights/Components' with mixed case, but Azure Resource Graph Explorer requires resource types to be specified in all lowercase. The correct type is 'microsoft.insights/components'. When the case does not match, the query returns no results because Azure Resource Graph performs a case-sensitive match on the 'type' property.

Answer

The 'contains' operator is case-sensitive.

Answer

The query must specify a subscription filter.

Answer

The 'where' clause must use '== ' instead of '=='.

Question 12

Which THREE considerations are important when designing a solution using Azure Functions with a Consumption plan for a latency-sensitive application?

Accepted Answer

Cold start latency may impact initial requests.. Option A is correct because on the Consumption plan, function apps scale to zero when idle, so the first request after an idle period triggers a cold start that adds latency to that initial invocation. Option B is correct because the Consumption plan enforces a maximum function execution timeout of 10 minutes (default 5 minutes), which constrains long-running latency-sensitive workloads. Option C is correct because Consumption-plan scaling is event-driven and not instantaneous, so bursts of traffic can cause temporary latency spikes while new instances are provisioned. Option D is incorrect because Always On is a feature of App Service plans (and Premium/ Dedicated), not the Consumption plan, and cannot be enabled there. Option E is incorrect because pre-warmed instances are a Premium plan capability, not available on the Consumption plan.

Answer

Always-on feature must be enabled to avoid cold starts.

Answer

Pre-warmed instances can be configured to reduce latency.

Question 13

You are developing a solution that uses Azure Container Registry (ACR) to store Docker images. You need to ensure that only authorized users can deploy images from ACR to an AKS cluster. What should you do?

Accepted Answer

Use the AKS cluster's managed identity with AcrPull role assignment.. Using an AKS cluster's managed identity with the AcrPull role assignment enables secure, password-less authentication to ACR. Option A is incorrect because AKS RBAC controls Kubernetes resources, not ACR permissions. Option B is incorrect because storing ACR credentials as Kubernetes secrets is less secure and requires manual management. Option D is incorrect because enabling the admin account on ACR is a shared credential approach that is not recommended for production.

Answer

Configure AKS RBAC to limit image pull permissions.

Answer

Use Kubernetes secrets to store ACR credentials.

Answer

Enable the admin account on ACR and use the credentials in AKS.

Question 14

You need to run a batch job every night that processes data from Azure Blob Storage and writes results to Azure SQL Database. The job may run for up to 2 hours. Which Azure service should you use?

Accepted Answer

Azure Container Instances.. Azure Container Instances (ACI) is the correct choice because it allows you to run a containerized batch job on-demand without managing underlying infrastructure. The job's duration of up to 2 hours fits well within ACI's default timeout of 60 minutes (configurable up to 24 hours), and you can trigger it nightly via a scheduler like Azure Logic Apps or a timer-triggered Azure Function. ACI provides fast startup, per-second billing, and direct access to Azure Blob Storage and SQL Database via connection strings or managed identities.

Answer

Azure Logic Apps.

Answer

Azure Batch.

Answer

Azure Functions (Consumption plan).

Question 15

You are designing a solution that uses Azure Functions to process events from Azure Event Hubs. The function must process events in order and exactly once per partition. What should you do?

Accepted Answer

Use the Event Hubs trigger for Azure Functions with default configuration.. The Event Hubs trigger for Azure Functions, by default, processes events in order and exactly once per partition. It uses checkpointing to track the offset of the last successfully processed event, ensuring that each event is processed only once and in sequence within a partition. This default behavior aligns with the requirement without needing additional configuration.

Answer

Enable session state in the function app.

Answer

Use a Service Bus queue trigger with a singleton lock.

Answer

Disable checkpointing to ensure no duplicates.