{"id":12834,"date":"2026-09-15T12:35:09","date_gmt":"2026-09-15T12:35:09","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=12834"},"modified":"2026-09-15T12:35:09","modified_gmt":"2026-09-15T12:35:09","slug":"microsoft-az-204-practice-test-questions-and-exam-dumps-part-13-q241-260","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/microsoft-az-204-practice-test-questions-and-exam-dumps-part-13-q241-260\/","title":{"rendered":"Microsoft AZ-204 Practice Test Questions and Exam Dumps Part 13 Q241-260"},"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>Q241. Which Azure service provides a globally distributed entry point for web applications with intelligent routing?<\/b><\/h3>\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 Front Door<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Azure Table Storage<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Azure Files<\/span><\/p>\n<p><b>Correct Answer: 2)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure Front Door provides a globally distributed entry point for web applications and APIs. It can route incoming HTTP and HTTPS requests to backend services based on factors such as performance, availability, and routing configuration. Front Door can also provide capabilities such as global load balancing, TLS termination, caching integration, and application-level traffic management. It is useful for applications that need improved availability and performance across geographic regions. Queue Storage is designed for asynchronous messaging, while Table Storage and Azure Files provide data storage capabilities. Therefore, Azure Front Door is the appropriate service for globally distributed web application routing.<\/span><\/p>\n<h3><b>Q242. Which Azure Front Door capability can route users to the healthiest available backend?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Health probes<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Blob versioning<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Queue triggers<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Cosmos DB TTL<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure Front Door uses health probes to determine whether configured backend endpoints are available and healthy. The service can use this health information when making routing decisions, helping direct traffic away from unhealthy endpoints. This is particularly valuable for applications deployed across multiple regions or backend instances because it improves resilience and availability. Blob versioning manages previous versions of storage objects, Queue triggers are associated with Azure Functions messaging workflows, and Cosmos DB TTL automatically expires data. Therefore, health probes are the appropriate Front Door capability for monitoring backend availability and supporting intelligent routing decisions.<\/span><\/p>\n<h3><b>Q243. An application needs to distribute HTTP requests among multiple backend instances based on performance and availability. Which Azure service should be used?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Azure Front Door<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Azure Table Storage<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Azure Key Vault<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Azure Queue Storage<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure Front Door can distribute HTTP and HTTPS traffic among multiple backend endpoints using global routing capabilities. It can consider backend health and configured routing behavior to direct requests toward appropriate endpoints. This makes it useful for applications deployed across multiple regions or backend environments. Front Door operates at the application layer and is designed for global web traffic management. Azure Table Storage is a NoSQL data store, Key Vault manages secrets and cryptographic material, and Queue Storage provides asynchronous messaging. Therefore, Azure Front Door is the best choice when an application requires global HTTP request distribution across multiple backend instances.<\/span><\/p>\n<h3><b>Q244. Which Azure Key Vault object is specifically designed to store passwords, connection strings, and API keys?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Certificate<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Key<\/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;\"> Managed identity<\/span><\/p>\n<p><b>Correct Answer: 3)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure Key Vault secrets are designed to securely store sensitive values such as passwords, connection strings, API keys, and other application secrets. Applications can retrieve these values at runtime rather than embedding them directly in source code or configuration files. Key Vault also supports keys for cryptographic operations and certificates for certificate management, but those objects have different purposes. Managed identities provide an identity for Azure resources and are not themselves secret containers. Using Key Vault secrets with managed identities can help applications access protected configuration without storing credentials in code. Therefore, Secret is the correct Key Vault object for passwords and similar sensitive values.<\/span><\/p>\n<h3><b>Q245. Which Azure feature allows an App Service application to access Azure Key Vault without storing credentials in application configuration?<\/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;\"> Blob lease<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> SAS token<\/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;\">A managed identity allows an Azure App Service application to authenticate to supported Azure services without storing credentials in application configuration. When used with Azure Key Vault, the application can obtain an identity-based token and access secrets or other permitted resources after appropriate permissions are assigned. This reduces the need to maintain passwords, service principals, or other credentials inside application settings. SAS tokens are primarily associated with delegated access to Azure Storage, while deployment slots manage application versions. Blob leases provide concurrency control for blob data. Therefore, managed identity is the preferred solution for secure App Service access to Key Vault without stored credentials.<\/span><\/p>\n<h3><b>Q246. Which Azure App Configuration feature allows developers to enable or disable application functionality without redeploying the application?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Feature flags<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Access restrictions<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Health Check<\/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;\">Azure App Configuration feature flags allow developers to control application functionality through configuration rather than requiring a new application deployment for every change. A feature can be enabled or disabled based on configuration and supported targeting conditions. This is useful for gradual rollouts, testing new functionality, or quickly disabling a feature when necessary. Access restrictions control inbound network traffic, Health Check monitors application availability, and deployment slots provide separate application environments. Feature flags therefore provide a flexible mechanism for managing application behavior independently from the application deployment lifecycle.<\/span><\/p>\n<h3><b>Q247. Which Azure service is designed to provide a centralized store for application configuration settings and feature flags?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Azure App Configuration<\/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 Container Registry<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Azure Files<\/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 Configuration provides a centralized store for application configuration values, feature flags, and other settings. It allows applications to retrieve configuration from a managed service instead of embedding environment-specific values directly in application code. Centralized configuration can simplify application management across development, testing, and production environments. App Configuration can also work alongside Azure Key Vault when sensitive values need dedicated secret protection. Queue Storage is used for asynchronous messaging, Container Registry stores container images, and Azure Files provides shared file storage. Therefore, Azure App Configuration is the correct service when applications require centralized configuration management.<\/span><\/p>\n<h3><b>Q248. Which Azure service should be used to store and manage cryptographic keys for applications?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Azure Key Vault<\/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 Front Door<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Azure App Service<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure Key Vault provides secure management of cryptographic keys, secrets, and certificates. Applications can use Key Vault to protect cryptographic material instead of storing keys directly in source code or application configuration. Access can be controlled through Microsoft Entra identities, managed identities, and appropriate authorization policies or role assignments. Key Vault can therefore help centralize and secure sensitive security-related assets. Queue Storage is designed for messaging, Front Door handles global web traffic, and App Service hosts web applications and APIs. Therefore, Azure Key Vault is the appropriate service for securely storing and managing cryptographic keys.<\/span><\/p>\n<h3><b>Q249. Which Azure Monitor feature can automatically notify administrators when a metric crosses a configured threshold?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Alert rule<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Blob versioning<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Service Bus session<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Container Registry task<\/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 alert rules can evaluate metrics, logs, or other supported signals and trigger an alert when configured conditions are met. For example, an alert rule can notify administrators when CPU utilization remains above a threshold, when an application generates a significant number of errors, or when a resource becomes unavailable. Alert rules can be associated with action groups that determine how notifications or automated responses are delivered. Blob versioning, Service Bus sessions, and ACR Tasks provide different capabilities unrelated to monitoring thresholds. Therefore, an Azure Monitor alert rule is the appropriate feature for detecting specified conditions and initiating notifications.<\/span><\/p>\n<h3><b>Q250. Which Azure Monitor component provides a centralized location for telemetry and logs from multiple Azure resources?<\/b><\/h3>\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 Front Door<\/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 Queue Storage<\/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 centralized storage and querying capabilities for logs and telemetry collected from Azure resources and supported applications. Developers and administrators can use Kusto Query Language to analyze the collected information, troubleshoot failures, identify trends, and create monitoring solutions. Centralizing logs makes it easier to investigate issues across multiple services instead of examining each resource independently. Azure Front Door manages web traffic, Azure Files provides shared file storage, and Queue Storage handles asynchronous messaging. Therefore, a Log Analytics workspace is the correct component when an application requires centralized collection and analysis of monitoring data.<\/span><\/p>\n<h3><b>Q251. Which Application Insights feature helps developers visualize the flow of a request across multiple distributed application components?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Distributed tracing<\/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;\"> Storage redundancy<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Queue partitioning<\/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 distributed tracing helps developers follow requests as they move through multiple components of a distributed application. This is particularly valuable for microservices and applications that call several APIs, databases, or external services. Distributed tracing can help identify where delays or failures occur and provide a broader view of end-to-end request execution. Dependency tracking complements this capability by collecting telemetry about calls to external dependencies. Blob lifecycle management and storage redundancy address data storage management, while queue partitioning is unrelated to application tracing. Therefore, distributed tracing is the appropriate Application Insights capability for following requests across distributed components.<\/span><\/p>\n<h3><b>Q252. An application hosted in Azure App Service needs to deploy a new version without immediately replacing the production version. Which feature should be used?<\/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;\"> Queue trigger<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Blob lease<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Cosmos DB change feed<\/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 deployment slots provide separate environments within the same App Service application, such as staging and production. Developers can deploy a new version to a staging slot, test it, and then swap the slot with production when the application is ready. This approach reduces deployment risk and can help minimize downtime. Configuration values can also be designated as slot-specific settings when appropriate. Queue triggers handle asynchronous function execution, blob leases coordinate blob access, and Cosmos DB change feed tracks data changes. Therefore, a deployment slot is the appropriate feature for testing and preparing a new application version before moving it into production.<\/span><\/p>\n<h3><b>Q253. Which App Service deployment strategy allows a developer to gradually send a percentage of production traffic to a new application version?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Traffic routing between deployment slots<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Blob soft delete<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Key Vault secret rotation<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Queue Storage<\/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 traffic routing can direct a selected percentage of incoming production traffic to a deployment slot. This supports gradual rollout strategies where a new version is exposed to a controlled portion of users before it receives all production traffic. Developers can monitor the new version and increase or decrease its traffic allocation based on application behavior. This approach can reduce deployment risk compared with immediately swapping all production traffic to the new version. Blob soft delete protects deleted objects, Key Vault manages secrets, and Queue Storage provides asynchronous messaging. Therefore, deployment-slot traffic routing is the correct feature for controlled gradual releases.<\/span><\/p>\n<h3><b>Q254. Which App Service setting prevents a configuration value from being exchanged when deployment slots are swapped?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Slot setting<\/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;\"> Health Check<\/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;\">An App Service application setting can be marked as a deployment slot setting to keep that value associated with a specific slot during a slot swap. This is useful for environment-specific configuration, such as connection strings or settings that must remain different between staging and production. When a swap occurs, slot-specific settings remain with their respective slots instead of moving with the application content. Always On helps keep an application loaded, Health Check monitors availability, and access restrictions control incoming traffic. Therefore, marking a configuration as a slot setting is the correct approach for preserving slot-specific values during deployment swaps.<\/span><\/p>\n<h3><b>Q255. Which App Service feature helps keep an application continuously loaded to reduce startup delays?<\/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;\"> Access restrictions<\/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;\"> Private Endpoint<\/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 feature helps keep an App Service application continuously loaded so that it does not become unloaded because of inactivity. Keeping the application active can reduce startup delays when new requests arrive, which can be useful for applications where response time is important. Always On is generally available for supported App Service plans rather than the lowest-cost hosting options. Access restrictions control inbound traffic, deployment slots provide separate deployment environments, and Private Endpoint provides private network connectivity. Therefore, Always On is the appropriate feature when the requirement is to reduce delays associated with an application being unloaded after periods of inactivity.<\/span><\/p>\n<h3><b>Q256. Which App Service feature checks application health and can remove unhealthy instances from traffic?<\/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;\"> Custom domain<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Deployment slot setting<\/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 allows developers to specify a health-check path that App Service can periodically request to determine whether an application instance is responding correctly. When an instance repeatedly fails health checks, App Service can take action to avoid routing traffic to unhealthy instances according to the service&#8217;s health-check behavior. This can improve application availability by helping the platform identify problematic instances. Always On keeps applications loaded, custom domains provide friendly hostnames, and slot settings preserve configuration during deployment swaps. Therefore, Health Check is the correct feature for monitoring application instance health and supporting traffic management around unhealthy instances.<\/span><\/p>\n<h3><b>Q257. Which Azure Container Registry capability controls who can perform actions such as pulling images or pushing new images?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Azure role-based access control<\/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;\"> App Service Health Check<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Cosmos DB TTL<\/span><\/p>\n<p><b>Correct Answer: 1)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure role-based access control, or Azure RBAC, can be used to control permissions for Azure Container Registry operations. Administrators can assign appropriate roles to users, applications, or managed identities so that they receive only the permissions required for their tasks. For example, an identity may be allowed to pull images without receiving permission to push or delete images. This follows the principle of least privilege and helps reduce unauthorized registry operations. Blob lifecycle management controls storage data transitions, Health Check monitors App Service instances, and Cosmos DB TTL manages item expiration. Therefore, Azure RBAC is the appropriate mechanism for controlling ACR access permissions.<\/span><\/p>\n<h3><b>Q258. An AKS workload needs to expose an application externally using an Azure load balancer. Which Kubernetes Service type should be used?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> ClusterIP<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> LoadBalancer<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> ExternalName<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Headless Service<\/span><\/p>\n<p><b>Correct Answer: 2)<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Kubernetes LoadBalancer Service type can expose an application externally and, in Azure Kubernetes Service, can integrate with an Azure load balancer to provide external connectivity. This is useful when clients outside the Kubernetes cluster need to access an application through a supported external endpoint. ClusterIP is primarily for internal cluster communication, while ExternalName maps a service to an external DNS name rather than creating a cloud load balancer. A headless Service does not provide the standard load-balancing behavior of a LoadBalancer Service. Therefore, LoadBalancer is the correct Service type for exposing an AKS workload externally through an Azure load balancer.<\/span><\/p>\n<h3><b>Q259. Which Kubernetes object is used to define the desired number of Pod replicas and manage rolling updates for an application?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Deployment<\/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;\"> Secret<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Service<\/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 Deployment manages the desired state of replicated Pods and supports controlled updates to application workloads. Developers can specify the desired number of replicas, container images, and update behavior. Kubernetes then works to maintain the desired number of Pods and can perform rolling updates when a new application version is deployed. ConfigMaps store non-sensitive configuration, Secrets store sensitive values, and Services provide stable network access to Pods. Therefore, a Deployment is the correct Kubernetes object when the requirement is to manage application replicas and perform rolling updates.<\/span><\/p>\n<h3><b>Q260. Which Kubernetes probe should be used to determine whether a container is ready to receive network traffic?<\/b><\/h3>\n<p><b>1)<\/b><span style=\"font-weight: 400;\"> Liveness probe<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>2)<\/b><span style=\"font-weight: 400;\"> Readiness probe<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>3)<\/b><span style=\"font-weight: 400;\"> Startup command<\/span><span style=\"font-weight: 400;\"><br \/>\n<\/span><b>4)<\/b><span style=\"font-weight: 400;\"> Resource limit<\/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 readiness probe determines whether a container is ready to receive traffic. When a readiness probe fails, Kubernetes can temporarily remove the Pod from the endpoints used by a Service, preventing requests from being sent to an instance that is not ready. This is especially useful during application startup or when an application temporarily cannot process requests. A liveness probe serves a different purpose by determining whether a container should be restarted because it is unhealthy. Startup probes can help with slow-starting applications, while resource limits control CPU and memory usage. Therefore, the readiness probe is the correct choice for controlling traffic based on application readiness.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Microsoft AZ-204 Exam Dumps and Practice Test Dumps &nbsp; Q241. Which Azure service provides a globally distributed entry point for web applications with intelligent routing? 1) Azure Queue Storage 2) Azure Front Door 3) Azure Table Storage 4) Azure Files Correct Answer: 2) Explanation: Azure Front Door provides a globally distributed entry point [&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\/12834"}],"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=12834"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/12834\/revisions"}],"predecessor-version":[{"id":12850,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/12834\/revisions\/12850"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=12834"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=12834"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=12834"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}