Download Developing Solutions for Microsoft Azure.AZ-204.Dump4Pass.2021-03-17.227q.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/

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. 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

Change feed support in Azure Blob Storage The purpose of the change feed is to provide transaction logs of all the changes that occur to the blobs and the blob metadata in your storage account. The change feed provides ordered, guaranteed, durable, immutable, read-only log of these changes. Client applications can read these logs at any time, either in streaming or in batch mode. The change feed enables you to build efficient and scalable solutions that process change events that occur in your Blob Storage account at a low cost. Reference:https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-change-feed

To move a storage account, create a copy of your storage account in another region. Then, move your data to that account by using AzCopy, or another tool of your choice. The steps are: Export a template. Modify the template by adding the target region and storage account name. Deploy the template to create the new storage account. Configure the new storage account. Move data to the new storage account. Delete the resources in the source region. Note: You must enable the change feed on your storage account to begin capturing and recording changes.You can enable and disable changes by using Azure Resource Manager templates on Portal or Powershell. Reference:https://docs.microsoft.com/en-us/azure/storage/common/storage-account-movehttps://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-change-feed

Box 1: If WEBSITES_ENABLE_APP_SERVICE_STORAGEIf WEBSITES_ENABLE_APP_SERVICE_STORAGE setting is unspecified or set to true, the /home/ directory will be shared across scale instances, and files written will persist across restarts Box 2: /homeReference:https://docs.microsoft.com/en-us/azure/app-service/containers/app-service-linux-faq

D: 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. A (not C): 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.      Reference:https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-web-app-overview

Number of VM instances: 4You are not charged extra for deployment slots. Pricing tier: IsolatedThe App Service Environment (ASE) is a powerful feature offering of the Azure App Service that gives network isolation and improved scale capabilities. It is essentially a deployment of the Azure App Service into a subnet of a customer’s Azure Virtual Network (VNet). Reference:https://azure.microsoft.com/sv-se/blog/announcing-app-service-isolated-more-power-scale-and-ease-of-use/

Box 1: DeploymentTo deploy Azure Functions to Kubernetes use the func kubernetes deploy command has several attributes that directly control how our app scales, once it is deployed to Kubernetes. Box 2: ScaledObjectWith --polling-interval, we can control the interval used by KEDA to check Azure Service Bus Queue for messages. Example of ScaledObject with polling interval apiVersion: keda.k8s.io/v1alpha1kind: ScaledObjectmetadata:    name: transformer-fn    namespace: tt    labels:        deploymentName: transformer-fnspec:    scaleTargetRef:        deploymentName: transformer-fn    pollingInterval: 5    minReplicaCount: 0    maxReplicaCount: 100Box 3: SecretStore connection strings in Kubernetes Secrets. Example: to create the Secret in our demo Namespace:# create the k8s demo namespace kubectl create namespace tt # grab connection string from Azure Service Bus KEDA_SCALER_CONNECTION_STRING=$(az servicebus queue authorization-rule keys list \   -g $RG_NAME \   --namespace-name $SBN_NAME \   --queue-name inbound \   -n keda-scaler \   --query "primaryConnectionString" \   -o tsv) # create the kubernetes secret kubectl create secret generic tt-keda-auth \   --from-literal KedaScaler=$KEDA_SCALER_CONNECTION_STRING \   --namespace tt Reference:https://www.thinktecture.com/en/kubernetes/serverless-workloads-with-keda/

Box 1: az appservice plan createThe azure group creates command successfully returns JSON result. Now we can use resource group to create a azure app service plan Box 2: az webapp createCreate a new web app.. Box 3: --plan $webappname..with the serviceplan we created in step 1. Box 4: az webapp deploymentContinuous Delivery with GitHub. Example: az webapp deployment source config --name firstsamplewebsite1 --resource-group websites--repo-url $gitrepo --branch master --git-token $token Box 5: --repo-url $gitrepo --branch master --manual-integrationReference:https://medium.com/@satish1v/devops-your-way-to-azure-web-apps-with-azure-cli-206ed4b3e9b1