View Full Microsoft AZ-204 Exam Dumps and Practice Test Dumps

 

Q301. Which Azure service provides a centralized workspace for querying and analyzing collected log data?

1) Azure App Configuration
2) Azure Log Analytics
3) Azure Container Registry
4) Azure Queue Storage

Correct Answer: 2)

Explanation:

Azure Log Analytics provides a centralized environment for collecting, querying, and analyzing log data from Azure resources, applications, and other supported sources. It uses a powerful query language that allows developers and administrators to investigate operational data, identify trends, troubleshoot failures, and build monitoring solutions. Log Analytics workspaces are commonly integrated with Azure Monitor and Application Insights. App Configuration manages application settings, Container Registry stores container images, and Queue Storage provides asynchronous messaging. Therefore, Azure Log Analytics is the correct service when centralized log collection and interactive analysis are required.

Q302. Which Application Insights capability helps identify calls between an application and external services such as databases or APIs?

1) Dependency tracking
2) Deployment slots
3) Access restrictions
4) Resource locking

Correct Answer: 1)

Explanation:

Application Insights dependency tracking monitors interactions between an application and external components such as databases, HTTP APIs, storage services, and other supported dependencies. This information helps developers understand application performance and identify whether slow responses or failures originate within the application or an external dependency. Application Insights can correlate requests, dependencies, exceptions, and other telemetry to provide a broader view of application behavior. Deployment slots manage application versions, access restrictions control inbound traffic, and resource locking protects Azure resources from certain changes. Therefore, dependency tracking is the correct Application Insights capability.

Q303. Which Azure Monitor feature can notify an administrator when a monitored metric exceeds a configured threshold?

1) Diagnostic setting
2) Alert rule
3) Log Analytics workspace
4) Workbook template

Correct Answer: 2)

Explanation:

An Azure Monitor alert rule evaluates monitored data and can trigger an alert when a configured condition is met. For example, an alert can be created when CPU utilization remains above a defined threshold, an application produces excessive failures, or another monitored metric reaches an undesirable value. Alert rules can be associated with action groups to notify administrators or initiate automated responses. Diagnostic settings primarily control where resource logs and metrics are sent, while Log Analytics provides centralized data analysis. Therefore, an alert rule is the appropriate Azure Monitor feature for detecting threshold-based conditions and initiating notifications.

Q304. Which Azure Monitor component defines who should be notified or what automated action should occur after an alert is triggered?

1) Action group
2) Storage account
3) Deployment slot
4) Function binding

Correct Answer: 1)

Explanation:

Azure Monitor action groups define the notifications and actions that should occur when an alert is triggered. An action group can include supported notification methods and automated actions, allowing organizations to notify responsible personnel or integrate alerts with automation workflows. This separates the condition that detects an issue from the response that should occur afterward. Storage accounts provide data storage, deployment slots support application deployment strategies, and function bindings simplify integration with supported Azure resources. Therefore, an action group is the correct Azure Monitor component for defining the response to an alert.

Q305. Which Azure App Service feature allows developers to deploy a new version of an application to an isolated environment before swapping it into production?

1) Access restrictions
2) Deployment slot
3) Health Check
4) VNet Integration

Correct Answer: 2)

Explanation:

An App Service deployment slot provides a separate environment where a new application version can be deployed and tested before it becomes the production version. After validation, the slot can be swapped with production, helping reduce deployment downtime and risk. Slots are particularly useful for staging, testing, and controlled release strategies. Access restrictions manage incoming traffic, Health Check monitors application health, and VNet Integration provides access to resources through a virtual network. Therefore, a deployment slot is the correct App Service feature for testing a new application version before promoting it to production.

Q306. Which App Service deployment feature can gradually route a percentage of production traffic to a non-production slot?

1) Traffic routing
2) Application settings
3) Health Check
4) Custom domain

Correct Answer: 1)

Explanation:

App Service traffic routing can direct a selected percentage of incoming traffic to a deployment slot instead of sending all requests directly to production. This supports controlled testing and gradual release strategies, allowing developers to observe the behavior of a new version with a limited portion of real traffic. If the new version performs correctly, traffic can be increased or the slot can eventually be swapped into production. Application settings manage configuration values, Health Check monitors application availability, and custom domains provide friendly web addresses. Therefore, traffic routing is the appropriate feature for gradually exposing a slot to users.

Q307. Which App Service setting prevents a configuration value from being exchanged when deployment slots are swapped?

1) Read-only setting
2) Deployment slot setting
3) Health Check setting
4) Scaling setting

Correct Answer: 2)

Explanation:

An App Service deployment slot setting marks an application configuration value as specific to the slot. When slots are swapped, values marked as deployment slot settings remain associated with their original slot instead of moving with the application content. This is useful for environment-specific values such as database connection strings, service endpoints, or other configuration that should differ between staging and production. Health Check settings serve a different purpose by monitoring application availability, while scaling settings control resource capacity. Therefore, marking a configuration value as a deployment slot setting is the correct approach.

Q308. Which Azure App Service capability allows an application to use a custom hostname such as www.example.com?

1) Custom domain
2) Deployment slot
3) Autoscale rule
4) Application Insights

Correct Answer: 1)

Explanation:

An App Service custom domain allows a web application to be accessed through a domain name selected by the application owner rather than only the default Azure-provided hostname. Domain configuration generally requires appropriate DNS records and domain verification before the hostname can be associated with the application. A custom domain provides a more recognizable address for users and can be combined with HTTPS certificates to secure communication. Deployment slots support application versions, autoscale adjusts capacity, and Application Insights monitors application behavior. Therefore, custom domain is the correct App Service capability for using a branded hostname.

Q309. Which App Service feature can automatically increase or decrease application instances according to workload conditions?

1) Autoscale
2) Custom domain
3) Access restriction
4) Deployment slot setting

Correct Answer: 1)

Explanation:

App Service autoscale can automatically adjust the number of application instances according to configured scaling rules and monitored conditions. This helps applications handle changes in demand without requiring administrators to manually change instance counts. Scaling rules can be based on supported metrics and thresholds, allowing capacity to increase during busy periods and decrease when demand falls. Custom domains control application hostnames, access restrictions control incoming requests, and deployment slot settings determine which configuration values remain associated with a slot. Therefore, autoscale is the appropriate App Service capability for dynamically adjusting application capacity.

Q310. Which Azure App Service feature provides a mechanism to restore an application and its associated content from a previous backup?

1) App Service backup and restore
2) Access restrictions
3) Traffic routing
4) Application Insights

Correct Answer: 1)

Explanation:

App Service backup and restore provides a mechanism for creating backups of supported application content and configuration and restoring the application when needed. Backups can help protect against accidental changes, deployment problems, or data loss scenarios. The backup configuration can include application content and supported database information depending on the selected setup and service requirements. Access restrictions control incoming network access, traffic routing manages distribution between deployment slots, and Application Insights provides monitoring telemetry. Therefore, App Service backup and restore is the correct feature when an application needs a recovery option based on a previous backup.

Q311. Which Azure service provides global HTTP and HTTPS load balancing for web applications using Microsoft’s global edge network?

1) Azure Queue Storage
2) Azure Front Door
3) Azure Table Storage
4) Azure Files

Correct Answer: 2)

Explanation:

Azure Front Door provides global application delivery and HTTP/HTTPS traffic management for web applications. It can route user requests across globally distributed application endpoints and use health probes to help direct traffic toward healthy origins. Front Door can improve availability and responsiveness for applications serving users in multiple geographic locations. Queue Storage provides asynchronous messaging, Table Storage offers NoSQL key-value storage, and Azure Files provides managed file shares. Therefore, Azure Front Door is the correct service when global HTTP and HTTPS traffic distribution is required for a web application.

Q312. Which Azure Front Door capability determines whether an origin is healthy before routing traffic to it?

1) Health probe
2) Application setting
3) Deployment slot
4) Storage tier

Correct Answer: 1)

Explanation:

Azure Front Door health probes periodically send requests to configured origins to determine whether they are responding appropriately. Front Door can use this health information when making routing decisions, helping direct traffic toward healthy application endpoints and away from unhealthy ones. This improves resilience when an application is deployed across multiple origins or regions. Application settings manage application configuration, deployment slots provide separate App Service environments, and storage tiers determine data-access characteristics. Therefore, health probes are the correct Front Door capability for checking origin availability before traffic is routed.

Q313. Which Azure service is designed for globally distributed NoSQL applications requiring configurable consistency models?

1) Azure Cosmos DB
2) Azure Queue Storage
3) Azure Files
4) Azure App Configuration

Correct Answer: 1)

Explanation:

Azure Cosmos DB is a globally distributed database service designed for scalable NoSQL workloads. It provides multiple consistency levels so developers can choose an appropriate balance between consistency, availability, latency, and performance for their application. Cosmos DB supports global distribution and automatic replication across selected regions, making it suitable for applications that need geographically distributed data access. Queue Storage is designed for simple asynchronous messaging, Azure Files provides shared file storage, and App Configuration manages application settings. Therefore, Azure Cosmos DB is the appropriate service for globally distributed NoSQL applications with configurable consistency requirements.

Q314. Which Cosmos DB operation is generally the most efficient way to retrieve a single known item when both its partition key and item ID are available?

1) Cross-partition query
2) Point read
3) Full container scan
4) Aggregation query

Correct Answer: 2)

Explanation:

A Cosmos DB point read retrieves a specific item when both the item’s ID and partition key are known. This operation is highly efficient because Cosmos DB can directly locate the item within the appropriate logical partition rather than searching across multiple partitions. Point reads are commonly preferred when applications need to retrieve individual known records and want predictable request-unit consumption. Cross-partition queries and scans can involve more work, while aggregation queries are intended for calculations across sets of data. Therefore, a point read is the most efficient choice when both the item ID and partition key are available.

Q315. Which Cosmos DB feature automatically removes items after a specified period?

1) Change feed
2) Time to Live
3) Indexing policy
4) Partition key

Correct Answer: 2)

Explanation:

Cosmos DB Time to Live, commonly called TTL, allows items to expire automatically after a configured duration. This is useful for temporary data, session information, logs, caches, and other records that should not remain in the database indefinitely. TTL can help automate data-retention requirements without requiring application code to periodically identify and delete expired items. The change feed tracks changes to items, indexing policies control query indexing behavior, and partition keys determine how data is distributed. Therefore, Time to Live is the correct Cosmos DB feature for automatic expiration of stored items.

Q316. Which Cosmos DB capability provides a stream of changes made to items so applications can process updates incrementally?

1) Change feed
2) TTL
3) Point-in-time restore
4) Strong consistency

Correct Answer: 1)

Explanation:

The Cosmos DB change feed provides an ordered record of changes to items within a container. Applications can consume these changes to implement event-driven processing, synchronization, analytics pipelines, materialized views, or downstream integrations. Instead of repeatedly querying the entire dataset to identify updates, an application can process changes incrementally through the change feed. TTL controls automatic expiration, point-in-time restore supports data recovery, and consistency settings determine how reads observe replicated data. Therefore, the change feed is the correct Cosmos DB capability for processing item changes incrementally.

Q317. Which Azure Storage redundancy option synchronously replicates data across availability zones within a region?

1) LRS
2) ZRS
3) GRS only
4) RA-GRS only

Correct Answer: 2)

Explanation:

Zone-redundant storage, or ZRS, synchronously replicates data across multiple availability zones within the same Azure region. This provides resilience against failures affecting an individual availability zone while keeping the data within the selected region. Locally redundant storage, or LRS, maintains copies within a single datacenter or availability zone scope and provides less protection against zone-level failures. Geo-redundant options replicate data to another region and address regional resilience rather than simply distributing copies across zones. Therefore, ZRS is the appropriate redundancy option when protection against availability-zone failures is required.

Q318. Which Azure Blob Storage feature protects deleted blobs by retaining them for a configured recovery period?

1) Blob soft delete
2) Blob indexing
3) Blob leasing
4) Storage firewall

Correct Answer: 1)

Explanation:

Blob soft delete protects against accidental deletion by retaining deleted blobs for a configured period. During the retention period, a deleted blob can be recovered according to the storage account’s supported recovery capabilities. This feature is useful for protecting important files from accidental or unintended deletion. Blob indexing helps identify data using searchable tags, blob leases provide controlled access for concurrency scenarios, and storage firewalls control network access. Therefore, Blob soft delete is the correct feature when deleted blobs need to remain recoverable for a defined period.

Q319. Which Azure Blob Storage feature allows an application to prevent other clients from modifying a blob while it is being processed?

1) Blob lease
2) Blob versioning
3) Storage tiering
4) Lifecycle management

Correct Answer: 1)

Explanation:

A Blob Storage lease provides a mechanism for acquiring exclusive access to a blob for a defined period. Applications can use leases to coordinate operations and prevent conflicting writes when multiple clients might attempt to modify the same blob. This is particularly useful for distributed applications where concurrency must be controlled. Blob versioning preserves previous versions, storage tiers optimize access and storage costs, and lifecycle management automates movement or deletion according to policies. Therefore, a blob lease is the appropriate feature when an application needs controlled exclusive access during processing.

Q320. Which Azure Storage feature can automatically move blobs to cooler access tiers or delete them after defined conditions are met?

1) Blob lifecycle management
2) Blob lease
3) Private Endpoint
4) User delegation SAS

Correct Answer: 1)

Explanation:

Azure Blob Storage lifecycle management allows organizations to define policies that automatically move blobs between supported access tiers or delete them when specified conditions are met. Policies can be based on factors such as the age of a blob, helping optimize storage costs and enforce retention requirements. For example, frequently accessed data can remain in a hot tier while older data can move to a cooler tier. Blob leases control concurrency, Private Endpoints provide private network access, and user delegation SAS provides delegated access. Therefore, lifecycle management is the correct feature for automating blob tiering and deletion.