Logic Apps for visual workflows in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a Logic App trigger that starts when an HTTP request is received.

Azure

{
  "definition": {
    "triggers": {
      "manual": {
        "type": "[1]"
      }
    }
  }
}

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

AHttpRequest

BRequest

CHttpTrigger

DHttp

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'HttpTrigger' which is from Azure Functions, not Logic Apps.

Using 'Http' which is the 'kind' property, not the type.

Using 'HttpRequest' which is not a valid trigger type.

The trigger type for starting a Logic App on an HTTP request is Request.

2fill in blank

medium

Complete the code to add an action that sends an email using Office 365 connector.

Azure

{
  "actions": {
    "send_email": {
      "type": "[1]",
      "inputs": {
        "host": {
          "connectionName": "office365",
          "operationId": "SendEmail"
        },
        "parameters": {
          "To": "[e-mail]",
          "Subject": "Hello",
          "Body": "Welcome to Logic Apps!"
        }
      }
    }
  }
}

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

AEmail

BHttp

CSendEmail

DApiConnection

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Http' which is for HTTP calls, not connectors.

Using 'SendEmail' which is an operation, not a type.

Using 'Email' which is not a valid action type.

The action type to call a connector like Office 365 is ApiConnection.

3fill in blank

hard

Fix the error in the condition expression to check if the variable 'count' is greater than 5.

Azure

{
  "actions": {
    "check_count": {
      "type": "If",
      "expression": "@greater([1], 5)",
      "actions": {}
    }
  }
}

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

Avariables('count')

Bcount

Cvariables[count]

Dvariables.get('count')

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'count' directly which is undefined.

Using bracket notation which is invalid in Logic Apps expressions.

Using 'variables.get' which is not supported.

To access a variable in Logic Apps expressions, use variables('count').

4fill in blank

hard

Fill both blanks to create a loop that iterates over an array variable 'items' and appends each item to a string variable 'result'.

Azure

{
  "actions": {
    "for_each": {
      "type": "Foreach",
      "inputs": {
        "items": [1]
      },
      "actions": {
        "append_string": {
          "type": "AppendToStringVariable",
          "inputs": {
            "name": "result",
            "value": [2]
          }
        }
      }
    }
  }
}

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

Avariables('items')

Bitems()

Citem()

Dvariables('result')

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'items()' which is not a variable or function here.

Using 'variables('result')' as the value to append instead of current item.

Using 'variables('items')' incorrectly inside the loop for current item.

The loop iterates over variables('items'). Inside the loop, item() gets the current element.

5fill in blank

hard

Fill all three blanks to define a Logic App action that initializes a variable named 'count' with integer type and value 0.

Azure

{
  "actions": {
    "init_count": {
      "type": "InitializeVariable",
      "inputs": {
        "variables": [
          {
            "name": [1],
            "type": [2],
            "value": [3]
          }
        ]
      }
    }
  }
}

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

A"count"

B"integer"

C0

D"int"

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'int' instead of 'integer' for type.

Not quoting the variable name and type.

Using a string '0' instead of number 0 for value.

The variable name is "count", type is "integer", and initial value is 0.

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