Logic Apps for visual workflows in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

What happens when a Logic App action fails?

In Azure Logic Apps, if an action inside a workflow fails, what is the default behavior of the workflow?

A The workflow pauses and waits for manual intervention before continuing.

B The workflow ignores the failure and continues to the next action.

C The workflow retries the failed action indefinitely until it succeeds.

D The entire workflow stops immediately and marks the run as failed.

💡 Hint

Think about how workflows handle errors by default to avoid unexpected results.

By default, when an action fails in a Logic App, the workflow run stops immediately and is marked as failed. This prevents further actions from running on potentially invalid data.

❓ Architecture

intermediate

Choosing triggers for Logic Apps

You want to start a Logic App workflow every time a new file is uploaded to an Azure Blob Storage container. Which trigger should you use?

A HTTP Request trigger that waits for an external call to start the workflow.

B Blob Storage trigger that fires when a new blob is created in the container.

C Recurrence trigger that runs every 5 minutes and checks for new files.

D Manual trigger that requires a user to start the workflow.

💡 Hint

Consider triggers that respond automatically to storage events.

The Blob Storage trigger is designed to start a Logic App when a new blob is created, making it the best choice for this scenario.

❓ security

advanced

Securing HTTP triggers in Logic Apps

You have a Logic App with an HTTP Request trigger. What is the best way to secure this trigger to prevent unauthorized access?

A Use Azure Active Directory (AAD) OAuth authentication for the trigger.

B Require an API key passed as a query parameter in the URL.

C Use a shared access signature (SAS) token in the trigger URL.

D Leave the trigger URL public and rely on IP filtering in the Logic App.

💡 Hint

Think about the most secure and manageable authentication method supported by Logic Apps.

Using Azure Active Directory OAuth authentication provides strong security by requiring valid tokens and integrates well with Azure identity management.

✅ Best Practice

advanced

Optimizing Logic Apps for cost and performance

You have a Logic App that runs very frequently and processes many messages. Which practice helps reduce costs and improve performance?

A Add delay actions between steps to slow down the workflow and reduce load.

B Use nested Logic Apps to split the workflow into smaller parts and call them sequentially.

C Use the Standard plan with Integration Service Environment (ISE) for dedicated resources.

D Use the Consumption plan and add parallel branches to process messages simultaneously.

💡 Hint

Consider plans that provide dedicated resources for high-volume workloads.

The Standard plan with Integration Service Environment offers dedicated compute resources, which improves performance and can reduce costs for high-frequency Logic Apps.

🧠 Conceptual

expert

Understanding retry policies in Logic Apps

Consider a Logic App action configured with a retry policy of 3 attempts and an interval of 10 seconds. The action fails on the first two attempts but succeeds on the third. How long will the Logic App wait before the third attempt?

A It waits 10 seconds before the third attempt after the second failure.

B It waits 0 seconds before the third attempt because retries happen immediately.

C It waits 20 seconds before the third attempt, adding intervals cumulatively.

D It waits 30 seconds before the third attempt, multiplying the interval by the attempt number.

💡 Hint

Think about how fixed interval retry policies work between attempts.

With a fixed interval retry policy, the Logic App waits the specified interval (10 seconds) after each failure before retrying. So before the third attempt, it waits 10 seconds after the second failure.