Microsoft Certified: Azure Developer Associate (AZ-204)

 The Microsoft Certified: Azure Developer Associate (AZ-204) is the core credential for developers who design, build, test, and maintain cloud applications. It focuses heavily on serverless computing, Azure functions, security integration, and SDK-based development

---------- Question 1

A financial institution stores millions of sensitive audit logs in Azure Blob Storage. These logs must be retained for seven years for regulatory compliance, after which they should be permanently deleted. Access to these logs should transition from frequent during the first year to infrequent thereafter, and then to rare archival access. To optimize storage costs and ensure compliance, what is the most appropriate strategy for managing these blobs?

1. Use Azure Blob Storage immutable storage with a time-based retention policy set for seven years.
2. Implement a custom Azure Function that periodically checks blob age and deletes them after seven years.
3. Configure an Azure Blob Storage lifecycle management policy to transition blobs to Cool after one year, then to Archive after three years, and finally delete after seven years.
4. Store all logs in Azure Data Lake Storage Gen2 with a hierarchical namespace and manually delete older data.

---------- Question 2

A development team is building a new microservice architecture on Azure. Each microservice requires several configuration settings, including API keys for external services, database connection strings, and feature flags. Some of these settings are highly sensitive and must be protected from unauthorized access, while others are less sensitive but still need to be managed centrally and dynamically updated without redeploying the microservices. They also want to be able to toggle features for specific environments. Which combination of Azure services should the team use to securely and efficiently manage both sensitive and non-sensitive configuration data for their microservices?

1. Store all configuration settings, sensitive and non-sensitive, directly within the microservice application settings in Azure App Service or Function App.
2. Store sensitive API keys and database connection strings in Azure Key Vault, and manage feature flags and non-sensitive settings using Azure App Configuration, linking the Key Vault secrets to App Configuration for central access.
3. Use a custom configuration database for all settings, encrypting sensitive data at rest and managing access through application-specific roles.
4. Store all configuration settings in environment variables on the compute instances hosting the microservices, retrieving them at runtime.

---------- Question 3

A media company stores large volumes of video files in Azure Blob Storage. They want to implement a solution to automatically move older, less frequently accessed video files from the hot storage tier to a cooler, more cost-effective tier after 30 days of last modification. Additionally, files that have not been accessed for 365 days should be automatically deleted from storage to optimize costs and manage data retention policies. Which Azure Blob Storage feature should the developer implement to manage the lifecycle of these blobs efficiently and automatically, minimizing manual intervention?

1. Access Tiers management through manual scripts
2. Shared Access Signatures SAS policies
3. Immutable Storage policies
4. Lifecycle Management policy

---------- Question 4

A global e-commerce platform uses Azure Cosmos DB for its product catalog, which experiences high read volumes and occasional writes. The platform needs to ensure that users always see the latest product information immediately after an update, regardless of their geographical location. However, extreme performance for all write operations is not the absolute top priority. Which consistency level should be configured for the Cosmos DB account to balance strong consistency for reads with acceptable write latency across multiple regions?

1. Eventual
2. Consistent Prefix
3. Session
4. Strong

---------- Question 5

Your financial application processes sensitive transaction data using Azure Cosmos DB. It is critical that read operations always reflect the very latest committed write, ensuring that no stale data is ever presented to users, even if it introduces a slight increase in read latency. However, write operations must acknowledge as quickly as possible without waiting for global replication. Given these specific requirements for data consistency, which Azure Cosmos DB consistency level should you configure for your database account?

1. Eventual
2. Consistent Prefix
3. Session
4. Strong

---------- Question 6

A healthcare organization stores patient records and medical imaging files in Azure Blob Storage. Due to regulatory compliance, these files must be retained for a minimum of seven years. Additionally, files older than two years are accessed infrequently but must remain available for audit purposes. The organization wants to optimize storage costs while ensuring compliance and data accessibility. Which Azure Blob Storage configuration and policy combination would most effectively address these requirements?

1. Set all blobs to the Premium access tier and enable versioning indefinitely.
2. Implement a lifecycle management policy to transition blobs older than two years to the Cool access tier and older than seven years to the Archive access tier.
3. Apply an immutable storage policy for a duration of seven years and keep all blobs in the Hot access tier.
4. Store all files in Azure Disk Storage and manage retention using custom scripts.

---------- Question 7

You are developing a mission-critical web application using Azure App Service. Your development team frequently deploys new features and bug fixes. To minimize downtime and ensure a smooth user experience, you need a strategy that allows you to test new versions of your application in a production-like environment before swapping them into the main production slot. Additionally, you want the ability to quickly revert to the previous stable version if any issues arise after a deployment. Which combination of Azure App Service features should you implement to meet these requirements efficiently?

1. Implement a single production slot and perform in-place upgrades.
2. Utilize deployment slots, configure a staging slot, and enable auto-swap.
3. Deploy multiple App Service instances behind an Azure Traffic Manager profile.
4. Use deployment slots, configure a staging slot, and perform manual swap with preview.

---------- Question 8

A microservices application deployed on Azure Kubernetes Service AKS uses multiple Azure Functions and an Azure App Service Web App. The development team needs a comprehensive solution to monitor performance, collect telemetry data including request rates, response times, and dependency calls across all components. They also require the ability to trace transactions end-to-end to diagnose issues quickly and set up alerts for critical performance deviations. Which Azure monitoring tool should be primarily used to achieve these goals?

1. Azure Monitor Logs with Log Analytics Workspaces.
2. Azure Activity Log.
3. Azure Network Watcher.
4. Azure Application Insights.

---------- Question 9

Your organization has a mobile application that allows users to upload profile pictures directly to an Azure Blob Storage container. For security reasons, the mobile application itself should not have direct access to the storage account keys. Furthermore, each user should only be granted permission to upload their specific profile picture to a designated folder within the container, and this permission should be time-limited to prevent misuse. Which Azure security mechanism should you implement to securely provide the mobile application with the necessary temporary and granular access to the blob storage?

1. Assign an Azure Active Directory role to the mobile application's service principal.
2. Generate and distribute a Shared Access Signature (SAS) to the mobile application for each upload.
3. Store the storage account key securely within the mobile application code.
4. Use Azure Storage Explorer to manually upload images on behalf of users.

---------- Question 10

An organization stores vast amounts of archival data, log files, and backup snapshots in Azure Blob Storage. Most of this data is rarely accessed after the first 30 days but must be retained for compliance purposes for seven years. Access frequency significantly decreases after a month, and data might only be needed for audit purposes or rare restoration events. The organization aims to minimize storage costs while ensuring data availability when required. Which combination of Blob Storage access tiers and lifecycle management policies should be implemented to achieve these goals effectively?

1. Use the Hot tier for all data and manually move old data to the Archive tier every month.
2. Initially store data in the Cool tier, then use a lifecycle policy to move it to the Archive tier after 30 days.
3. Store all data directly in the Archive tier from ingestion and retrieve it when needed.
4. Use the Hot tier for the first 30 days, then transition to the Cool tier indefinitely.

---

Are they useful?

Click here to get 390 more questions to pass this certification at the first try! Explanation for each answer is included!

Follow the below LINKEDIN channel to stay updated about 89+ exams!

Cloud Technology Hub