Microsoft Certified: Azure Developer Associate - (AZ-204) Exam Questions

Create a managed identity is CORRECT because here we need to use managed identity in all the cases where possible, as mentioned in the Security requirements.

Create an Azure App Configuration store is CORRECT because as per the requirements, we need to store all the site settings and app configuration centrally, without using secrets, which eliminates Azure key vault. App config store allows you to do the same and act as a central storing solution for all your configurations in all your Azure app services. It also encrypts the stored data in rest and in transit.

Update the role assignments for the Azure App Configuration store is CORRECT because you need to assign some sort of access to the managed identity which will allow it to store the config settings to the Configuration store.

Create an Azure Key Vault is INCORRECT because as per the requirements we do not need to store the configurations as secrets. And in keyvault, you usually store settings/configurations in secrets. And an App configuration store should be used here instead because it is meant to be used as a central configuration store for all app services in Azure.

Update the role assignments for the Azure Key Vault is INCORRECT because we are not using Azure key vault here to store configurations, so we do not have to update the role assignments in it.

Read More:

https://learn.microsoft.com/en-us/azure/azure-app-configuration/overview

https://learn.microsoft.com/en-us/azure/azure-app-configuration/faq

Create a user flow is CORRECT because a user flow allows you to define how the users in a tenant perform actions like sign-up, sign-in and edit profiles in your webapp.

Add the app to the user flow is CORRECT because in order to apply the conditions that you have defined in the user flow, you need to attach an app to the flow. That is why the app needs to be registered before we can use/test these user flows.

Register the app in Microsoft Entra ID is CORRECT because you need an app against which the users will authenticate. You need the app to be registered before you can configure a user flow for the farmers.

Add the shared access signature (SAS) token to the app and Create a shared access signature (SAS) token are INCORRECT options because use of SAS token go against the requirement of farmers using their own Microsoft Entra ID user profile to authenticate.

Read More:

https://learn.microsoft.com/en-us/azure/active-directory-b2c/tutorial-create-user-flows?pivots=b2c-user-flow

Scale up the App Service plan to Premium is CORRECT because error 503 implies that the service is not available at the moment. Also, as mentioned in the error details, there is also a spike noticed in CPU and memory usage, which clearly signifies that the resource usage has reached its limit and the application needs more resources which can be achieved by scaling it up.

Add an App Service staging deployment slot is INCORRECT because deployment slot is useful when you want to test some new features and do not want to deploy the new changes all at once to the instance serving the users currently. Here deployment slot will not help in resolving error 503.

Configure the App Service Local Cache feature is INCORRECT because configuring cache for an app can improve its latency and response time but it cannot provide more CPU and memory which is currently lacking in the app as we see error 503.

Create an Azure Content Delivery Network profile and endpoint is INCORRECT because CDN is useful when you want to make sure the app is reachable and highly performant to all the users irrespective of the geographical locations. But it cannot help in providing more CPU and memory resources.

Read More:

https://learn.microsoft.com/en-us/azure/app-service/manage-scale-up

Configure the App Service Local Cache feature is CORRECT because here it is reported that the avg response time is high and also the network traffic, which implies that there was a high number of requests which made the app take longer to respond. A quick solution for this situation would be to implement cache so that if the requests are repeated, then the app does not have to go all the way to the data store and fetch again and again. This also improves the response time.

Scale up the App Service plan to Premium is INCORRECT because scaling up provides more resources like CPU, memory, disk space etc but that is not what we are looking for. We need to speed up the response time in the moment of a huge spike in the request count.

Restart the application from the App Service portal is INCORRECT because restarting it will only clean up the temp data in the app internal memory and nothing else. So we will again see the same results in case of a large number of requests. Hence we need to implement a more permanent solution here.

Create a custom autoscale rule to increase the instance count is INCORRECT because scaling out will only increase the count of the instances, which in turn will have to make the same number of calls to the backend data store when there is heavy traffic. So the response time has not really improved. Hence we cannot use this.

Read More:

https://learn.microsoft.com/en-us/azure/app-service/overview-local-cache

TrackMetric is CORRECT because TrackMetric allows you to send pre-aggregated telemetry data representing a specific metric over a time interval. This reduces the volume of data sent to Azure by summarizing multiple individual values.

You can define metrics for various aspects of your distributor API calls, such as:

• Average response time

• Total number of calls

• Success rate (percentage of successful calls)

• Number of calls per API endpoint

TrackEvent is INCORRECT as this method is used for capturing specific events within your application. While you could potentially use it to track each API call, it wouldn't provide aggregation functionalities. Sending individual events for every API call would also increase telemetry traffic and data costs.

TrackDependency is INCORRECT as this method is designed to track external dependencies your application interacts with, like database calls or web service calls. It wouldn't be ideal for aggregating internal API call telemetry.

TrackException is INCORRECT as this method is specifically used for capturing exceptions and errors encountered during application execution. It wouldn't be suitable for aggregating API call statistics.

TrackTrace is INCORRECT as this method logs detailed tracing information for debugging purposes. While it could capture API call details, it wouldn't provide aggregation functionalities and would contribute to increased data volume.

Read More:

https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/metrics-custom-overview

(Action 1) Create an Azure Content Delivery Network profile is CORRECT because this sets up the CDN profile, which acts as a container for your CDN settings and endpoints.

(Action 4) Create an Azure Content Delivery Network endpoint is CORRECT because the endpoint is necessary to route requests to your origin (e.g., your web application or API).

(Action 5) Configure a new Azure Content Delivery Network origin is CORRECT because this sets up the actual origin server where your content is stored, such as your production app, and links it to the CDN endpoint for content delivery.

(Action 2) Create an Azure Content Delivery Network origin group is INCORRECT an origin group in Azure CDN is used to group multiple origins and apply load balancing or failover policies. This is useful for high availability and redundancy but not directly related to validating updates, directing staff to the production app, or displaying profile information upon authentication.

(Action 3) Configure Azure Content Delivery Network compression is INCORRECT as CDN compression is a performance optimization technique to reduce the size of files transferred from the CDN to the users, which improves load times. While useful for performance, it does not address the specific requirements of validating updates, redirecting to the production app, or handling authentication and profile display.

(Action 6) Add the Azure Content Delivery Network origin to the origin group is INCORRECT as this action involves adding a specific origin to a previously created origin group, which again is more about managing multiple origins for load balancing and failover. It does not directly relate to the need to validate updates, provide a redirection link to the production app, or display authenticated user profile information.

Read More:

https://learn.microsoft.com/en-us/azure/cdn/scripts/cli/cdn-azure-cli-create-endpoint

Create an Azure Application Gateway with a Web Application Firewall (WAF). Configure end-to-end TLS encryption and the WAF is CORRECT because of the following:

• HTTP 503 and High CPU/Memory Usage: Application Gateway with WAF balances traffic and protects against DDoS attacks.

• HTTP 502 and High Response Times/Networking Traffic: It manages load distribution and improves response times.

• Large Webpage Load Sizes: While it doesn’t reduce size directly, it improves load times via better traffic management.

• Authentication Errors to Service Bus: Ensuring end-to-end TLS encryption secures communications, potentially resolving these issues.

Azure Cache for Redis is INCORRECT as it reduces database load but doesn’t address HTTP errors or security.

Azure CDN is INCORRECT as it helps with load times but not security comprehensively.

App Service with TLS/SSL is INCORRECT as it improves security but not load balancing or advanced threat protection.

Read More:

https://learn.microsoft.com/en-us/azure/web-application-firewall/overview

https://learn.microsoft.com/en-us/azure/application-gateway/overview

Standard is CORRECT because you need to work with Deployment Slots so that you can do the migration in parts, and also test/validate the changes as and when you make.Basic tier does not support deployment slots.

Read More:

https://learn.microsoft.com/en-us/azure/app-service/deploy-staging-slots?source=recommendations&tabs=portal

Deployment slot is CORRECT as it allows you to create separate environments (such as staging, testing, and production) within the same App Service. This enables internal staff to validate code changes in a staging environment before swapping it with production, ensuring that changes are tested and approved before release.

Custom container is INCORRECT as this is used for deploying applications in containers, which isn't specifically related to validating code changes before production.

Domain certificate is INCORRECT as this is for securing custom domains with SSL/TLS certificates, not for code validation.

Deployment credentials is INCORRECT as these are used for deploying applications via FTP or Git, not for staging and validating code changes.

Read More:

https://learn.microsoft.com/en-us/azure/app-service/deploy-staging-slots

https://learn.microsoft.com/en-us/azure/app-service/deploy-staging-slots#best-practices

/v1.0/me is CORRECT because this endpoint retrieves the properties and relationships of the signed-in user, which includes profile photo, email, and other personal information. It is designed for scenarios where you need to get information about the currently authenticated user.

/v1.0/me/people/?$search=me is INCORRECT as this endpoint is used to search for people relevant to the signed-in user (e.g., their contacts) but is not specifically for retrieving the profile photo and email of the signed-in user.

/v1.0/users?$select=profilePhoto,mail is INCORRECT as this endpoint can be used to retrieve properties for a list of users, but it is more complex and less efficient when you only need information about the currently authenticated user. It also requires appropriate permissions to access other users' information.

Read More:

https://learn.microsoft.com/en-us/graph/api/user-get?view=graph-rest-1.0&tabs=http

https://learn.microsoft.com/en-us/graph/auth/auth-concepts