Exam overview page

This exam measures your ability to accomplish the following technical tasks: develop Azure compute solutions; develop for Azure storage; implement Azure security; monitor, troubleshoot, and optimize Azure solutions; and connect to and consume Azure services and third-party services.

Developing Solutions for Microsoft Azure

Provision VMs

Configure VMs for remote access

Create ARM templates

Create container images for solutions by using Docker

Publish an image to the Azure Container Registry

Run containers by using Azure Container Registry

Implement Iaas solutions

create an Azure App Service Web App

Enable diagnostics logging

Deploy code to a web app

Configure web app settings including SSL, API, and connection strings

Implement autoscaling rules, including scheduled autoscaling, and scaling by operational or system metrics

Create Azure App Service Web App

Implement input and output bindings for a function

Implement function triggers by using data operations, timers, and webhooks

Implement Azure Durable Functions

Implement Azure Functions

Develop Azure compute solutions (25-30%)

Select the appropriate API for your solution

Implement partitioning schemes

Interact with data using the appropriate SDK

Set the appropriate consistency level for operations

Create Cosmos DB containers

Implement scaling (partitions, containers)

Implement server-side programming including stored procedures, triggers, and change feed notifications

Develop solutions that use Cosmos DB storage

Move items in Blob storage between storage accounts or containers

Set and retrieve properties and metadata

Implement data archiving and retention

Implement hot, cool, and archive storage

Develop solutions that use blob storage

Develop for Azure Storage (10-15%)

Implement OAuth2 authentication

Create and implement shared access signatures

Register apps and use Azure Active Directory to authenticate users

Control access to resources by using role-based access controls (RBAC)

Implement user authentication and authorization

Secure app configuration data by using the App Configuration and KeyVault API

Implement Managed Identities for Azure resources

Implement secure cloud solutions

Implement Azure Security (15-20%)

Develop code to implement CDNs in solutions

Configure cache and expiration policies for FrontDoor, CDNs, or Redis caches Store and retrieve data in Azure Redis cache

Integrate caching and content delivery within solutions

Configure instrumentation in an app or service by using Application Insights

Analyze log data and troubleshoot solutions by using Azure Monitor

Implement Application Insights Web Test and Alerts

Implement code that handles transient faults

Instrument solutions to support monitoring and logging

Monitor, troubleshoot, and optimize Azure solutions (10-15%)

Create a Logic App

Create a custom connector for Logic Apps

Create a custom template for Logic Apps

Develop an App Service Logic App

Create an APIM instance

Configure authentication for APIs

Define policies for APIs

Implement API Management

Implement solutions that use Azure Event Grid

Implement solutions that use Azure Notification Hubs

Implement solutions that use Azure Event Hub

Develop event-based solutions

Implement solutions that use Azure Service Bus

Implement solutions that use Azure Queue Storage queues

Develop message-based solutions

Connect to and consume Azure services and third-party services (25-30%)

Logic Apps is a cloud service that helps you connect services in a drag and drop UI

Overview - What is Azure Logic Apps?

<h2 id=longer-description>Longer description</h2> <p>Logic Apps is the only technology that provides a design-first approach intended for developers.</p> 

Run micro apps (small functions) without spinning up your own server. Pay only for used execution time, which can be very little

Durable functions

Azure Functions enable the creation of event driven, compute-on-demand systems that can be triggered 
    by various external events. Learn how to leverage functions to execute server-side logic and build serverless architectures.

Create serverless applications

<h2 id=longer-description>Longer description</h2> <p><strong>Features</strong></p> <ul> <li>Only pay for what you use</li> <li>Triggered by events</li> <li>Best for stateless logic</li> <li>Can be converted to a normal program if you want to run it more continuously.</li> </ul> <p><strong>Be careful of</strong></p> <ul> <li>Timeout is 5 minutes by default, but can be extended to 10 minutes. For function is triggered by HTTP then timeout is restricted to 2.5 minutes.</li> <li>Scaling can only be done with one new instance every 10 seconds, with a maximum of 200 instances.</li> </ul> <p>You define function apps to logically group and structure functions and a compute resource in Azure.</p> <ul> <li>Choosing a service plan <ul> <li>consumption - timeouts are applied</li> <li>app service plan - running on a VM so it&#39;s not server less, but functions can run continuously.</li> </ul> </li> <li>Storage account - mandatory and is used for logging and triggers</li> </ul> <h3 id=types-of-triggers>Types of triggers</h3> <p>Functions need to be triggered to run. A function can only have one trigger.</p> <table> <thead> <tr> <th>Trigger type</th> <th>Description</th> </tr> </thead> <tbody><tr> <td>Blob</td> <td>New or updated blobs. You specify path within the storage account that will filter what changes that will be triggered.</td> </tr> <tr> <td>Cosmos DB</td> <td>Inserts or updates of documents</td> </tr> <tr> <td>Event Grid</td> <td>Events are received</td> </tr> <tr> <td>HTTP</td> <td>On request</td> </tr> <tr> <td>MS Graph Events</td> <td>Incoming events from the Microsoft Graph</td> </tr> <tr> <td>Queue storage</td> <td>New message in queue</td> </tr> <tr> <td>Service Bus</td> <td>New message in queue</td> </tr> <tr> <td>Timer</td> <td>Run on schedule, specified as <a href="https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-timer?tabs=csharp#ncrontab-expressions">CRON expression</a></td> </tr> </tbody></table> <h3 id=bindings>Bindings</h3> <p>A declarative way to connect your function to a <a href=https://docs.microsoft.com/en-us/azure/azure-functions/functions-triggers-bindings#supported-bindings>lots of different services</a> without having to write the connection code for it. All bindings need the following properties:</p> <ul> <li>Name - the name used to access the binding in code</li> <li>Type - name of binding</li> <li>Direction - in or out</li> </ul> <p>Often, but not always, a connection string is required also.</p> <p>Bindings are defined in function.json like in this example:</p> <pre><code class=language-json><span class=hljs>{
  <span class=hljs-attr>&quot;bindings&quot;</span>: [
    {
      <span class=hljs-attr>&quot;name&quot;</span>: <span class=hljs-string>&quot;reservations&quot;</span>,
      <span class=hljs-attr>&quot;type&quot;</span>: <span class=hljs-string>&quot;queueTrigger&quot;</span>,
      <span class=hljs-attr>&quot;direction&quot;</span>: <span class=hljs-string>&quot;in&quot;</span>,
      <span class=hljs-attr>&quot;queueName&quot;</span>: <span class=hljs-string>&quot;newreservationsqueue&quot;</span>,
      <span class=hljs-attr>&quot;connection&quot;</span>: <span class=hljs-string>&quot;CONNECTION_TO_STORAGE_QUEUE&quot;</span>
    }
  ]
}</span></code></pre> <h4 id=input-bindings>Input bindings</h4> <table> <thead> <tr> <th>Type</th> <th>Description</th> </tr> </thead> <tbody><tr> <td>Blob storage</td> <td>Read blob</td> </tr> <tr> <td>Cosmos DB</td> <td>Read document</td> </tr> <tr> <td>Table Storage</td> <td>Read from table storage</td> </tr> <tr> <td>Durable Client</td> <td></td> </tr> <tr> <td>Orchestration Client</td> <td></td> </tr> <tr> <td>SignalR Connection Info</td> <td></td> </tr> <tr> <td>Microsoft Graph</td> <td>Read files from OneDrive, Excel and get auth tokens to interact with any Microsoft Graph API</td> </tr> <tr> <td>Mobile Apps</td> <td>Loads a record from a mobile table endpoint</td> </tr> </tbody></table> <h4 id=output-bindings>Output bindings</h4> <table> <thead> <tr> <th>Type</th> <th>Description</th> </tr> </thead> <tbody><tr> <td>Blob storage</td> <td>Write to blob storage</td> </tr> <tr> <td>Cosmos DB</td> <td>Write a new document</td> </tr> <tr> <td>Event hubs</td> <td>Write events to an event stream</td> </tr> <tr> <td>Queue Storage</td> <td>Write messages to a queue</td> </tr> <tr> <td>Service Bus</td> <td>Write messages to a queue or topic</td> </tr> <tr> <td>Table Storage</td> <td>Write to a storage table</td> </tr> <tr> <td>HTTP</td> <td>Send HTTP response when initiated by an HTTP trigger</td> </tr> <tr> <td>SendGrid</td> <td>Send email</td> </tr> <tr> <td>SignalR</td> <td></td> </tr> <tr> <td>Twilio SMS</td> <td>Send SMS message</td> </tr> <tr> <td>Microsoft Graph</td> <td>Write to OneDrive files, modify Excel docs and send email through Outlook</td> </tr> <tr> <td>Mobile Apps</td> <td>Writes a new record to a Mobile Apps table</td> </tr> <tr> <td>Notification Hubs</td> <td>Send push notifications</td> </tr> </tbody></table> <h3 id=streaming-log>Streaming log</h3> <table> <thead> <tr> <th>Language</th> <th>How to log</th> </tr> </thead> <tbody><tr> <td>JavaScript</td> <td>context.log(&#39;My logging text&#39;);</td> </tr> <tr> <td>C#</td> <td>log.Info(&quot;My logging text&quot;);</td> </tr> <tr> <td>PowerShell</td> <td>Write-Host &quot;My logging text&quot;</td> </tr> </tbody></table> <h3 id=security>Security</h3> <p>HTTP triggers are the only ones that can be called from Internet. It is therefore important that you secure them properly with an API key. Your options are:</p> <ul> <li>Anonymous (everyone can call the function)</li> <li>Function (this specific function has its own key)</li> <li>Admin (use global &quot;master&quot; key)</li> </ul> <p>Use this key by:</p> <ul> <li>Adding an HTTP header x-functions-key</li> <li>Adding a query string parameter code</li> </ul> <h3 id=durable-functions>Durable functions</h3> <p>Gives you the possibility to retain state between function calls.</p> <p><strong>Features</strong></p> <ul> <li>Event driven code able to wait for one or more external events before continuing.</li> <li>Chain functions together with fan-out and fan-in patterns.</li> <li>Orcestration and coordination in what order they should execute.</li> <li>State is automatically managed for you</li> </ul> <p><strong>Types of durable functions</strong></p> <table> <thead> <tr> <th>Type</th> <th>Description</th> </tr> </thead> <tbody><tr> <td>Client</td> <td>The entry point for the durable function logic</td> </tr> <tr> <td>Orchestrator</td> <td>The main part in defining a stateful workflow with these features:</td> </tr> </tbody></table> <ul> <li>Workflow is defined in code</li> <li>Functions can be called sync and async</li> <li>Function can be dehydrated while waiting for another one to finish and then rehydrated when response is returned.| |Activity|A unit of work containing the actual code doing what needs to be done.=|</li> </ul> <p><strong>Application patterns</strong></p> <table> <thead> <tr> <th>Type</th> <th>Description</th> </tr> </thead> <tbody><tr> <td>Function chaining</td> <td>Execute a sequence of functions in a specified order</td> </tr> <tr> <td>Fan out/fan in</td> <td>Runs many functions in parallel and wait for them all to finish</td> </tr> <tr> <td>Async HTTP APIs</td> <td>Used when you have longrunning external clients. Two endpoints offer a Start call and a GetStatus call returning info about progress.</td> </tr> <tr> <td>Monitor</td> <td>A recurring proces to look for condition changes and then do the work</td> </tr> <tr> <td>Human interaction</td> <td>I.e. an approval process where function can escalate if approval isn&#39;t received within a certain time</td> </tr> </tbody></table> <p><strong>Example of timer usage</strong></p> <pre><code class=language-javascript><span class=hljs><span class=hljs-keyword>const</span> df = <span class=hljs-built_in>require</span>(<span class=hljs-string>&quot;durable-functions&quot;</span>);
<span class=hljs-keyword>const</span> moment = <span class=hljs-built_in>require</span>(<span class=hljs-string>&quot;moment&quot;</span>);

<span class=hljs-built_in>module</span>.exports = df.orchestrator(<span class=hljs-function><span class=hljs-keyword>function</span>*(<span class=hljs-params>context</span>) </span>{
    <span class=hljs-keyword>const</span> deadline = moment.utc(context.df.currentUtcDateTime).add(<span class=hljs-number>30</span>, <span class=hljs-string>&quot;s&quot;</span>);

    <span class=hljs-keyword>const</span> activityTask = context.df.callActivity(<span class=hljs-string>&quot;GetQuote&quot;</span>);
    <span class=hljs-keyword>const</span> timeoutTask = context.df.createTimer(deadline.toDate());

    <span class=hljs-keyword>const</span> winner = <span class=hljs-keyword>yield</span> context.df.Task.any([activityTask, timeoutTask]);
    <span class=hljs-keyword>if</span> (winner === activityTask) {
        <span class=hljs-comment>// success case</span>
        timeoutTask.cancel();
        <span class=hljs-keyword>return</span> <span class=hljs-literal>true</span>;
    }
    <span class=hljs-keyword>else</span>
    {
        <span class=hljs-comment>// timeout case</span>
        <span class=hljs-keyword>return</span> <span class=hljs-literal>false</span>;
    }
});</span></code></pre> <h3 id=local-development>Local development</h3> <p>The functions editor in Azure does not support editing functions created locally. A local functions project can contain a number of functions, all sharing the same language runtime. It basically equals to a function app in Azure. </p> <p><strong>Function core tools</strong></p> <table> <thead> <tr> <th>Command</th> <th>Description</th> </tr> </thead> <tbody><tr> <td><code>func init</code></td> <td>Create a new functions project. You&#39;ll select worker runtime and from available languages in that runtime. The files created depend on runtime, but these two files are always included:<ul><li><strong>host.json</strong> - runtime configuration values, used both when running locally and in Azure</li><li><strong>local.settings.json</strong> - settings used when only running locally</li></ul></td> </tr> <tr> <td><code>func new</code></td> <td>Create a new function. You&#39;ll be asked to select template</td> </tr> <tr> <td><code>func start</code></td> <td>Run from project folder and all functions will be started. If you run it in the cloud shell you might need to start the function in the background by running <code>func start &amp;&gt; ~/output.txt &amp;</code> and then use <code>pkill func</code> to stop it.</td> </tr> <tr> <td><code>func azure functionapp publish &lt;app_name&gt;</code></td> <td>Publish a function project to Azure. <code>&lt;app_name&gt;</code> is the function app in Azure.<br>Important to remember: <ul><li>Make sure you test app before deploying</li><li>All existing functions in the target function app will be deleted</li><li>There&#39;s no relationship between the function project and the function app</li><li>HTTP function created by the core tools have &quot;function&quot; as authorization level.</li></ul></td> </tr> </tbody></table> 

(Intermediate) Discover how Azure Functions allows you to easily write serverless code in your language of preference to handle events at scale, with minimal overhead and cost.

Pluralsight: Azure Functions Fundamentals

(Beginner) Azure Functions is the quickest and easiest way to get your code running in Azure. This course will teach you how to create your own serverless functions, integrate with other services, and host them in Azure or Docker containers.

Pluralsight: Create Serverless Functions

(Beginner) Durable Functions enables you to create reliable stateful workflows with Azure Functions. This course teaches you how to implement 'fan-out fan-in' patterns, pause waiting for human interaction, and how to debug, deploy, and monitor your workflows.

Pluralsight: Azure Durable Functions Fundamentals

Strategies for testing your code in Azure Functions

<h2 id=longer-description>Longer description</h2> <h3 id=default-properties-when-adding-a-new-document>Default properties when adding a new document</h3> <table> <thead> <tr> <th>Property</th> <th>Description</th> </tr> </thead> <tbody><tr> <td>_rid</td> <td>A hierarchical unique identifier, mainly used internally</td> </tr> <tr> <td>_self</td> <td>Unique addressable URI for this document</td> </tr> <tr> <td>_etag</td> <td>Tag used for optimistic concurrency</td> </tr> <tr> <td>_attachments</td> <td>Addressable path for the attachments resource</td> </tr> <tr> <td>_ts</td> <td>Time stamp when last updated</td> </tr> </tbody></table> <p>Throughput is billed per database. You can have several databases in a Cosmos DB account.</p> <p>One database can contain many containers. Partition key is specified per container.</p> 

(Intermediate) Microsoft's Azure Cosmos DB is becoming an essential tool for creating powerful global web and mobile applications. This course will teach you how to design databases and build applications using the various Cosmos DB APIs and supported data models.

Pluralsight: Learning Azure Cosmos DB

This is a very nice service that automates so much for you. If you haven't tried it out yet then go ahead right away.

Web apps in Azure allow you to publish and manage your website easily without 
    having to work with the underlying servers, storage, or network assets. Instead, you can focus 
    on your website features and rely on the robust Azure platform to provide secure access to your site. 

Learn how to deploy a website to Azure with Azure App Services

<h2 id=longer-description>Longer description</h2> <p>This is such a long description</p> 

Centralized handling of app settings and feature toggles. Enable apps to reload settings without restarting them.

How to configure App Configuration in a .NET Core service

Using Azure App Configuration in a Worker Service

Create an Azure Functions app with Azure App Configuration

Navigate Azure

Learning the cloud, one service at the time

Azure services

Logic App

Function Apps

Cosmos DB

App Service

App Configuration

Azure Exams

AZ-204 Developing Solutions for Microsoft Azure