{"id":12836,"date":"2026-09-15T12:34:47","date_gmt":"2026-09-15T12:34:47","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=12836"},"modified":"2026-09-15T12:34:47","modified_gmt":"2026-09-15T12:34:47","slug":"microsoft-az-204-practice-test-questions-and-exam-dumps-part-15-q281-300","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/microsoft-az-204-practice-test-questions-and-exam-dumps-part-15-q281-300\/","title":{"rendered":"Microsoft AZ-204 Practice Test Questions and Exam Dumps Part 15 Q281-300"},"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>Q281. Which Azure Functions feature is used to send data to an external service after a function executes?<\/b><\/h3>\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;\"> Output binding<\/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;\"> Deployment slot<\/span><\/p>\n<p><b>Correct Answer: 2)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">An Azure Functions output binding allows a function to send or write data to an external resource without requiring developers to implement all of the underlying connection and client-management code manually. Output bindings can be used with supported services such as Azure Storage, queues, Event Hubs, and other Azure resources. This simplifies integration and reduces boilerplate code within the function. Input bindings perform the opposite role by retrieving data for a function. Timer triggers control when functions execute, while deployment slots support application deployment and testing. Therefore, an output binding is the correct feature for sending function results to an external service.<\/span><\/p>\n<h3><b>Q282. Which Azure Functions pattern is designed to execute multiple independent activities in parallel and then combine their results?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Fan-out\/fan-in<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Function chaining<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Retry pattern<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> HTTP polling<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Durable Functions fan-out\/fan-in pattern is designed for scenarios where multiple independent operations can execute concurrently and their results must later be combined. The orchestrator first starts several activity functions, allowing them to run in parallel, and then waits for all activities to complete before processing their results. This can improve efficiency when tasks do not depend on one another. Function chaining is more appropriate when activities must execute sequentially. Retry patterns address transient failures, while HTTP polling is used for monitoring long-running operations. Therefore, fan-out\/fan-in is the correct Durable Functions pattern for parallel processing followed by aggregation.<\/span><\/p>\n<h3><b>Q283. Which Durable Functions pattern continuously checks the status of an external operation until it completes?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Function chaining<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Fan-out\/fan-in<\/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;\"> Singleton pattern<\/span><\/p>\n<p><b>Correct Answer: 3)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Durable Functions monitor pattern is used when an orchestration needs to periodically check the status of an external process or condition. The orchestration can use durable timers between checks, allowing it to wait efficiently without continuously consuming execution resources. Once the monitored operation reaches the desired state, the orchestration can continue or complete. Function chaining executes activities sequentially, fan-out\/fan-in coordinates parallel work, and singleton patterns focus on limiting concurrent orchestration instances. Therefore, the monitor pattern is the appropriate Durable Functions design for repeatedly checking an external operation until a condition is satisfied.<\/span><\/p>\n<h3><b>Q284. Which Durable Functions capability allows an orchestration to wait for information provided by an external system?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> External event<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Output binding<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Queue trigger<\/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;\">Durable Functions external events allow an orchestration to pause and wait for a notification from an external system or application. The external system can signal the orchestration when an expected event occurs, allowing the workflow to continue from that point. This is useful for human approval processes, asynchronous callbacks, or workflows that depend on information generated outside the orchestration itself. Output bindings send data to external resources, queue triggers start functions when queue messages arrive, and deployment slots support application deployment. Therefore, an external event is the correct Durable Functions feature for receiving information from an outside system.<\/span><\/p>\n<h3><b>Q285. Which Durable Functions feature allows an orchestration to call another orchestration as a reusable workflow component?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Durable timer<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Sub-orchestration<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Function key<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Input binding<\/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 Functions sub-orchestration allows one orchestration to invoke another orchestration as part of a larger workflow. This is useful when a particular workflow contains a reusable sequence of operations that can be separated into its own orchestration. Sub-orchestrations can improve organization, maintainability, and reuse in complex applications. Durable timers provide scheduled delays, function keys help authorize function requests, and input bindings retrieve data from supported resources. Therefore, sub-orchestration is the correct feature when a Durable Functions workflow needs to call another orchestration as a component of its processing.<\/span><\/p>\n<h3><b>Q286. Why must Durable Functions orchestrator code avoid non-deterministic operations such as generating random values directly?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> They prevent Azure Storage from working<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> They can produce different results when the orchestration is replayed<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> They disable function bindings<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> They automatically delete orchestration history<\/span><\/p>\n<p><b>Correct Answer: 2)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Durable Functions orchestrators can replay their execution history to reconstruct the current state of a workflow. Because of this behavior, orchestrator code must be deterministic. Operations that can produce different results during replay, such as directly generating random values, reading the current system time incorrectly, or making uncontrolled external calls, can cause inconsistent workflow behavior. Durable Functions provides specialized APIs for certain operations that need deterministic behavior. Azure Storage remains available, bindings are not disabled, and orchestration history is not automatically deleted because of non-deterministic code. Therefore, avoiding non-deterministic operations prevents replay from producing inconsistent results.<\/span><\/p>\n<h3><b>Q287. Where can Azure Functions application settings be configured for a Function App?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Function App Configuration<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Azure DNS zones only<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Blob container metadata only<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Application Insights logs only<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure Functions application settings can be configured through the Function App&#8217;s Configuration settings in Azure. These settings are commonly used for environment-specific values such as connection strings, feature configuration, service endpoints, and other application settings. They can be exposed to the function application through environment variables. Sensitive values should be protected appropriately, and managed identities can often reduce the need to store credentials. DNS zones manage name resolution, Blob metadata stores information associated with blobs, and Application Insights provides monitoring data. Therefore, Function App Configuration is the correct location for managing application settings.<\/span><\/p>\n<h3><b>Q288. Which App Service feature allows a web application to receive traffic from a virtual network while maintaining access to Azure resources 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;\"> Deployment slot<\/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;\"> Health Check<\/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 running in Azure App Service to make outbound connections to resources accessible through an Azure virtual network. This is useful when an application needs to communicate securely with private resources such as databases, internal APIs, or services hosted within a virtual network. VNet Integration primarily supports outbound connectivity from the application rather than making the App Service itself directly reachable through the virtual network. Deployment slots support application versioning, custom domains provide friendly web addresses, and Health Check monitors application availability. Therefore, VNet Integration is the correct feature for outbound access to virtual-network resources.<\/span><\/p>\n<h3><b>Q289. Which App Service feature can restrict incoming requests based on IP addresses or virtual network rules?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Access restrictions<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Always On<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Application settings<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Deployment slots<\/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 access restrictions allow administrators to control which incoming requests are permitted to reach an application. Rules can be configured using IP addresses, virtual network-based conditions, and other supported criteria. This is useful for limiting access to trusted networks, corporate environments, or specific client addresses. Always On keeps an application loaded and available but does not primarily provide network filtering. Application settings store configuration values, while deployment slots provide separate application environments for deployment and testing. Therefore, access restrictions are the appropriate App Service feature for controlling inbound traffic based on network rules.<\/span><\/p>\n<h3><b>Q290. Which App Service feature can automatically provide an HTTPS certificate for a custom domain under supported conditions?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Managed certificate<\/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;\"> Service Bus topic<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Azure Table Storage<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">An App Service managed certificate can provide a managed TLS certificate for supported custom-domain scenarios. This reduces the administrative work associated with obtaining and renewing certificates manually. HTTPS encryption protects communication between clients and the web application, while App Service handles supported certificate lifecycle operations. Queue triggers process messages, Service Bus topics support messaging patterns, and Table Storage provides NoSQL key-value storage. Certificate availability depends on the domain configuration and supported App Service requirements. Therefore, the managed certificate feature is the correct choice when an application needs a supported HTTPS certificate with simplified certificate management.<\/span><\/p>\n<h3><b>Q291. Which App Service feature keeps an application loaded to help prevent delays caused by application initialization after periods of inactivity?<\/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;\"> Always On<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Access restrictions<\/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: 2)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The App Service Always On feature keeps the application loaded by periodically sending requests to prevent the application from becoming unloaded due to inactivity. This can reduce startup delays for applications that require initialization before serving requests. Always On is particularly useful for applications where consistent response times are important and is available only with supported App Service plans. Health Check is used to monitor application health, access restrictions control incoming traffic, and custom domains provide user-friendly host names. Therefore, Always On is the appropriate feature for keeping an App Service application continuously active.<\/span><\/p>\n<h3><b>Q292. Which App Service feature can verify application availability by periodically sending requests to a configured health-check path?<\/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;\"> Always On<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Deployment slot setting<\/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;\">App Service Health Check periodically sends requests to a configured application path and uses the responses to determine whether an application instance is healthy. This can help Azure identify unhealthy instances and improve application availability by removing problematic instances from traffic according to the service&#8217;s behavior. Health Check is different from Always On, which focuses on keeping the application loaded. Deployment slot settings control configuration behavior between slots, while custom domains provide alternative host names. Therefore, Health Check is the correct App Service feature when application availability needs to be monitored through a specific endpoint.<\/span><\/p>\n<h3><b>Q293. Which Azure Container Registry feature can automatically trigger an action when an image is pushed to a repository?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Webhook<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> PersistentVolumeClaim<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Health probe<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> App Service slot<\/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 webhooks can notify external systems when specific registry events occur, such as an image being pushed. This enables integration with deployment systems, automation workflows, and other services that need to respond to registry activity. For example, a webhook can notify an external deployment process after a new container image becomes available. PersistentVolumeClaims are Kubernetes storage requests, health probes monitor application conditions, and App Service slots support deployment strategies. Therefore, an ACR webhook is the appropriate feature when an external action or notification should occur after a container registry event.<\/span><\/p>\n<h3><b>Q294. Which Azure Container Registry feature provides fine-grained permissions for specific repositories?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Repository-scoped access token<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> App Service Health Check<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Azure Monitor alert<\/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;\">Azure Container Registry repository-scoped access tokens can provide more granular permissions than broad registry-level access. They allow administrators to define access for specific repositories and assign actions such as reading or writing according to the application&#8217;s requirements. This is useful when different teams, services, or automation processes should have access only to particular repositories. Health Check monitors App Service applications, Azure Monitor alerts detect conditions based on monitoring data, and deployment slots support application deployment. Therefore, repository-scoped access is the appropriate approach when container image permissions need to be restricted to selected repositories.<\/span><\/p>\n<h3><b>Q295. Which Azure Container Registry feature provides private network connectivity to the registry through an Azure virtual network?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Public IP restriction only<\/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 slot<\/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;\">An Azure Container Registry Private Endpoint provides private connectivity to a registry through an Azure virtual network using a private IP address. This allows workloads such as virtual machines, AKS clusters, or other supported resources to communicate with the registry without requiring public network exposure. Private connectivity can help reduce attack surface and support network-isolation requirements. Public IP restrictions provide access controls but do not create the same private endpoint architecture. Deployment slots are related to App Service, while Application Insights provides application monitoring. Therefore, Private Endpoint is the correct feature for private network connectivity to Azure Container Registry.<\/span><\/p>\n<h3><b>Q296. Which Kubernetes resource specifies CPU and memory requirements that help the scheduler determine where a Pod should run?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Resource requests<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> ConfigMap<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Service<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Ingress<\/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 specify the minimum amount of CPU or memory a container requires. The Kubernetes scheduler uses these requests when deciding which node has sufficient available capacity to host a Pod. Properly configured requests help Kubernetes make more predictable scheduling decisions and allow cluster resources to be allocated efficiently. Resource limits serve a different purpose by defining the maximum amount of a resource a container can consume. ConfigMaps store configuration data, Services provide networking, and Ingress handles HTTP routing. Therefore, resource requests are the correct mechanism for communicating a Pod&#8217;s required CPU and memory capacity to the Kubernetes scheduler.<\/span><\/p>\n<h3><b>Q297. Which Kubernetes setting limits the maximum CPU or memory a container can consume?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Resource requests<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Resource limits<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Service selectors<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Pod labels<\/span><\/p>\n<p><b>Correct Answer: 2)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Kubernetes resource limits define the maximum amount of CPU or memory that a container is permitted to consume. Setting appropriate limits can prevent one workload from consuming excessive resources and negatively affecting other applications running on the same node. Resource requests specify the amount of capacity needed for scheduling, while limits establish an upper boundary for consumption. Service selectors identify Pods for networking, and labels provide metadata used for selection and organization. Therefore, resource limits are the correct Kubernetes mechanism for restricting the maximum CPU or memory consumption of a container.<\/span><\/p>\n<h3><b>Q298. Which Kubernetes deployment strategy gradually replaces old Pods with new Pods to reduce application downtime?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Recreate<\/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 replacement<\/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 Kubernetes rolling update gradually replaces existing Pods with new versions during an application update. This approach helps maintain application availability because old and new Pods can coexist temporarily while the update progresses. Deployment configuration can control how many Pods are unavailable or can be created during the update. The Recreate strategy stops existing Pods before creating new ones and can therefore cause downtime. Manual replacement does not provide the automated rollout behavior offered by Kubernetes Deployments. Therefore, a rolling update is the appropriate strategy for gradually replacing old application Pods while minimizing service interruption.<\/span><\/p>\n<h3><b>Q299. Which Kubernetes command concept is used to check whether a Deployment rollout has successfully completed?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Rollout status<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> ConfigMap reload<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Service discovery<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Secret rotation<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Kubernetes rollout status functionality can be used to monitor whether a Deployment has successfully progressed to the desired state. During an update, Kubernetes gradually replaces Pods according to the Deployment&#8217;s rollout strategy. Checking rollout status helps administrators and automation systems determine whether the new version has become available and whether the deployment is progressing correctly. ConfigMaps manage configuration, service discovery supports networking, and Secret rotation concerns sensitive credentials. Therefore, rollout status is the appropriate mechanism for determining whether a Kubernetes Deployment update has completed successfully.<\/span><\/p>\n<h3><b>Q300. Which Azure service can collect platform metrics, logs, and diagnostic information from Azure resources for centralized monitoring?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Azure Monitor<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Azure Container Registry<\/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 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 Monitor provides centralized monitoring capabilities for Azure resources and applications. It can collect metrics, activity logs, platform logs, and diagnostic information, allowing administrators and developers to analyze resource health and identify operational issues. Azure Monitor can work with Log Analytics for querying and analyzing collected log data and can generate alerts when specified conditions occur. Azure Container Registry stores container images, Queue Storage provides asynchronous messaging, and App Configuration manages application settings. Therefore, Azure Monitor is the correct service when centralized collection and analysis of Azure resource monitoring data is required.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Microsoft AZ-204 Exam Dumps and Practice Test Dumps &nbsp; Q281. Which Azure Functions feature is used to send data to an external service after a function executes? 1) Input binding 2) Output binding 3) Timer trigger 4) Deployment slot Correct Answer: 2) Explanation: An Azure Functions output binding allows a function to send [&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\/12836"}],"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=12836"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/12836\/revisions"}],"predecessor-version":[{"id":12848,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/12836\/revisions\/12848"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=12836"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=12836"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=12836"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}