Workflows for orchestration in GCP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of Workflows in Google Cloud?

Workflows help you connect and automate different cloud services by defining a sequence of steps that run automatically, like a recipe for tasks.

intermediate

How does Workflows handle errors during execution?

Workflows can catch errors and decide what to do next, like retrying a step or running a different path, so the process can continue smoothly.

beginner

What is a step in a Workflow?

A step is a single action in a Workflow, such as calling an API, waiting for a response, or running a condition to decide the next step.

beginner

Why is Workflows considered serverless?

Because you don't manage any servers or infrastructure; Google Cloud runs and scales the Workflow automatically for you.

intermediate

How can Workflows improve cloud application reliability?

By automating retries, error handling, and controlling the order of tasks, Workflows reduce manual errors and make processes more reliable.

What does a Workflow in Google Cloud primarily do?

A Manages virtual machines

B Stores large amounts of data

C Automates and sequences cloud service tasks

D Creates user accounts

Workflows automate and sequence tasks across cloud services to simplify complex processes.

Which of the following is NOT a feature of Workflows?

A Manual server management

B Conditional branching

C Calling APIs in sequence

D Error handling and retries

Workflows are serverless, so you do not manage servers manually.

How does Workflows handle decision-making in a process?

A By random selection

B Requires manual input each step

C Only runs tasks in parallel

D Using conditional steps to choose paths

Workflows use conditions to decide which steps to run next automatically.

What kind of tasks can Workflows connect?

A Only database queries

B APIs, cloud functions, and services

C Only virtual machine setups

D Only user interface designs

Workflows can connect various cloud services including APIs and functions.

Why is using Workflows beneficial for cloud automation?

A It reduces manual work and errors

B It increases manual server setup

C It slows down processes

D It requires complex coding

Workflows automate tasks to reduce manual effort and mistakes.

Explain how Google Cloud Workflows help automate cloud tasks.

Think about how a recipe guides cooking steps automatically.

Describe the benefits of using Workflows for cloud orchestration.

Consider how automation helps avoid mistakes and saves time.

Practice

1. What is the main purpose of Google Cloud Workflows?

easy

A. To store large amounts of data securely

B. To automate and coordinate multiple cloud services in a sequence

C. To create virtual machines for computing

D. To monitor network traffic in real-time

Solution

1. Step 1: Understand the role of Workflows

   Workflows are designed to automate tasks by connecting different cloud services step-by-step.

2. Step 2: Compare options with this role

   Options B, C, and D describe storage, computing, and monitoring, which are not the main purpose of Workflows.

3. Final Answer:

   To automate and coordinate multiple cloud services in a sequence -> Option B

4. Quick Check:

   Workflows automate cloud tasks = A [OK]

Hint: Workflows connect services step-by-step to automate tasks [OK]

Common Mistakes:

• Confusing Workflows with storage or compute services
• Thinking Workflows monitor network traffic
• Assuming Workflows create virtual machines

2. Which of the following is the correct way to start a step in a Google Cloud Workflow YAML?

easy

A. steps:

B. start:

C. main:

D. execute:

Solution

1. Step 1: Recall the YAML structure for Workflows

   The main entry point for a workflow is defined under the main: key.

2. Step 2: Check other options

   Options like steps:, start:, and execute: are not valid top-level keys for starting a workflow.

3. Final Answer:

   main: -> Option C

4. Quick Check:

   Workflow starts with main: in YAML [OK]

Hint: Workflows start with main: block in YAML [OK]

Common Mistakes:

• Using steps: instead of main:
• Confusing start: as the entry point
• Trying execute: which is invalid

3. Given this snippet of a workflow YAML:

main:
  steps:
  - call: http.get
    args:
      url: "https://example.com/api"
  - return: ${steps[0].body.status}

What will the workflow return if the HTTP GET response body is {"status": "success"}?

medium

A. "success"

B. {"status": "success"}

C. An error because of wrong syntax

D. null

Solution

1. Step 1: Understand the call and return steps

   The first step calls an HTTP GET and stores the response in steps[0]. The second step returns the status field from the response body.

2. Step 2: Extract the status value from the response

   The response body is {"status": "success"}, so steps[0].body.status is "success".

3. Final Answer:

   "success" -> Option A

4. Quick Check:

   Return status field from HTTP response = "success" [OK]

Hint: Return uses ${steps[index].body.field} to get JSON values [OK]

Common Mistakes:

• Returning the whole body instead of the status field
• Syntax errors in accessing steps array
• Assuming null if not parsed correctly

4. Identify the error in this workflow snippet:

main:
  steps:
  - call: http.get
    args:
      url: "https://example.com/api"
  - return: steps[0].body.status

medium

A. Missing quotes around the URL

B. Incorrect indentation of steps

C. http.get is not a valid call

D. Missing ${} around the expression in return

Solution

1. Step 1: Check expression syntax in return

   In Workflows YAML, expressions must be wrapped in ${} to be evaluated.

2. Step 2: Verify other parts

   Indentation is correct, http.get is valid, and URL is quoted properly.

3. Final Answer:

   Missing ${} around the expression in return -> Option D

4. Quick Check:

   Expressions need ${} to evaluate in return [OK]

Hint: Wrap expressions in ${} to evaluate in workflow YAML [OK]

Common Mistakes:

• Forgetting ${} around expressions
• Misaligning YAML indentation
• Assuming http.get is invalid
• Not quoting URLs

5. You want to create a workflow that calls two APIs in sequence, but only calls the second API if the first returns status "ok". Which workflow feature helps you implement this conditional logic?

hard

A. Using switch or if steps to check the first API's response

B. Using parallel steps to call both APIs at the same time

C. Using retry to repeat the first API call until status is ok

D. Using return to stop the workflow after the first call

Solution

1. Step 1: Understand conditional execution in workflows

   Workflows support switch or if steps to decide which steps run based on conditions.

2. Step 2: Match the requirement

   To call the second API only if the first returns "ok", use if or switch to check the first response before proceeding.

3. Final Answer:

   Using switch or if steps to check the first API's response -> Option A

4. Quick Check:

   Conditional steps use if/switch to control flow [OK]

Hint: Use if or switch to run steps conditionally in workflows [OK]

Common Mistakes:

• Using parallel steps which run both APIs simultaneously
• Using retry which repeats calls but doesn't conditionally run next
• Using return which ends workflow early