{"id":12828,"date":"2026-09-15T12:36:39","date_gmt":"2026-09-15T12:36:39","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=12828"},"modified":"2026-09-15T12:36:39","modified_gmt":"2026-09-15T12:36:39","slug":"microsoft-az-204-practice-test-questions-and-exam-dumps-part-8-q141-160","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/microsoft-az-204-practice-test-questions-and-exam-dumps-part-8-q141-160\/","title":{"rendered":"Microsoft AZ-204 Practice Test Questions and Exam Dumps Part 8 Q141-160"},"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<h3><b>Q141. Which Durable Functions pattern is best suited for coordinating multiple activities in a defined sequence?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Fan-out\/fan-in pattern<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Function chaining pattern<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Monitor pattern<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Async HTTP API pattern<\/span><\/p>\n<p><b>Correct Answer: 2)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The function chaining pattern in Azure Durable Functions is designed to execute multiple activities in a specific sequence. Each activity can complete before the next activity begins, and the orchestration maintains the workflow state automatically. This is useful when one operation depends on the successful completion or output of a previous operation. For example, an application might validate an order, process payment, update inventory, and then send a confirmation. Durable Functions manage checkpoints and state, reducing the need for developers to build custom coordination logic.<\/span><\/p>\n<h3><b>Q142. In Azure Durable Functions, what is the primary purpose of an activity function?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> To store application secrets<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> To define HTTP endpoints only<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> To perform individual units of work within an orchestration<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> To manage Azure subscriptions<\/span><\/p>\n<p><b>Correct Answer: 3)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">An activity function performs a specific unit of work that is coordinated by a Durable Functions orchestrator. Activities can execute tasks such as processing data, calling an external service, sending an email, or writing information to storage. The orchestrator determines when activities should run and can use their results in subsequent steps. Keeping business operations inside activity functions helps maintain a clear separation between workflow coordination and actual work. Azure Durable Functions also handle state management and replay behavior around orchestrations, making activity functions an important building block for reliable long-running workflows.<\/span><\/p>\n<h3><b>Q143. Which Durable Functions feature is designed to maintain state for individual entities that can be accessed through operations?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Entity functions<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Timer triggers<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> HTTP triggers<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Blob triggers<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Durable entity functions are designed to maintain small amounts of state for individual entities and process operations against that state. An entity can represent concepts such as a counter, device, account, or inventory item. Instead of requiring developers to build separate state-management infrastructure, Durable Entities provide a programming model for reading, updating, and coordinating state. Operations are sent to the entity and processed sequentially for that entity. This approach is particularly useful when an application needs reliable stateful operations that can be coordinated using the Durable Functions framework.<\/span><\/p>\n<h3><b>Q144. Which Durable Functions capability should be used when an orchestration must pause until a future time?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Queue trigger<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Durable timer<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Blob trigger<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Event Grid subscription<\/span><\/p>\n<p><b>Correct Answer: 2)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A Durable timer allows a Durable Functions orchestration to pause until a specified future time without continuously consuming compute resources while waiting. This is useful for scenarios such as scheduled reminders, delayed processing, time-based approvals, or workflows that must wait for a deadline. The orchestration can create a durable timer and continue execution when that timer expires. Because the Durable Functions runtime manages orchestration state, the application does not need to maintain a continuously running process merely to wait for a future timestamp.<\/span><\/p>\n<h3><b>Q145. Where should application-specific configuration values normally be stored for an Azure Function App?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Application settings in the Function App configuration<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Source-code comments<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Function names<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> DNS records<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Application settings provide a centralized way to store configuration values for an Azure Function App. They are exposed to application code as environment variables and allow configuration to be separated from the deployed application package. This makes it easier to change settings between development, testing, and production environments without modifying source code. Sensitive values should not be embedded directly in code or configuration files. Instead, applications can use services such as Azure Key Vault together with managed identities when stronger secret-management capabilities are required.<\/span><\/p>\n<h3><b>Q146. Which deployment method can be used to deploy an Azure Functions application as a ZIP package?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> ZIP deployment<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> DNS delegation<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Network peering<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Database replication<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">ZIP deployment allows an Azure Functions application to be packaged into a ZIP archive and deployed to the Function App. This method is useful for automated deployment pipelines because the application artifacts can be prepared, packaged, and transferred consistently. It also provides a straightforward approach for deploying code without manually copying individual files. During deployment, Azure makes the application package available to the Functions runtime. ZIP deployment can therefore be integrated into development workflows and CI\/CD processes where repeatable application deployments are important.<\/span><\/p>\n<h3><b>Q147. Which Azure Functions configuration file is commonly used to configure host-level runtime behavior such as extension settings?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> package.json<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> host.json<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> index.html<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> web.config only<\/span><\/p>\n<p><b>Correct Answer: 2)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The host.json file contains configuration settings that affect the behavior of the Azure Functions host. Developers can use it to configure runtime features and settings associated with triggers and bindings, logging behavior, extensions, and other host-level functionality. Unlike application settings, which are generally environment-specific values, host.json defines behavior for the Functions runtime. Changes to host.json should therefore be tested carefully because they can affect how functions execute. The exact available settings depend on the Functions runtime version and the extensions being used by the application.<\/span><\/p>\n<h3><b>Q148. Why should developers consider function execution timeout settings when designing Azure Functions applications?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> They determine the DNS name of the function<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> They control the maximum allowed execution duration under the applicable hosting plan<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> They automatically encrypt all source code<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> They define the storage account partition key<\/span><\/p>\n<p><b>Correct Answer: 2)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure Functions have execution-duration considerations that depend on the hosting plan and configuration. Developers should understand these limits when designing workloads that perform long-running operations. A function that requires more time than the applicable execution limit may terminate before completing its work. For longer workflows, developers can use Durable Functions, queues, or other asynchronous processing patterns rather than keeping a single invocation running unnecessarily. Properly designing around execution limits helps improve reliability, scalability, and resource utilization while avoiding failures caused by unexpectedly long-running function executions.<\/span><\/p>\n<h3><b>Q149. Which Azure App Service feature can automatically remove an instance from traffic when the application is unhealthy?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Health Check<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Deployment Center<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Custom Domain<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Access Restrictions<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The App Service Health Check feature monitors a configured application endpoint and helps determine whether an application instance is healthy. If an instance repeatedly fails health checks, App Service can stop routing traffic to that unhealthy instance and take corrective action according to the platform behavior. This improves application availability when an application is deployed across multiple instances. Developers should configure the health endpoint so that it accurately reflects application readiness and important dependencies. Health Check is especially valuable for production applications where maintaining traffic only to healthy instances is important.<\/span><\/p>\n<h3><b>Q150. Which App Service capability provides built-in authentication and authorization without requiring developers to implement the complete authentication flow themselves?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Easy Auth<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Blob lifecycle management<\/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;\"> Storage Explorer<\/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 provides built-in authentication and authorization capabilities, commonly referred to as Easy Auth. This feature can integrate applications with identity providers and help protect web applications and APIs without requiring developers to implement every authentication mechanism manually. It can handle authentication workflows and make authenticated user information available to the application. This is useful when developers want to secure an App Service application while minimizing custom authentication code. Additional application-level authorization logic can still be implemented when more specific access-control requirements are necessary.<\/span><\/p>\n<h3><b>Q151. Which App Service feature allows an application to use a custom domain name such as<\/b><a href=\"http:\/\/www.example.com\"> <b>www.example.com<\/b><\/a><b>?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Deployment slot<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Custom domain<\/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;\"> Application setting<\/span><\/p>\n<p><b>Correct Answer: 2)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Custom Domains capability in Azure App Service allows an application to be accessed through a domain name owned by the organization instead of only through the default Azure-provided hostname. Developers configure the custom hostname and verify domain ownership before using it with the application. For production websites, HTTPS should also be configured so that communication between clients and the application is encrypted. Custom domains provide a professional public endpoint and can be combined with App Service TLS\/SSL features to provide secure access for users.<\/span><\/p>\n<h3><b>Q152. Which App Service setting helps keep an application continuously loaded instead of allowing the application to become idle?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Always On<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Private Endpoint<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Deployment Center<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Access Restriction<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Always On setting helps keep an App Service application loaded by preventing the application from being unloaded due to inactivity. This is particularly useful for applications where startup time is undesirable or where regular background processing requires the application to remain active. When Always On is enabled, App Service periodically sends requests to keep the application active. The feature is available only on supported App Service plans. Developers should still design applications to handle restarts because cloud applications can experience platform operations, deployments, or other events that cause instances to restart.<\/span><\/p>\n<h3><b>Q153. Which App Service feature allows an application to access resources in an Azure virtual network without placing the App Service instance directly inside that network?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> VNet Integration<\/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;\"> Custom Domain<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Deployment Slot<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">App Service VNet Integration allows an application to make outbound connections to resources accessible through an Azure virtual network. This can be useful when a web application needs to communicate with private services such as databases or internal APIs. VNet Integration does not mean that the App Service application itself becomes a traditional virtual machine inside the virtual network. Instead, it provides supported networking connectivity from the application to resources reachable through the network. This approach helps developers build applications that use private backend services while retaining App Service as the managed hosting platform.<\/span><\/p>\n<h3><b>Q154. An Azure Container Registry contains private container images. Which identity-based approach can allow an Azure resource to access the registry without storing registry credentials in application code?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Managed identity<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Public anonymous access<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Hard-coded administrator password<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> DNS alias<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A managed identity can provide an Azure resource with an identity that can be granted appropriate permissions to access Azure Container Registry. This avoids placing usernames, passwords, or other long-lived credentials directly in application code or deployment configuration. The identity can be assigned the required role, such as permission to pull images, according to the principle of least privilege. Managed identities are particularly useful when Azure services need to authenticate to other Azure resources. This approach reduces credential-management overhead and helps improve the security of automated container deployments.<\/span><\/p>\n<h3><b>Q155. An AKS cluster must pull private container images from Azure Container Registry. What is a common Azure-native approach?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Give every pod the registry administrator password<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Grant the AKS cluster identity permission to pull images from ACR<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Make all ACR repositories publicly accessible<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Store the registry password inside the container image<\/span><\/p>\n<p><b>Correct Answer: 2)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">AKS can be configured so that its identity has permission to pull container images from Azure Container Registry. This allows Kubernetes workloads to retrieve private images without making the registry publicly accessible or embedding credentials inside container images. The required permissions should be limited to the operations needed by the cluster, following least-privilege principles. This integration is useful in automated deployment environments because the cluster can authenticate to ACR using Azure identity mechanisms. It also simplifies credential management compared with distributing static registry passwords across workloads.<\/span><\/p>\n<h3><b>Q156. Which Kubernetes component is commonly used to expose HTTP or HTTPS routes from outside the cluster to services inside an AKS cluster?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> ConfigMap<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Ingress<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Secret<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> PersistentVolume<\/span><\/p>\n<p><b>Correct Answer: 2)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A Kubernetes Ingress provides rules for routing external HTTP or HTTPS traffic to services within a Kubernetes cluster. In AKS, an ingress solution can be used to define host-based or path-based routing, allowing multiple applications to share an external entry point. An ingress controller processes the defined rules and handles the actual traffic routing. This is useful when applications require web-based access from outside the cluster. Developers should select an appropriate ingress implementation based on requirements such as TLS termination, routing behavior, scalability, and integration with Azure networking services.<\/span><\/p>\n<h3><b>Q157. What is the primary purpose of a Kubernetes readiness probe?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Determine whether a container should receive traffic<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Permanently delete a failed pod<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Increase the container&#8217;s CPU limit automatically<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Create a new container image<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A Kubernetes readiness probe determines whether a container is ready to receive traffic. When a readiness check fails, Kubernetes can remove the pod from the endpoints used by a Service, preventing traffic from being sent to an application that is not ready. This is especially useful during application startup, temporary dependency failures, or controlled initialization processes. A readiness probe does not necessarily mean that the container should be restarted. Restart behavior is primarily associated with liveness checks and Kubernetes container management. Correctly configured readiness probes can improve application availability during deployments and startup periods.<\/span><\/p>\n<h3><b>Q158. What is the primary purpose of a Kubernetes liveness probe?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Determine whether a container should be restarted because it is unhealthy<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Assign a DNS name to the Service<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Store confidential configuration values<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Create a Kubernetes namespace<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A Kubernetes liveness probe helps determine whether a running container is still functioning correctly. If the liveness probe repeatedly fails according to the configured thresholds, Kubernetes can restart the affected container. This is useful when an application becomes stuck or enters a state from which it cannot recover by itself. Liveness probes are different from readiness probes: readiness determines whether traffic should be sent to a container, while liveness focuses on whether the container should continue running. Proper configuration is important because overly aggressive probes can cause healthy applications to restart unnecessarily.<\/span><\/p>\n<h3><b>Q159. Why are Kubernetes resource requests and limits specified for containers?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> To define expected and maximum resource usage such as CPU and memory<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> To configure DNS zones<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> To create storage accounts automatically<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> To encrypt Kubernetes secrets<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Kubernetes resource requests and limits help control how containers consume compute resources. A request indicates the amount of CPU or memory that a workload expects and is used by the scheduler when deciding where to place a pod. A limit establishes an upper boundary for resource consumption. Properly configured values help improve cluster resource utilization and reduce the risk that one workload consumes excessive resources. Developers should choose values based on realistic application behavior and monitor workloads over time. Resource configuration is also important for predictable scheduling and efficient AKS cluster operation.<\/span><\/p>\n<h3><b>Q160. Which Kubernetes deployment strategy updates application pods gradually while keeping the existing version available during the rollout?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Recreate deployment<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Rolling update<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Manual deletion<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Static deployment<\/span><\/p>\n<p><b>Correct Answer: 2)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A rolling update gradually replaces pods running the old application version with pods running the new version. This allows an application to remain available during deployment rather than stopping all existing instances at once. Kubernetes controls the rollout according to the Deployment configuration, including settings that determine how many pods can be unavailable or created beyond the desired count. Rolling updates are commonly used for production applications because they reduce downtime and provide a controlled deployment process. If problems occur, Kubernetes deployments can also support rollback to a previous application revision.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Microsoft AZ-204 Exam Dumps and Practice Test Dumps &nbsp; Q141. Which Durable Functions pattern is best suited for coordinating multiple activities in a defined sequence? 1) Fan-out\/fan-in pattern 2) Function chaining pattern 3) Monitor pattern 4) Async HTTP API pattern Correct Answer: 2) Explanation: The function chaining pattern in Azure Durable Functions is [&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\/12828"}],"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=12828"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/12828\/revisions"}],"predecessor-version":[{"id":12855,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/12828\/revisions\/12855"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=12828"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=12828"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=12828"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}