OKTA OKTA Workflows and Automation 2

Question 1

In Okta Workflows, what is a 'Table'?

Accepted Answer

A persistent data store within Workflows for storing records

Answer

Tables in Okta Workflows are built-in data stores that allow Flows to read, write, and update structured records without an external database.

Question 2

What is the purpose of the 'List' card type in Okta Workflows?

Accepted Answer

To iterate over or manipulate collections of items within a Flow

Answer

List cards in Okta Workflows allow you to perform operations on arrays or collections, such as filtering, mapping, or looping over items.

Question 3

When using Okta Workflows to deprovision a user, which action would you use to remove them from all their assigned Okta groups?

Accepted Answer

Remove User from All Groups

Answer

The 'Remove User from All Groups' action card in the Okta connector removes a deprovisioned user from every group they belong to in Okta.

Question 4

Which feature of Okta Workflows allows you to run a subflow from within another Flow?

Accepted Answer

Child Flow / Helper Flow

Answer

Helper Flows (also called Child Flows) let you encapsulate reusable logic that can be called from multiple parent Flows, promoting modularity.

Question 5

What is the maximum number of concurrent Flow executions Okta Workflows supports by default per tenant?

Accepted Answer

100

Answer

By default, Okta Workflows allows up to 100 concurrent Flow executions per tenant; this limit can be increased for high-volume use cases.

OKTA - OKTA Certified Professional Practice Test