Download Developing Solutions for Microsoft Azure.AZ-204.Prep4Sure.2020-04-13.24q.vcex

Not necessary to convert the account, instead move photo processing to an Azure Function triggered from the blob upload..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.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

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

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

Explanation: You need to catch the triggered event, so move the photo processing to an Azure Function triggered from the blob uploadNote: 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

Scenario: All Internal services must only be accessible from Internal Virtual Networks (VNets)There are three Network Location types – Private, Public and DomainReference:https://devblogs.microsoft.com/powershell/setting-network-location-to-private/

Azure Event Hub  is used for telemetry and distributed data streaming.This service provides a single solution that enables rapid data retrieval for real-time processing as well as repeated replay of stored raw data. It can capture the streaming data into a file for processing and analysis.It has the following characteristics:low latencycapable of receiving and processing millions of events per secondat least once deliveryReference:https://docs.microsoft.com/en-us/azure/event-grid/compare-messaging-services

Example:// Create a new instance of the Cosmos Client    this.cosmosClient = new CosmosClient(EndpointUri, PrimaryKey)//ADD THIS PART TO YOUR CODE    await this.CreateDatabaseAsync();Reference:https://docs.microsoft.com/en-us/azure/cosmos-db/sql-api-get-started

Scenario: The Shipping Logic App requires secure resources to the corporate VNet and use dedicated storage resources with a fixed costing model.You can access to Azure Virtual Network resources from Azure Logic Apps by using integration service environments (ISEs).Sometimes, your logic apps and integration accounts need access to secured resources, such as virtual machines (VMs) and other systems or services, that are inside an Azure virtual network. To set up this access, you can create an integration service environment (ISE) where you can run your logic apps and create your integration accounts.Reference:https://docs.microsoft.com/en-us/azure/logic-apps/connect-virtual-network-vnet-isolated-environment-overview

Use the authentication-managed-identity policy to authenticate with a backend service using the managed identity of the API Management service. This policy essentially uses the managed identity to obtain an access token from Azure Active Directory for accessing the specified resource. After successfully obtaining the token, the policy will set the value of the token in the Authorization header using the Bearer scheme.Reference:https://docs.microsoft.com/bs-cyrl-ba/azure/api-management/api-management-authentication-policies