Why serverless matters in Azure - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an Azure Function App using serverless compute.

Azure

az functionapp create --resource-group myResourceGroup --consumption-plan-location westus --runtime python --name myFunctionApp --storage-account [1]

Drag options to blanks, or click blank then click option'

Amystorageaccount

Bmyfunctionplan

Cmyappserviceplan

Dmyresourcegroup

Attempts:

3 left

💡 Hint

Common Mistakes

Using the app service plan name instead of storage account

Confusing resource group with storage account

The storage account is required to create a Function App in Azure serverless. It stores code and triggers.

2fill in blank

medium

Complete the code to create a serverless Azure Function with the correct trigger type.

Azure

func new --name HttpTrigger --template [1]

Drag options to blanks, or click blank then click option'

Acontainertrigger

Bvmtrigger

CHttpTrigger

Dappservicetrigger

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing triggers related to VMs or containers which are not serverless triggers

The HTTP trigger is a common serverless trigger that runs functions on web requests.

3fill in blank

hard

Fix the error in the Azure CLI command to scale a serverless function app automatically.

Azure

az functionapp plan update --name myFunctionAppPlan --resource-group myResourceGroup --sku [1]

Drag options to blanks, or click blank then click option'

AY1

BS1

CP1v2

DB1

Attempts:

3 left

💡 Hint

Common Mistakes

Using standard or premium SKUs which are not serverless consumption plans

The Y1 SKU is the consumption (serverless) plan that enables automatic scaling.

4fill in blank

hard

Fill both blanks to configure an Azure Function App to use serverless and enable monitoring.

Azure

az functionapp create --resource-group myResourceGroup --plan [1] --name myFunctionApp --storage-account myStorageAccount --runtime dotnet --app-insights [2]

Drag options to blanks, or click blank then click option'

AConsumptionPlan

BStandardPlan

CmyAppInsights

DmyStorageAccount

Attempts:

3 left

💡 Hint

Common Mistakes

Using a standard plan instead of consumption plan

Confusing storage account with App Insights

The ConsumptionPlan enables serverless scaling, and myAppInsights enables monitoring with Application Insights.

5fill in blank

hard

Fill all three blanks to define a serverless Azure Function with an HTTP trigger and environment variable.

Azure

func init MyFunctionProj --worker-runtime [1]
func new --name HttpTrigger --template [2] --authlevel anonymous
az functionapp config appsettings set --name myFunctionApp --resource-group myResourceGroup --settings [3]=Production

Drag options to blanks, or click blank then click option'

Apython

BHTTP trigger

CENVIRONMENT

Dnode

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong runtime language

Confusing trigger template names

Incorrect environment variable key

The worker runtime is python, the trigger template is HTTP trigger, and the environment variable key is ENVIRONMENT.