Download Developing Solutions for Microsoft Azure.AZ-204.NetworkArmy.2021-08-04.195q.vcex

Scenario: Shipping websiteUse Azure Content Delivery Network (CDN) and ensure maximum performance for dynamic content while minimizing latency and costs. Tier: StandardProfile: AkamaiOptimization: Dynamic site accelerationDynamic site acceleration (DSA) is available for Azure CDN Standard from Akamai, Azure CDN Standard from Verizon, and Azure CDN Premium from Verizon profiles. DSA includes various techniques that benefit the latency and performance of dynamic content. Techniques include route and network optimization, TCP optimization, and more. You can use this optimization to accelerate a web app that includes numerous responses that aren't cacheable. Examples are search results, checkout transactions, or real-time data. You can continue to use core Azure CDN caching capabilities for static data. Reference:https://docs.microsoft.com/en-us/azure/cdn/cdn-optimization-overview

Box 1: Azure BackupThe VM is critical and has not been backed up in the past. The VM must enable a quick restore from a 7-day snapshot to include in-place restore of disks in case of failure. In-Place restore of disks in IaaS VMs is a feature of Azure Backup. Performance: Accelerated NetworkingScenario: The VM shows high network latency, jitter, and high CPU utilization. Box 2: Accelerated networkingThe VM shows high network latency, jitter, and high CPU utilization. Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, greatly improving its networking performance. This high-performance path bypasses the host from the datapath, reducing latency, jitter, and CPU utilization, for use with the most demanding network workloads on supported VM types. Reference:https://azure.microsoft.com/en-us/blog/an-easy-way-to-bring-back-your-azure-vm-with-in-place-restore/

Async operation tracking The HTTP response mentioned previously is designed to help implement long-running HTTP async APIs with Durable Functions. This pattern is sometimes referred to as the polling consumer pattern. Both the client and server implementations of this pattern are built into the Durable Functions HTTP APIs. Function app You perform local testing for the RequestUserApproval function. The following error message displays:'Timeout value of 00:10:00 exceeded by function: RequestUserApproval'The same error message displays when you test the function in an Azure development environment when you run the following Kusto query:FunctionAppLogs | where FunctionName = = "RequestUserApproval" Reference:https://docs.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-http-features

Azure Functions can run on either a Consumption Plan or a dedicated App Service Plan. If you run in a dedicated mode, you need to turn on the Always On setting for your Function App to run properly. The Function runtime will go idle after a few minutes of inactivity, so only HTTP triggers will actually "wake up" your functions. This is similar to how WebJobs must have Always On enabled. Scenario: Notification latency: Users report that anomaly detection emails can sometimes arrive several minutes after an anomaly is detected. Anomaly detection service: You have an anomaly detection service that analyzes log information for anomalies. It is implemented as an Azure Machine Learning model. The model is deployed as a web service. If an anomaly is detected, an Azure Function that emails administrators is called by using an HTTP WebHook. Reference:https://github.com/Azure/Azure-Functions/wiki/Enable-Always-On-when-running-on-dedicated-App-Service-Plan 

Box 1: RepositoryUpdatedWhen a new version of the ContentAnalysisService is available the previous seven days of content must be processed with the new version to verify that the new version does not significantly deviate from the old version. Box 2: serviceBox 3: imageCollectionReference:https://docs.microsoft.com/en-us/azure/devops/notifications/oob-supported-event-types

Scenario: You must minimize costs for all Azure services. All Internal services must only be accessible from internal Virtual Networks (VNets). Best for long-running scenarios where Durable Functions can't be used. Consider an App Service plan in the following situations:You have existing, underutilized VMs that are already running other App Service instances. You want to provide a custom image on which to run your functions. Predictive scaling and costs are required. Note: When you create a function app in Azure, you must choose a hosting plan for your app. There are three basic hosting plans available for Azure Functions: Consumption plan, Premium plan, and Dedicated (App Service) plan. Incorrect Answers:A: A Premium plan would be more costly.C: Need the VNET functionality.Reference:https://docs.microsoft.com/en-us/azure/azure-functions/functions-scale

Methods to Get User Identity and Claims in a .NET Azure Functions App include:ClaimsPrincipal from the Request Context The ClaimsPrincipal object is also available as part of the request context and can be extracted from the HttpRequest.HttpContext. User Claims from the Request Headers. App Service passes user claims to the app by using special request headers. Reference:https://levelup.gitconnected.com/four-alternative-methods-to-get-user-identity-and-claims-in-a-net-azure-functions-app-df98c40424bb 

Step 1: Build a new application image by using dockerfileStep 2: Create an alias if the image with the fully qualified path to the registryBefore you can push the image to a private registry, you’ve to ensure a proper image name. This can be achieved using the docker tag command. For demonstration purpose, we’ll use Docker’s hello world image, rename it and push it to ACR. # pulls hello-world from the public docker hub $ docker pull hello-world # tag the image in order to be able to push it to a private registry $ docker tag hello-word <REGISTRY_NAME>/hello-world # push the image $ docker push <REGISTRY_NAME>/hello-world Step 3: Log in to the registry and push imageIn order to push images to the newly created ACR instance, you need to login to ACR form the Docker CLI. Once logged in, you can push any existing docker image to your ACR instance. Scenario:Coho Winery plans to move the application to Azure and continue to support label creation. LabelMaker app Azure Monitor Container Health must be used to monitor the performance of workloads that are deployed to Kubernetes environments and hosted on Azure Kubernetes Service (AKS). You must use Azure Container Registry to publish images that support the AKS deployment. References:https://thorsten-hans.com/how-to-use-a-private-azure-container-registry-with-kubernetes-9b86e67b93b6https://docs.microsoft.com/en-us/azure/container-registry/container-registry-tutorial-quick-task

You need to catch the triggered event, so move the photo processing to an Azure Function triggered from the blob upload. Note: Azure Storage events allow applications to react to events. Common Blob storage event scenarios include image or video processing, search indexing, or any file-oriented workflow. Events are pushed using Azure Event Grid to subscribers such as Azure Functions, Azure Logic Apps, or even to your own http listener. However, the processing must start in less than one minute. Note: Only storage accounts of kind StorageV2 (general purpose v2) and BlobStorage support event integration. Storage (general purpose v1) does not support integration with Event Grid. Reference:https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-event-overview

Specify custom warm-up. Some apps might require custom warm-up actions before the swap. The applicationInitialization configuration element in web.config lets you specify custom initialization actions. The swap operation waits for this custom warm-up to finish before swapping with the target slot. Here's a sample web.config fragment. <system.webServer>     <applicationInitialization>         <add initializationPage="/" hostName="[app hostname]" />         <add initializationPage="/Home/About" hostName="[app hostname]" />     </applicationInitialization> </system.webServer> Reference:https://docs.microsoft.com/en-us/azure/app-service/deploy-staging-slots#troubleshoot-swaps