Function App creation in Azure - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an Azure Function App?

An Azure Function App is a service that lets you run small pieces of code (functions) in the cloud without managing servers. It automatically scales and only charges you for the time your code runs.

intermediate

Which hosting plan options are available when creating an Azure Function App?

You can choose between Consumption Plan (serverless, auto-scaling), Premium Plan (more powerful, always warm), and Dedicated (App Service) Plan (fixed resources).

beginner

Why do you need a Storage Account when creating a Function App?

The Storage Account stores function code, triggers, and logs. It is required for the Function App to work properly.

beginner

What is the purpose of the Runtime Stack setting during Function App creation?

The Runtime Stack defines the programming language and environment your function code will run on, like Node.js, Python, or .NET.

intermediate

How does Azure Function App scaling work in the Consumption Plan?

In the Consumption Plan, Azure automatically adds or removes compute resources based on the number of incoming events, so your app scales out when needed and scales in when idle.

What is the main benefit of using an Azure Function App?

A Run code without managing servers

B Store large files

C Create virtual machines

D Manage databases

Azure Function Apps let you run code without worrying about servers, making it easy to build scalable apps.

Which Azure service must you create alongside a Function App to store its code and logs?

A Virtual Network

B App Service Plan

C SQL Database

D Storage Account

A Storage Account is required to store function code, triggers, and logs.

Which hosting plan automatically scales your Function App based on demand?

A Dedicated Plan

B Consumption Plan

C Premium Plan

D Basic Plan

The Consumption Plan automatically scales your app based on incoming events.

What does the Runtime Stack setting specify when creating a Function App?

A Scaling rules

B Storage location

C Programming language environment

D Network settings

Runtime Stack defines the language and environment your function code runs on.

Which of these is NOT a valid trigger type for Azure Functions?

A Virtual Machine Trigger

B Timer Trigger

C HTTP Trigger

D Blob Storage Trigger

Virtual Machine Trigger is not a valid Azure Function trigger type.

Explain the steps and key settings needed to create an Azure Function App.

Think about what resources and options you must pick before your function can run.

Describe how Azure Function App scaling works in the Consumption Plan and why it is useful.

Consider how the app adjusts resources when traffic changes.

Practice

1. What is the main purpose of an Azure Function App?

easy

A. To run small pieces of code in the cloud without managing servers

B. To store large amounts of data in the cloud

C. To create virtual machines for hosting websites

D. To manage user identities and access

Solution

1. Step 1: Understand Azure Function App purpose

   Azure Function Apps are designed to run code triggered by events without needing to manage servers.

2. Step 2: Compare options

   Options A, B, and D describe other Azure services like virtual machines, storage, and identity management, not Function Apps.

3. Final Answer:

   To run small pieces of code in the cloud without managing servers -> Option A

4. Quick Check:

   Function Apps run code serverlessly [OK]

Hint: Function Apps run code without servers [OK]

Common Mistakes:

• Confusing Function Apps with storage services
• Thinking Function Apps create virtual machines
• Mixing up Function Apps with identity services

2. Which Azure CLI command correctly creates a Function App named myfuncapp in resource group mygroup with a storage account mystorage and runtime python?

easy

A. az function create --resource mygroup --name myfuncapp --storage-account mystorage --runtime python

B. az functionapp new --group mygroup --app-name myfuncapp --storage mystorage --runtime python

C. az create functionapp --resource-group mygroup --name myfuncapp --storage mystorage --runtime python

D. az functionapp create --resource-group mygroup --name myfuncapp --storage-account mystorage --runtime python

Solution

1. Step 1: Identify correct Azure CLI syntax

   The correct command to create a Function App is az functionapp create with parameters --resource-group, --name, --storage-account, and --runtime.

2. Step 2: Compare options

   az functionapp create --resource-group mygroup --name myfuncapp --storage-account mystorage --runtime python matches the correct syntax. Options B, C, and D use incorrect commands or parameter names.

3. Final Answer:

   az functionapp create --resource-group mygroup --name myfuncapp --storage-account mystorage --runtime python -> Option D

4. Quick Check:

   Use az functionapp create with correct flags [OK]

Hint: Use 'az functionapp create' with correct flags [OK]

Common Mistakes:

• Using wrong command like 'az functionapp new'
• Mixing parameter names like '--group' instead of '--resource-group'
• Omitting required parameters

3. What will happen if you run this Azure CLI command?

az functionapp create --resource-group mygroup --name myfuncapp --storage-account mystorage --runtime node --runtime-version 14

medium

A. Fails because --runtime-version is not a valid parameter

B. Creates a Function App named myfuncapp with Node.js runtime version 14

C. Creates a Function App but ignores the runtime version

D. Creates a Function App with default runtime version

Solution

1. Step 1: Understand parameters in the command

   The command uses --runtime node and specifies --runtime-version 14, which is valid to set Node.js version 14.

2. Step 2: Check Azure CLI behavior

   Azure CLI supports --runtime-version to specify the runtime version, so the Function App will be created with Node.js 14.

3. Final Answer:

   Creates a Function App named myfuncapp with Node.js runtime version 14 -> Option B

4. Quick Check:

   Runtime and version flags create correct environment [OK]

Hint: Use --runtime and --runtime-version to specify environment [OK]

Common Mistakes:

• Thinking --runtime-version is invalid
• Assuming runtime version is ignored
• Confusing runtime with storage account

4. You tried to create a Function App with this command:

az functionapp create --resource-group mygroup --name myfuncapp --storage mystorage --runtime python

But it failed. What is the most likely cause?

medium

A. The parameter --storage is incorrect; it should be --storage-account

B. The runtime python is not supported

C. Resource group mygroup does not exist

D. Function App name myfuncapp is invalid

Solution

1. Step 1: Check command parameters

   The parameter for storage account must be --storage-account, not --storage.

2. Step 2: Validate other options

   Python runtime is supported, resource group existence is not confirmed but the error is about parameter, and the name looks valid.

3. Final Answer:

   The parameter --storage is incorrect; it should be --storage-account -> Option A

4. Quick Check:

   Use correct parameter names in CLI commands [OK]

Hint: Use --storage-account, not --storage [OK]

Common Mistakes:

• Using wrong parameter names
• Assuming runtime unsupported without checking
• Ignoring error messages about parameters

5. You want to create a Function App that runs Python code triggered every hour. Which two Azure services must you configure together to achieve this?

hard

A. Function App and Azure SQL Database

B. Function App and Azure Blob Storage

C. Function App and Timer Trigger

D. Function App and Azure Virtual Machine

Solution

1. Step 1: Identify the trigger for scheduled execution

   Azure Function Apps use triggers to start code. For hourly runs, a Timer Trigger is used.

2. Step 2: Understand service roles

   Blob Storage, Virtual Machines, and SQL Database are not used to schedule function runs but serve other purposes.

3. Final Answer:

   Function App and Timer Trigger -> Option C

4. Quick Check:

   Timer Trigger schedules Function App runs [OK]

Hint: Use Timer Trigger for scheduled Function Apps [OK]

Common Mistakes:

• Confusing storage or database with scheduling
• Thinking VM is needed for Function Apps
• Ignoring triggers in Function Apps