AZ-305 ยท Application architecture design
Logic Apps Consumption vs Standard vs Functions
Azure Logic Apps (Consumption vs Standard) with connectors, versus Azure Functions and Durable Functions, for integrating SaaS and enterprise systems.
Key points
- Logic Apps: low-code workflows, triggers, actions, 1,400+ connectors.
- Consumption: multitenant, one workflow per resource, pay per execution.
- Standard: single-tenant, many workflows, stateful or stateless, built-in connectors in-process, VNet, data in region.
- Functions: code-first, event-triggered; Durable Functions: stateful orchestrations in code.
- Connectors and designer: Logic Apps; custom code: Functions.
Source: https://learn.microsoft.com/en-us/azure/logic-apps/single-tenant-overview-compare
Practice questions
How many workflows can a single Consumption logic app resource contain?
- Only one
- Up to 10
- Up to 100
- Unlimited
Show answer
Answer: A. Only one
A Consumption logic app maps one-to-one to a single workflow. The Standard logic app is the one that can host multiple stateful and stateless workflows, much like a function app hosts several functions.
Which statements about stateless workflows in Standard logic apps are correct?
- They keep run state in memory instead of external storage
- Runs interrupted by an outage are not restored automatically
- They can start from the Recurrence (schedule) trigger
- They store full run history by default
- They are best suited to large messages of several MB
Show answer
Answer: A. They keep run state in memory instead of external storage, B. Runs interrupted by an outage are not restored automatically
Stateless workflows keep inputs, outputs and state in memory only, so they are fast and cheap but interrupted runs are not restored automatically, and they work best with small payloads (under about 64 KB). They can use only push triggers, so the Recurrence trigger is unavailable. Run history is not stored by default.
A Standard logic app workflow can be changed from stateful to stateless after it is created without any side effects.
Show answer
Answer: False
False. The stateful or stateless choice is made at creation time; changing the workflow type afterwards results in runtime errors. Create a new workflow of the other type instead.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
