{"id":12824,"date":"2026-09-15T12:37:22","date_gmt":"2026-09-15T12:37:22","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=12824"},"modified":"2026-09-15T12:37:22","modified_gmt":"2026-09-15T12:37:22","slug":"microsoft-az-204-practice-test-questions-and-exam-dumps-part-4-q61-80","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/microsoft-az-204-practice-test-questions-and-exam-dumps-part-4-q61-80\/","title":{"rendered":"Microsoft AZ-204 Practice Test Questions and Exam Dumps Part 4 Q61-80"},"content":{"rendered":"<p><b>View Full <a href=\"https:\/\/www.examlabs.com\/az-204-exam-dumps\">Microsoft AZ-204 Exam Dumps<\/a> and Practice Test Dumps<\/b><\/p>\n<p>&nbsp;<\/p>\n<p><b>Q61. Which Azure service allows an application to securely retrieve secrets without storing credentials directly in source code?<\/b><\/p>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Azure CDN<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Azure Key Vault<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Azure Queue Storage<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Azure Monitor<\/span><\/p>\n<p><b>Correct Answer: 2)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure Key Vault provides secure storage and management for secrets, keys, and certificates used by applications. Instead of placing passwords, connection strings, or other sensitive values directly in source code, an application can retrieve them from Key Vault when needed. Access can be controlled through Microsoft Entra ID and role-based access control. Managed identities can further reduce the need for applications to store authentication credentials. Key Vault also supports secret rotation and centralized management. Therefore, when an application needs to securely retrieve sensitive configuration values without embedding credentials in source code, Azure Key Vault is the appropriate service.<\/span><\/p>\n<p><b>Q62. Which Azure App Service feature allows an application to automatically scale out when demand increases?<\/b><\/p>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Autoscale<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Deployment slots<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Custom domains<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> App settings<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure App Service Autoscale can automatically adjust the number of application instances based on configured rules and workload metrics. When application demand increases, additional instances can be added to handle the increased workload. When demand decreases, instances can be removed to reduce resource consumption. Scaling rules can use metrics such as CPU utilization, memory usage, or request counts depending on the configuration. Autoscale is particularly useful for applications whose traffic changes throughout the day or during specific events. Therefore, when an application must automatically scale out in response to increased demand, App Service Autoscale is the correct feature.<\/span><\/p>\n<p><b>Q63. Which Azure App Service deployment strategy allows a developer to validate an application in staging before swapping it into production?<\/b><\/p>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Azure CDN<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Deployment slots<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Azure Storage<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Application Insights<\/span><\/p>\n<p><b>Correct Answer: 2)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Deployment slots allow an Azure App Service application to have multiple environments, such as production and staging. Developers can deploy a new application version to the staging slot and test it without immediately replacing the production version. Once testing is successful, the staging slot can be swapped with production. This approach helps minimize downtime and provides a safer deployment process. Slot-specific settings can also remain associated with their original environments when configured appropriately. Therefore, deployment slots are the appropriate App Service feature when a developer needs to validate an application in staging before promoting it to production.<\/span><\/p>\n<p><b>Q64. Which Azure service provides a managed message broker with queues and topics that support advanced messaging scenarios?<\/b><\/p>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Azure Blob Storage<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Azure Service Bus<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Azure App Configuration<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Azure CDN<\/span><\/p>\n<p><b>Correct Answer: 2)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure Service Bus provides managed enterprise messaging through queues and topics. It supports advanced messaging capabilities such as dead-letter queues, duplicate detection, message sessions, transactions, and publish-subscribe communication. Queues allow messages to be processed asynchronously, while topics can distribute messages to multiple subscriptions. Service Bus is useful when applications require reliable communication between loosely coupled components. It is more feature-rich than simple Azure Storage queues and is appropriate for enterprise messaging scenarios. Therefore, when an application requires a managed message broker supporting advanced queues and topics, Azure Service Bus is the correct Azure service.<\/span><\/p>\n<p><b>Q65. Which Azure messaging service is best suited for simple asynchronous communication between application components?<\/b><\/p>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Azure Queue Storage<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Azure Key Vault<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Azure Front Door<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Azure Monitor<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure Queue Storage provides a simple and scalable mechanism for asynchronous communication between application components. A producer places messages into a queue, and a consumer retrieves and processes those messages later. This decouples application components and allows them to operate independently. Queue Storage is particularly useful for background tasks, workload buffering, and simple task-processing scenarios. It does not provide all the advanced messaging features available in Azure Service Bus. Therefore, when an application needs straightforward asynchronous communication and does not require advanced enterprise messaging capabilities, Azure Queue Storage is an appropriate choice.<\/span><\/p>\n<p><b>Q66. Which Azure service is designed for event-driven applications that need to react when resources or services generate events?<\/b><\/p>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Azure Event Grid<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Azure SQL Database<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Azure Files<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Azure Virtual Machines<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure Event Grid is designed for event-driven architectures in which applications need to respond to events generated by Azure resources or supported external sources. For example, an application can respond when a blob is created, a resource changes state, or another service publishes an event. Event Grid routes events to handlers such as Azure Functions, webhooks, and other supported services. It is focused on event notification and routing rather than traditional message queuing. Therefore, when an application needs to react automatically to events generated by Azure resources or services, Azure Event Grid is the appropriate solution.<\/span><\/p>\n<p><b>Q67. Which Azure Functions feature allows a function to receive data from an external service without writing extensive connection code?<\/b><\/p>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Input binding<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Deployment slot<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Autoscale rule<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Custom domain<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">An input binding allows an Azure Function to receive data from a supported external service through configuration rather than requiring extensive service-specific connection code. Depending on the trigger and binding configuration, the function can receive data from services such as Azure Storage or Cosmos DB. Bindings help simplify integration and allow developers to focus on business logic. They can also reduce repetitive code used to connect to external resources. Therefore, when a function needs to obtain data from a supported external service through a simplified integration mechanism, an input binding is the appropriate Azure Functions feature.<\/span><\/p>\n<p><b>Q68. Which Azure Functions feature can send data or results from a function to another supported Azure service?<\/b><\/p>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Output binding<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Timer trigger<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> HTTP authorization<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Function host<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">An output binding allows an Azure Function to send data or results to a supported destination without requiring developers to implement all the underlying service interaction manually. Depending on the configuration, an output binding can send information to services such as Azure Storage, Service Bus, or other supported destinations. This simplifies common integration scenarios and allows developers to concentrate on application logic. Input bindings retrieve data, while output bindings send data. Therefore, when the requirement is to send function output to a supported Azure service using a simplified integration mechanism, an output binding is the correct choice.<\/span><\/p>\n<p><b>Q69. Which Azure Functions plan is designed to support long-running functions and features such as pre-warmed instances?<\/b><\/p>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Consumption plan<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Premium plan<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Basic storage plan<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Free App Service plan<\/span><\/p>\n<p><b>Correct Answer: 2)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Azure Functions Premium plan provides features designed for applications that require more predictable performance and advanced hosting capabilities. It supports pre-warmed instances, which can help reduce cold-start delays, and supports longer-running workloads than the traditional Consumption plan. Premium also provides additional scaling and networking capabilities that can be important for enterprise applications. The Consumption plan is attractive for workloads that benefit from serverless execution and pay-per-use behavior, while Premium is better suited to workloads requiring additional control and performance features. Therefore, the Premium plan is the appropriate choice for long-running functions and pre-warmed instances.<\/span><\/p>\n<p><b>Q70. Which Azure Functions hosting option is generally designed for event-driven workloads with automatic scaling and pay-per-execution characteristics?<\/b><\/p>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Consumption plan<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Dedicated physical server<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Azure DNS plan<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Storage account plan<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Consumption plan is designed for serverless Azure Functions workloads where resources can automatically scale according to incoming events and executions. It is well suited to applications with variable or intermittent workloads because capacity can adjust as demand changes. Billing is based on execution and resource consumption according to the applicable plan terms. This model allows developers to focus on function code without managing dedicated infrastructure. Other plans provide additional capabilities for workloads requiring more predictable performance or networking features. Therefore, for event-driven workloads that benefit from automatic scaling and serverless execution, the Consumption plan is an appropriate Azure Functions hosting option.<\/span><\/p>\n<p><b>Q71. Which Azure Functions trigger is designed to execute a function when a new blob is created or updated in Azure Blob Storage?<\/b><\/p>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Blob trigger<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Timer trigger<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> HTTP trigger<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Queue trigger<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Blob trigger allows an Azure Function to execute in response to changes involving blobs in Azure Blob Storage. This can be useful when an application needs to automatically process uploaded files, transform images, inspect documents, or perform other operations after blob data becomes available. The trigger connects the function workflow with blob activity instead of relying on an HTTP request or scheduled execution. Developers can use bindings alongside the trigger to access blob content efficiently. Therefore, when a function should execute because a blob is created or updated in Azure Blob Storage, the Blob trigger is the appropriate choice.<\/span><\/p>\n<p><b>Q72. Which Azure Functions trigger is commonly used to execute code when a message becomes available in Azure Service Bus?<\/b><\/p>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Service Bus trigger<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Timer trigger<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> HTTP trigger<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Blob trigger<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Service Bus trigger allows Azure Functions to respond to messages arriving in an Azure Service Bus queue or topic subscription. This is useful for implementing asynchronous and event-driven application processing. A producer can place messages into Service Bus, while the function processes them independently without requiring direct communication between application components. Service Bus provides advanced messaging features such as dead-lettering and message sessions, which can complement function-based processing. Therefore, when an Azure Function needs to execute in response to messages arriving through an Azure Service Bus queue or topic subscription, the Service Bus trigger is the appropriate trigger type.<\/span><\/p>\n<p><b>Q73. Which Azure Functions trigger can execute a function when an event is published through Azure Event Grid?<\/b><\/p>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Event Grid trigger<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Queue trigger<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Timer trigger<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Blob trigger<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Event Grid trigger enables an Azure Function to execute when an event is delivered through Azure Event Grid. This supports event-driven architectures where applications react automatically to changes or actions occurring in Azure resources or external services. For example, a function can respond to events associated with storage operations or other supported publishers. Event Grid handles event routing, while the function provides the processing logic. This combination can reduce the need for continuously running polling processes. Therefore, when an Azure Function must execute in response to an event delivered through Azure Event Grid, the Event Grid trigger is the appropriate option.<\/span><\/p>\n<p><b>Q74. Which Azure service can provide distributed tracing and dependency information for an application?<\/b><\/p>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Application Insights<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Azure Queue Storage<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Azure DNS<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Azure Container Registry<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Application Insights provides application telemetry that can help developers analyze requests, dependencies, exceptions, performance, and distributed application behavior. Dependency tracking can show how an application interacts with databases, APIs, and other services. This information is useful for identifying slow components and understanding how requests move through distributed systems. Application Insights integrates with Azure Monitor and can provide queries and visualizations for troubleshooting. It is therefore more appropriate for application-level observability than storage or networking services. When a developer needs distributed tracing and dependency information for an application, Application Insights is the correct choice.<\/span><\/p>\n<p><b>Q75. Which Azure service can collect logs and provide a query environment for analyzing telemetry from multiple resources?<\/b><\/p>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Log Analytics workspace<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Azure CDN<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Azure Files<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Azure Container Registry<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A Log Analytics workspace provides a centralized environment for collecting and querying log data from supported Azure resources, applications, and services. It works closely with Azure Monitor and can use Kusto Query Language, or KQL, to analyze telemetry. Developers and administrators can use queries to identify errors, investigate resource behavior, analyze trends, and troubleshoot issues. Centralizing logs makes it easier to correlate information from multiple resources rather than reviewing each resource independently. Therefore, when the requirement is to collect and query logs from multiple sources in a centralized environment, a Log Analytics workspace is the appropriate Azure service.<\/span><\/p>\n<p><b>Q76. Which Azure service allows developers to store container images privately before deploying them to container platforms?<\/b><\/p>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Azure Container Registry<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Azure Application Insights<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Azure Event Grid<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Azure Service Bus<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure Container Registry provides private repositories for storing and managing container images and other supported artifacts. Developers can build container images, push them to an Azure Container Registry, and later retrieve those images for deployment to services such as Azure Container Instances or Azure Kubernetes Service. ACR integrates with Azure identity and security capabilities, allowing organizations to control who can access container images. Keeping images in a private registry is useful when applications contain proprietary code or configurations. Therefore, Azure Container Registry is the appropriate service for privately storing container images before deploying them to Azure container platforms.<\/span><\/p>\n<p><b>Q77. Which Azure Container Registry capability can automatically build a container image from source code?<\/b><\/p>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> ACR Tasks<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Azure DNS<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Blob soft delete<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> App Service slots<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">ACR Tasks provides automated container image build capabilities within Azure Container Registry. Developers can configure tasks to build container images from source code or base images and push the resulting images into a registry. This can help automate parts of the container development lifecycle and reduce the need for developers to manually execute image-building commands. Tasks can also support automated rebuild scenarios when base images are updated, depending on configuration. Therefore, when a developer needs Azure Container Registry to automatically build container images from source code or related inputs, ACR Tasks is the appropriate capability.<\/span><\/p>\n<p><b>Q78. Which Azure service provides managed Kubernetes orchestration for deploying containerized applications across a cluster?<\/b><\/p>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Azure Kubernetes Service<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Azure Blob Storage<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Azure Functions<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Azure App Configuration<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure Kubernetes Service provides managed Kubernetes orchestration for containerized workloads. Kubernetes organizes containers into workloads such as pods and deployments and provides capabilities for scheduling, service discovery, scaling, rolling updates, and health management. AKS reduces the administrative effort required to operate the Kubernetes control plane while allowing developers to use standard Kubernetes APIs and tools. It is especially useful when applications consist of multiple containerized components that need coordinated deployment and scaling. Therefore, when the requirement is managed Kubernetes orchestration for containerized applications running across a cluster, Azure Kubernetes Service is the correct Azure service.<\/span><\/p>\n<p><b>Q79. Which Azure Container Instances restart policy is appropriate for a container that should run only once and should not restart after successful completion?<\/b><\/p>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Always<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> OnFailure<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Never<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Continuous<\/span><\/p>\n<p><b>Correct Answer: 3)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Never restart policy is appropriate when an Azure Container Instance should execute a workload and remain stopped after the container exits. This can be useful for one-time jobs, batch operations, or other tasks that are expected to complete once. The Always policy is intended for workloads that should continuously restart, while OnFailure is useful when a container should restart after an unsuccessful termination. Choosing the correct policy depends on how the containerized workload is expected to behave after completion. Therefore, for a one-time container that should not restart after successful completion, the Never restart policy is appropriate.<\/span><\/p>\n<p><b>Q80. Which Azure Container Instances restart policy is most appropriate when a container should restart only if it terminates with an error?<\/b><\/p>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Never<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Always<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> OnFailure<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Manual<\/span><\/p>\n<p><b>Correct Answer: 3)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The OnFailure restart policy instructs Azure Container Instances to restart a container when it terminates unsuccessfully. This policy is useful for batch jobs or task-oriented workloads where successful completion should leave the container stopped, but an error should cause another attempt. It avoids continuously restarting containers that have completed successfully while still providing automatic recovery from failures. The Always policy is more appropriate for continuously running workloads, while Never prevents automatic restarts. Therefore, when a container should restart only after an unsuccessful execution, the OnFailure restart policy is the appropriate choice.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Microsoft AZ-204 Exam Dumps and Practice Test Dumps &nbsp; Q61. Which Azure service allows an application to securely retrieve secrets without storing credentials directly in source code? 1) Azure CDN 2) Azure Key Vault 3) Azure Queue Storage 4) Azure Monitor Correct Answer: 2) Explanation: Azure Key Vault provides secure storage and management [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/12824"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=12824"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/12824\/revisions"}],"predecessor-version":[{"id":12859,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/12824\/revisions\/12859"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=12824"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=12824"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=12824"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}