Microsoft AZ-204 Online Practice Questions and Exam Preparation

Microsoft AZ-204 Online Questions & Answers

• Question 511:

  HOTSPOT

  You are using Azure Front Door Service.

  You are expecting inbound files to be compressed by using Brotli compression. You discover that inbound XML files are not compressed. The files are 9 megabytes (MB) in size.

  You need to determine the root cause for the issue.

  To answer, select the appropriate options in the answer area.

  NOTE: Each correct selection is worth one point.

  

  

  ---

  Box 1: No

  Front Door can dynamically compress content on the edge, resulting in a smaller and faster response to your clients. All files are eligible for compression. However, a file must be of a MIME type that is eligible for compression list.

  Box 2: No

  Sometimes you may wish to purge cached content from all edge nodes and force them all to retrieve new updated assets. This might be due to updates to your web application, or to quickly update assets that contain incorrect information.

  Box 3: Yes

  These profiles support the following compression encodings: Gzip (GNU zip), Brotli

  https://docs.microsoft.com/en-us/azure/frontdoor/front-door-caching

• Question 512:

  You develop a REST API. You implement a user delegation SAS token to communicate with Azure Blob storage.

  The token is compromised.

  You need to revoke the token.

  What are two possible ways to achieve this goal? Each correct answer presents a complete solution.

  NOTE: Each correct selection is worth one point.

  A. Revoke the delegation keys
  B. Delete the stored access policy.
  C. Regenerate the account key.
  D. Remove the role assignment for the security principle.
  A. Revoke the delegation keys
  B. Delete the stored access policy.

  ---

  Explanation

  A: Revoke a user delegation SAS

  To revoke a user delegation SAS from the Azure CLI, call the az storage account revoke-delegation-keys command. This command revokes all of the user delegation keys associated with the specified storage account. Any shared access signatures associated with those keys are invalidated.

  B: To revoke a stored access policy, you can either delete it, or rename it by changing the signed identifier. Changing the signed identifier breaks the associations between any existing signatures and the stored access policy. Deleting or renaming the stored access policy immediately effects all of the shared access signatures associated with it.

  https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/storage/blobs/storage-blob-user-delegation-sas-create-cli.md

  https://docs.microsoft.com/en-us/rest/api/storageservices/define-stored-access-policy#modifying-or-revoking-a-stored-access-policy

• Question 513:

  DRAG DROP

  You are developing several microservices named serviceA, serviceB, and serviceC. You deploy the microservices to a new Azure Container Apps environment.

  You have the following requirements:

  The microservices must persist data to storage. serviceA must persist data only visible to the current container and the storage must be restricted to the amount of disk space available in the container. serviceB must persist data for the lifetime of the replica and allow multiple containers in the replica to mount the same storage location. serviceC must persist data beyond the lifetime of the replica while allowing multiple containers to access the storage and enable per object permissions.

  You need to configure storage for each microservice.

  Which storage type should you use? To answer, drag the appropriate storage types to the correct microservices. Each storage type may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.

  NOTE: Each correct selection is worth one point.

  Select and Place:

  

  

  ---

  Box 1: Container file system

  serviceA must persist data only visible to the current container and the storage must be restricted to the amount of disk space available in the container.

  Container-scoped storage

  Ephemeral storage available to a running container

  Persistence: Data is available until container shuts down

  Example: Writing a local app cache.

  Container file system storage has the following characteristics: The storage is temporary and disappears when the container is shut down or restarted.

  Files written to this storage are only visible to processes running in the current container.

  Box 2: Ephemeral

  serviceB must persist data for the lifetime of the replica and allow multiple containers in the replica to mount the same storage location.

  Replica-scoped storage

  Ephemeral storage for sharing files between containers in the same replica

  Persistence: Data is available until replica shuts down

  Example: The main app container writing log files that are processed by a sidecar container.

  Box 3: Azure file storage

  serviceC must persist data beyond the lifetime of the replica while allowing multiple containers to access the storage and enable per object permissions.

  Azure file shares can be used as persistent volumes for stateful containers.

  Azure Files

  Permanent storage

  Data is persisted to Azure Files

  Example: Writing files to a file share to make data accessible by other systems.

  Note:

  * Ephemeral volume

  Ephemeral OS disks are created on the local virtual machine (VM) storage and not saved to the remote Azure Storage. Ephemeral OS disks work well for stateless workloads, where applications are tolerant of individual VM failures but are more affected by VM deployment time or reimaging of individual VM instances. With Ephemeral OS disk, you get lower read/write latency to the OS disk and faster VM reimage.

  The key features of ephemeral disks are:

  Ideal for stateless applications.

  Supported by Marketplace, custom images, and by Azure Compute Gallery (formerly known as Shared Image Gallery).

  Ability to fast reset or reimage VMs and scale set instances to the original boot state.

  Lower latency, similar to a temporary disk.

  Ephemeral OS disks are free, you incur no storage cost for OS disks.

  Available in all Azure regions.

  https://learn.microsoft.com/en-us/azure/container-apps/storage-mounts

  https://learn.microsoft.com/en-us/azure/storage/files/storage-files-introduction

  https://learn.microsoft.com/en-us/azure/virtual-machines/ephemeral-os-disks

• Question 514:

  You are developing a microservices-based application that uses Azure Container Apps.

  The application consists of several containerized services that handle tasks, such as processing orders, managing inventory, and generating reports.

  You deploy a new revision of the processing orders app.

  Processing orders must be triggered by a web request and must always be available based on incoming web requests.

  You need to validate that the replica is ready to handle incoming requests.

  What should you implement?

  A. TCP liveness probe
  B. HTTP readiness probe
  C. HTTP startup probe
  D. TCP readiness probe
  E. HTTP liveness probe
  B. HTTP readiness probe

• Question 515:

  HOTSPOT

  You need to implement the corporate website.

  How should you configure the solution? To answer, select the appropriate options in the answer area.

  NOTE: Each correct selection is worth one point.

  

  

  ---

  Box 1: Standard

  Below is a high-level comparison of the features as per the pricing tier for the App Service Plan.

  

  Note: Corporate website

  The company provides a public website located at

  http://www.vanarsdelltd.com.

  The website consists of a React JavaScript user interface, HTML, CSS, image assets, and several APIs hosted in Azure Functions. Corporate website requirements:

  1. Secure the website by using SSL.

  2. Minimize costs for data storage and hosting.

  3. Implement native GitHub workflows for continuous integration and continuous deployment (CI/CD).

  4. Distribute the website content globally for local use.

  5. Implement monitoring by using Application Insights and availability web tests including SSL certificate validity and custom header value verification.

  6. The website must have 99.95 percent uptime.

  Box 2: App Service Web App

  A Web App is a web application that is hosted in an App Service. The App Service is the managed service in Azure that enables you to deploy a web application and make it available to your customers on the Internet in a very short amount of time.

  Incorrect:

  A Static Web Application is any web application that can be delivered directly to an end user's browser without any server-side alteration of the HTML, CSS, or JavaScript content.

  https://azure-training.com/2018/12/27/understanding-app-services-app-service-plan-and-ase/

  https://docs.microsoft.com/en-us/azure/app-service/overview

• Question 516:

  You are implementing an application by using Azure Event Grid to push near-real-time information to customers.

  You have the following requirements: You must send events to thousands of customers that include hundreds of various event types.

  The events must be filtered by event type before processing.

  Authentication and authorization must be handled by using Microsoft Entra ID.

  The events must be published to a single endpoint.

  You need to implement Azure Event Grid.

  Solution: Publish events to a system topic. Create an event subscription for each customer.

  Does the solution meet the goal?

  A. Yes
  B. No
  B. No

  ---

  Explanation

  Correct Solution: Publish events to a partner topic. Create an event subscription for each customer.

  Partner Events overview for customers - Azure Event Grid

  Azure Event Grid's Partner Events allows customers to subscribe to events that originate in a registered system using the same mechanism they would use for any other event source on Azure, such as an Azure service. Those registered systems integrate with Event Grid are known as "partners".

  This feature also enables customers to send events to partner systems that support receiving and routing events to customer's solutions/endpoints in their platform.

  Note: Partners

  A partner is a kind of publisher that sends events from its system to make them available to Azure customers. A partner is typically a SaaS or ERP provider that integrates with Azure Event Grid to help customers realize event-driven use cases across platforms. Partners not only can publish events to Azure Event Grid, but they can also receive events from it. These capabilities are enabled through the Partner Events feature.

  Note 2: Why should I use Partner Events?

  You may want to use the Partner Events feature if you've one or more of the following requirements.

  You want to subscribe to events that originate in a partner system and route them to event handlers on Azure or to any application or service with a public endpoint.

  You want to take advantage of the rich set Event Grid's destinations/event handlers that react to events from partners.

  *-> You want to forward events raised by your custom application on Azure, an Azure service, or a Microsoft service to your application or service hosted by the partner system. For example, you may want to send Microsoft Entra ID, Teams, SharePoint, or Azure Storage events to a partner system on which you're a tenant for processing.

  You need a resilient push delivery mechanism with send-retry support and at-least once semantics.

  You want to use Cloud Events 1.0 schema for your events.

  Note 3: Partner topic

  Receive events from a partner

  You receive events from a partner in a partner topic that's' created on your behalf by a partner. Here are the high-level steps to subscribe to events from a partner.

  1. Authorize partner to create a partner topic in a resource group you designate. Authorizations are stored in partner configurations (Azure resources).

  2. Request partner to forward your events from its service to your partner topic. Partner provisions a partner topic in the specified resource group of your Azure subscription.

  3. After the partner creates a partner topic in your Azure subscription and resource group, activate your partner topic.

  4. Subscribe to events by creating one or more event subscriptions on the partner topic.

  https://learn.microsoft.com/en-us/azure/event-grid/concepts

  https://learn.microsoft.com/en-us/azure/event-grid/partner-events-overview

• Question 517:

  DRAG DROP

  You develop and deploy a web app to Azure App Service in a production environment. You scale out the web app to four instances and configure a staging slot to support changes.

  You must monitor the web app in the environment to include the following requirements:

  1. Increase web app availability by re-routing requests away from instances with error status codes and automatically replace instances if they remain in an error state after one hour.

  2. Send web server logs, application logs, standard output and standard error messaging to an Azure Storage blob account.

  You need to configure Azure App Service.

  Which values should you use? To answer, drag the appropriate configuration value to the correct requirements. Each configuration value may be used once, more than....

  Select and Place:

  

  

  ---

  Box 1: Health check

  Health check increases your application's availability by re-routing requests away from unhealthy instances, and replacing instances if they remain unhealthy. Your App Service plan should be scaled to two or more instances to fully utilize Health check.

  Box 2: Diagnostic setting

  Azure provides built-in diagnostics to assist with debugging an App Service app.

  With the new Azure Monitor integration, you can create Diagnostic Settings to send logs to Storage Accounts, Event Hubs and Log Analytics.

  https://docs.microsoft.com/en-us/azure/app-service/monitor-instances-health-check

  https://docs.microsoft.com/en-us/azure/app-service/troubleshoot-diagnostic-logs

• Question 518:

  You need to audit the retail store sales transactions.

  What are two possible ways to achieve the goal? Each correct answer presents a complete solution.

  NOTE: Each correct selection is worth one point.

  A. Update the retail store location data upload process to include blob index tags. Create an Azure Function to process the blob index tags and filter by store location.
  B. Process the change feed logs of the Azure Blob storage account by using an Azure Function. Specify a time range for the change feed data.
  C. Enable blob versioning for the storage account. Use an Azure Function to process a list of the blob versions per day.
  D. Process an Azure Storage blob inventory report by using an Azure Function. Create rule filters on the blob inventory report.
  E. Subscribe to blob storage events by using an Azure Function and Azure Event Grid. Filter the events by store location.
  B. Process the change feed logs of the Azure Blob storage account by using an Azure Function. Specify a time range for the change feed data.
  E. Subscribe to blob storage events by using an Azure Function and Azure Event Grid. Filter the events by store location.

  ---

  Explanation

  Scenario: Audit store sale transaction information nightly to validate data, process sales financials, and reconcile inventory.

  "Process the change feed logs of the Azure Blob storage account by using an Azure Function. Specify a time range for the change feed data": Change feed support is well-suited for scenarios that process data based on objects that have changed. For example, applications can: Store, audit, and analyze changes to your objects, over any period of time, for security, compliance or intelligence for enterprise data management.

  "Subscribe to blob storage events by using an Azure Function and Azure Event Grid. Filter the events by store location": Azure Storage events allow applications to react to events, such as the creation and deletion of blobs. It does so without the need for complicated code or expensive and inefficient polling services. The best part is you only pay for what you use.

  Blob storage events are pushed using Azure Event Grid to subscribers such as Azure Functions, Azure Logic Apps, or even to your own http listener. Event Grid provides reliable event delivery to your applications through rich retry policies and dead-lettering.

  Incorrect Answers:

  "Enable blob versioning for the storage account. Use an Azure Function to process a list of the blob versions per day": You can enable Blob storage versioning to automatically maintain previous versions of an object. When blob versioning is enabled, you can access earlier versions of a blob to recover your data if it is modified or deleted.

  https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-change-feed

  https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-event-overview

• Question 519:

  HOTSPOT

  You are developing an application that uses Azure Storage Queues.

  You have the following code:

  

  For each of the following statements, select Yes if the statement is true. Otherwise, select No.

  NOTE: Each correct selection is worth one point.

  

  

  ---

  Box 1: No

  The code does not configure the lock duration.

  Note: Default lock duration is 30 seconds. Lock duration will be set even if it is not specified in code.

  Box 2: Yes

  Peeking messages will not remove them from the queue.

  Box 3: Yes

  https://docs.microsoft.com/en-us/azure/storage/queues/storage-dotnet-how-to-use-queues

  https://docs.microsoft.com/en-us/dotnet/api/microsoft.servicebus.messaging.queuedescription.lockduration

• Question 520:

  Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

  After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

  You are developing a web app named mywebapp1. Mywebapp1 uses the address myapp1.azurewebsites.net. You protect mywebapp1 by implementing an Azure Web Application Firewall (WAF). The traffic to mywebapp1 is routed through an Azure Application Gateway instance that is also used by other web apps.

  You want to secure all traffic to mywebapp1 by using SSL. Solution: You open the Azure Application Gateway's HTTP setting and set the Override backend path option to mywebapp1.azurewebsites.net. You then enable the Use for App service option.

  Does this meet the goal?

  A. Yes
  B. No
  A. Yes

  ---

  Explanation

  The ability to specify a host override is defined in the HTTP settings and can be applied to any back-end pool during rule creation.

  The ability to derive the host name from the IP or FQDN of the back-end pool members. HTTP settings also provide an option to dynamically pick the host name from a back-end pool member's FQDN if configured with the option to derive host name from an individual back-end pool member.

  SSL termination and end to end SSL with multi-tenant services. In case of end to end SSL, trusted Azure services such as Azure App service web apps do not require whitelisting the backends in the application gateway. Therefore, there is no need to add any authentication certificates.

  https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-web-app-overview