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.

Practice

1. What is the primary purpose of Azure Logic Apps in cloud workflows?

easy

A. To create automated workflows visually without writing code

B. To manually manage virtual machines

C. To store large amounts of data

D. To write complex backend applications

Solution

1. Step 1: Understand Logic Apps purpose

   Logic Apps are designed to automate workflows visually, making it easy to connect services without coding.

2. Step 2: Compare options

   Options B, C, and D describe other Azure services or tasks unrelated to Logic Apps' main function.

3. Final Answer:

   To create automated workflows visually without writing code -> Option A

4. Quick Check:

   Logic Apps = Visual automation [OK]

Hint: Logic Apps automate visually, no code needed [OK]

Common Mistakes:

• Confusing Logic Apps with data storage services
• Thinking Logic Apps manage virtual machines
• Assuming Logic Apps require coding

2. Which of the following is the correct way to start a Logic App workflow?

easy

A. By creating a virtual machine

B. By writing a function in C#

C. By defining a trigger that listens for an event

D. By uploading a database file

Solution

1. Step 1: Identify how Logic Apps start

   Logic Apps begin with a trigger that waits for an event or condition to start the workflow.

2. Step 2: Eliminate incorrect options

   Options B, C, and D are unrelated to Logic Apps workflow initiation.

3. Final Answer:

   By defining a trigger that listens for an event -> Option C

4. Quick Check:

   Logic Apps start with triggers [OK]

Hint: Logic Apps always start with a trigger [OK]

Common Mistakes:

• Thinking code is needed to start Logic Apps
• Confusing Logic Apps with VM or database setup
• Ignoring the trigger concept

3. Consider a Logic App with a trigger on receiving an email and an action to save attachments to OneDrive. What happens when an email with two attachments arrives?

medium

A. Only the first attachment is saved, the second is ignored

B. Attachments are deleted from the email

C. The Logic App fails with an error

D. Both attachments are saved to OneDrive automatically

Solution

1. Step 1: Understand the trigger and action

   The trigger activates on email receipt; the action processes all attachments.

2. Step 2: Analyze behavior with multiple attachments

   Logic Apps handle each attachment, saving both to OneDrive automatically.

3. Final Answer:

   Both attachments are saved to OneDrive automatically -> Option D

4. Quick Check:

   Multiple attachments = all saved [OK]

Hint: Logic Apps process all items in a trigger event [OK]

Common Mistakes:

• Assuming only one attachment is processed
• Expecting failure on multiple attachments
• Thinking attachments get deleted automatically

4. You created a Logic App with a trigger on HTTP request and an action to send an email. The email is never sent after calling the HTTP endpoint. What is the most likely issue?

medium

A. The HTTP trigger URL was not copied correctly

B. The email action is missing a recipient address

C. The Logic App is not connected to a virtual network

D. The Logic App requires a database connection

Solution

1. Step 1: Check trigger and action setup

   The HTTP trigger activates the workflow; the email action must have a recipient to send mail.

2. Step 2: Identify missing email recipient

   If the recipient is missing, the email action silently fails or does not send.

3. Final Answer:

   The email action is missing a recipient address -> Option B

4. Quick Check:

   Email action needs recipient [OK]

Hint: Always set email recipient in Logic Apps [OK]

Common Mistakes:

• Assuming trigger URL copy error causes no email
• Thinking virtual network is required for email
• Believing database connection is needed

5. You want to build a Logic App that triggers when a file is added to an FTP server, then copies the file to Azure Blob Storage, but only if the file size is less than 5 MB. How should you design this workflow?

hard

A. Use an FTP trigger, add a condition to check file size, then copy to Blob Storage if condition is true

B. Use a Blob Storage trigger and copy files to FTP server

C. Use an FTP trigger and copy all files to Blob Storage without conditions

D. Use a manual trigger and upload files to Blob Storage

Solution

1. Step 1: Select correct trigger

   The workflow must start when a file is added to FTP, so use an FTP trigger.

2. Step 2: Add condition to check file size

   Insert a condition action to verify if the file size is less than 5 MB before copying.

3. Step 3: Copy file to Blob Storage if condition met

   If the condition is true, perform the copy action to Azure Blob Storage.

4. Final Answer:

   Use an FTP trigger, add a condition to check file size, then copy to Blob Storage if condition is true -> Option A

5. Quick Check:

   Trigger + condition + action = correct design [OK]

Hint: Use condition to filter files before action [OK]

Common Mistakes:

• Using wrong trigger type
• Skipping file size condition
• Copying files without filtering
• Using manual trigger instead of automatic