I85PREP
⌘ K
monday.com Work Management Advanced study materials
monday.com Work Management Advanced study resources

monday.com Work Management Advanced practice questions

One question at a time. Build your monday.com Work Management Advanced understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Board structure, data model and item hierarchy

In the monday.com Work Management data model, which sequence correctly orders the containers from broadest to most granular?

  1. Account → Group → Workspace → Board → Item
  2. Board → Workspace → Item → Group → Subitem
  3. Workspace → Board → Group → Item → Subitem Correct answer.
  4. Workspace → Group → Board → Subitem → Item

Explanation

Workspaces contain boards, each board contains groups, groups hold items, and items can hold subitems. The account sits above workspaces but is not part of the board-level item hierarchy shown here.

Question 2Board structure, data model and item hierarchy

A project board is divided into phases such as Discovery, Build, and Launch. Which board element is designed to segment items into those phases while keeping them on the same board?

  1. A group Correct answer.
  2. A subitem
  3. A dashboard
  4. A workspace

Explanation

Groups are colored sections inside a board used to organize items into stages, teams, or categories. They keep items on one board, unlike separate boards, and they are not child records or reporting surfaces.

Question 3Board structure, data model and item hierarchy

Which statement best describes a subitem in a monday.com Work Management board?

  1. A duplicated item that stays linked to the original item's activity log.
  2. A separate board that appears as a tab in the same workspace.
  3. A column that stores multiple values inside one cell.
  4. A child record stored on the board's subitems board and shown beneath a parent item. Correct answer.

Explanation

Subitems are child records nested beneath a parent item and are stored on a dedicated subitems board that has its own column schema. They are not top-level boards, multi-value cells, or duplicates of the parent.

Question 4Board structure, data model and item hierarchy

A portfolio board links to a vendor board through a Connect Boards column. Portfolio editors must see each vendor's status but must not be able to change it from the portfolio board. Which column should be added to show the vendor status read-only?

  1. A Status column whose labels are manually copied from the vendor board
  2. A Formula column that references the vendor board by name
  3. A Dropdown column populated with the vendor status labels
  4. A Mirror column sourced from the Connect Boards column Correct answer.

Explanation

The Mirror column displays values from connected items and is read-only at the destination; edits must be made on the source board. Formula columns cannot query another board directly, while Status and Dropdown columns store local values that do not stay in sync.

Question 5Board structure, data model and item hierarchy

When a builder adds a new column to a board's subitems, where is that column defined in the board's data model?

  1. On the Connect Boards column of the parent board.
  2. On the subitems board associated with the parent board. Correct answer.
  3. On the parent board's main table, hidden from top-level items.
  4. On every workspace dashboard that uses the board.

Explanation

Subitems live on a separate subitems board, and their columns are defined on that subitems board. Parent board columns do not automatically apply to subitems, and dashboards and Connect Boards columns do not define storage schema.

Question 6Board structure, data model and item hierarchy

A team wants each item to remain in one group on its home board while also being referenced from several cross-functional boards without creating duplicates. Which monday.com capability supports this many-to-many relationship?

  1. Moving the item repeatedly between boards
  2. Creating a subitem for each cross-functional board
  3. Connect Boards column linking the item to items on other boards Correct answer.
  4. Adding a Group column that references another board's group

Explanation

Connect Boards creates item-to-item links across boards, so the item stays in its home group while being referenced elsewhere. Moving items relocates them, subitems are children rather than cross-board references, and a Group column cannot point to another board's group.

Question 7Board structure, data model and item hierarchy

Which statement is accurate about the item name column on a standard monday.com board?

  1. It is automatically mirrored to every connected board.
  2. It can be deleted if another column is set as the item name.
  3. It only accepts text values and cannot be used in automations.
  4. It is the first column, can be renamed, and cannot be deleted. Correct answer.

Explanation

Every board includes a fixed item name column as its first column; it can be renamed but not removed, and it can be used in automations. It is not automatically mirrored, and another column cannot replace it as the deletable name field.

Question 8Board structure, data model and item hierarchy

In the board structure, what is the item card used for?

  1. A workspace-level permission template applied to every board in the workspace.
  2. An expanded view of one item's columns, subitems, updates, and activity. Correct answer.
  3. A board-level setting that controls the color assigned to each group in the main view.
  4. A column type that stores file attachments and previews them inside an item's row.

Explanation

Clicking an item opens the item card, which consolidates its column values, subitems, updates, files, and activity in one place. It is not a board setting, a workspace permission, or a column type.

Question 9Board structure, data model and item hierarchy

A project item is linked to a client item on another board through a Connect Boards column. The project item is then moved from one group to another on the same project board. What happens to the connection?

  1. The connection is converted into a Mirror column automatically.
  2. The connection is copied to a new item and the original link is cleared.
  3. The connection remains because links are between items, not between groups. Correct answer.
  4. The connection is broken because Connect Boards links only to groups.

Explanation

Connect Boards links individual items to individual items, not groups to groups. Moving an item between groups on its own board therefore leaves the existing connection intact.

Question 10Board structure, data model and item hierarchy

Which scenario correctly calls for a Mirror column rather than a Connect Boards column?

  1. You need to allow users to select multiple items from another board inside one cell.
  2. You need to create a two-way link so a change on either board updates both items.
  3. You need to display a connected item's timeline without letting viewers edit the source timeline. Correct answer.
  4. You need to enforce that every item has at least one connected item before it can be saved.

Explanation

A Connect Boards column establishes the item-to-item link, while a Mirror column displays values from connected items and remains read-only at the destination. Two-way editing, multi-item selection, and required-link validation are handled by the Connect Boards column and its settings, not by choosing a Mirror column.

Question 11Board structure, data model and item hierarchy

A board has groups named Backlog, In Progress, and Done. An item currently sits in Backlog. How many of those groups can the same item belong to at one time on its home board?

  1. Exactly one group Correct answer.
  2. As many groups as the board has views
  3. Up to two groups, if the item is also mirrored
  4. One group plus any group that shares a subitem

Explanation

An item on a monday.com board belongs to a single group; changing its group moves it rather than adding membership. Mirrors, views, and subitems do not create additional group memberships for the item. The group is a container, not a multi-select field on the item.

Question 12Board structure, data model and item hierarchy

A project board has Table, Kanban, and Gantt views. A team member changes an item's status from the Kanban view. What is reflected in the Table view for that same item?

  1. A separate Table-view status value, because each view stores its own item data
  2. The Table view keeps the old status until the board is refreshed manually
  3. No status change, because status columns cannot be edited from a Kanban view
  4. The updated status, because all views display the same board data Correct answer.

Explanation

Views are alternate presentations of the same board items and column values, not separate data stores. Editing a column in any view updates the shared item record. The Table view therefore shows the same updated status without a separate copy.

Question 13Board structure, data model and item hierarchy

A parent board contains 80 items, and each item has at least one subitem. In the board's data model, how many subitems boards are associated with that parent board?

  1. One subitems board per item that has subitems
  2. One subitems board per group on the parent board
  3. Eighty subitems boards, because each item has at least one subitem
  4. One subitems board for the entire parent board Correct answer.

Explanation

monday.com stores subitems in a separate subitems board linked to the parent board, and that subitems board holds the subitems for all items on the parent board. The parent board does not create a new subitems board for each item or group. This shared structure is why subitem columns apply across the board's subitems.

Question 14Board structure, data model and item hierarchy

An item with two subitems and several column values is moved from the Backlog group to the Sprint 1 group on the same board. What happens to the item's column values and subitems?

  1. The subitems are detached from the item and must be recreated after the move
  2. They move with the item; only its group assignment changes Correct answer.
  3. Only the item name moves, while column values and subitems stay with the old group
  4. The column values are cleared, and the subitems remain attached to the Backlog group

Explanation

Moving an item between groups on the same board changes its group assignment while keeping the item record intact. Column values and subitems are attributes of that item and travel with it. This is not a copy, so no data is duplicated or cleared.

Question 15Board structure, data model and item hierarchy

A project item has three subitems with status values. A builder uses the item's Duplicate action. What is the expected result for the subitems?

  1. The duplicate includes copies of the subitems and their values Correct answer.
  2. The duplicate includes only the parent item; subitems are never copied
  3. The duplicate creates a new subitems board for the copied subitems
  4. The duplicate links to the original subitems instead of copying them

Explanation

Duplicating an item creates a new item copy in the same group and duplicates the item's subitems along with their column values. The copy is independent of the original, so editing the duplicated subitems does not change the originals. It does not create a new subitems board.

Question 16Board structure, data model and item hierarchy

A Connect Boards column on a project board links to a client item on a separate Clients board. Which statement describes what the project board stores for that connection?

  1. A mirror column value that is calculated only when the board is exported
  2. A reference to the linked client item, displayed through the connection Correct answer.
  3. A full copy of the client item's column values
  4. A new client item created automatically on the Clients board

Explanation

Connect Boards columns create links between items and display the connected item, but the target item's data remains on its home board. The project board stores the connection reference rather than duplicating the client's fields. Mirror columns, not the connection itself, are used to display selected fields from the linked item.

Question 17Board structure, data model and item hierarchy

A builder wants to organize the subitems under a single parent item into separate collapsible sections called Design, Build, and QA. Which limitation of the subitems table affects this plan?

  1. The subitems table does not provide group containers; subitems under an item form a flat list Correct answer.
  2. Subitems must each belong to a parent group on the main board, so they inherit the main board groups
  3. Subitems cannot store files, so section names cannot be attached
  4. Subitems cannot use status columns, so phase labels cannot be represented

Explanation

On a monday.com board, groups organize items on the main board, but the subitems table under an item is a flat list rather than a grouped container. You can use columns to label phases, but you cannot create collapsible group sections inside the subitems table. This is a structural limitation, not a restriction on status columns or files.

Question 18Board structure, data model and item hierarchy

A parent board has a Status column called Project Status, and its subitems have a separate Status column called Task Status. The parent item's Project Status has not been set manually, and one subitem's Task Status is set to Done. What does the parent item's Project Status show by default?

  1. Blank, because parent and subitem columns are separate and do not sync automatically Correct answer.
  2. The parent status is locked until a mirror column is added to the subitems table
  3. Done only if the parent item has at least two subitems
  4. Done, because subitem status values automatically roll up to the parent

Explanation

Parent item columns and subitem columns are defined separately, and a subitem's value does not automatically write to the parent item's column. Rollup or summary behavior must be configured rather than assumed by default. Therefore the parent Project Status remains unchanged unless a rollup is set up.

Question 19Board structure, data model and item hierarchy

A parent board has three items, each with subitems. A builder adds a new Priority column to the subitems table from one item's subitems. What is the data-model consequence for the other items' subitems?

  1. It is shared by all subitems on that parent board through the single subitems board Correct answer.
  2. It applies only to the subitems under the item where the column was created, not to the others
  3. It is duplicated independently for each parent item's subitems, with separate column settings
  4. It is placed on the main board's items instead, because subitem columns are defined at board level

Explanation

All subitems on a parent board are stored in one shared subitems board, so subitem columns are defined for that whole subitems board. Adding a subitem column therefore makes it available across the subitems of every parent item on that board, not just the item where it was added. This shared schema is why subitem column changes affect all subitems on the board.

Question 20Board structure, data model and item hierarchy

A board has a Status column with labels Not Started, In Progress, and Done. Which statement correctly separates the column definition from an item's value?

  1. The column type and labels are board-level; the selected label is per item Correct answer.
  2. The selected label is stored in the board view, while the item stores only the column title
  3. Each item defines its own status labels, and the board-level column only stores the column title
  4. The label set is stored on each item, while the column type is set per group

Explanation

A monday.com column defines its type and configuration, such as the status label set, at the board level. Each item then stores its own value, such as which status label is selected. Changing an item's selected label does not redefine the column's label set.

Question 21Board structure, data model and item hierarchy

Which statement accurately describes the Item ID on a standard monday.com board?

  1. It is an optional column that appears only on boards with multiple groups.
  2. It is a user-editable text label that can be renamed from the item card at any time.
  3. It is a unique auto-generated number used by automations and the API. Correct answer.
  4. It is a sequential number that resets whenever the item is moved to another group.

Explanation

Every item on a monday.com board receives a unique, system-generated Item ID at creation. That ID cannot be edited by users, and automations and API calls use it to reference the item reliably. It is not a column you add or an optional field.

Question 22Board structure, data model and item hierarchy

What is the maximum nesting depth for subitems under a parent item in a monday.com Work Management board?

  1. Subitems sit one level below the parent and cannot contain further subitems. Correct answer.
  2. Subitems can be nested only when the parent board includes a Connect Boards column.
  3. Subitems can contain their own subitems to any depth that the board supports.
  4. Subitems can be nested two levels deep, but the platform does not allow deeper nesting.

Explanation

In monday.com Work Management, the item hierarchy is board, group, item, and subitem. Subitems are the deepest supported level; you cannot add subitems beneath a subitem. This one-level limitation keeps the hierarchy predictable for automations and reporting.

Question 23Board structure, data model and item hierarchy

When a user archives an item on a monday.com board, what is the result for that item?

  1. The item is hidden but can be restored later from the archived items area. Correct answer.
  2. The item is moved to a different board and keeps its original group assignment.
  3. The item is permanently deleted and cannot be recovered by any board user.
  4. The item is converted into a subitem under the next item in the same group.

Explanation

Archiving removes an item from the active board view while preserving its data for later restoration. Archived items are not deleted and can be found in the board's archived items area. Permanent deletion is a separate action that sends an item to the trash.

Question 24Board structure, data model and item hierarchy

A builder adds a Mirror column to a project board to display the status of a connected client item. A team member tries to change the status directly in the Mirror column. What is the expected result?

  1. The change is saved only on the project board and does not affect the client board.
  2. The change is allowed only if the team member has edit permissions on the client board.
  3. The change is queued and applied to the client item after the next board refresh.
  4. The change is not allowed because the Mirror column is read-only and reflects the source item. Correct answer.

Explanation

A Mirror column displays data pulled from a connected item and is read-only by design. To change the underlying value, a user must edit the source item on its own board. Editing the Mirror cell directly is not possible, regardless of permissions.

Question 25Board structure, data model and item hierarchy

A builder hides a column from all views on a board. What happens to the data that was stored in that column?

  1. The data becomes read-only but remains visible on the item card.
  2. The data is moved to a backup board until the column is shown again.
  3. The data is deleted from all items after the column is hidden.
  4. The data remains stored and is still available to automations and the API. Correct answer.

Explanation

Hiding a column only changes its visibility in board views; it does not delete or move the underlying data. Items retain their values, and automations, formulas, and API calls can still reference the hidden column. The data becomes visible again if the column is shown.

Question 26Board structure, data model and item hierarchy

A project manager needs to show that one item on a board must finish before another item on the same board can start. Which column type is designed for this relationship?

  1. Formula column
  2. Connect Boards column
  3. Dependency column Correct answer.
  4. Mirror column

Explanation

The Dependency column links items on the same board to represent scheduling relationships such as finish-to-start. Connect Boards columns link items across different boards, while Mirror and Formula columns derive values rather than define dependencies. For same-board predecessor and successor links, the Dependency column is the intended structure.

Question 27Board structure, data model and item hierarchy

Which statement describes how a Formula column behaves on a monday.com board?

  1. It stores a static value that users must recalculate manually after each change.
  2. It is a read-only mirror of a column on a connected board.
  3. It can only reference the item name column and cannot use numeric columns at all.
  4. It calculates from other columns and updates automatically when they change. Correct answer.

Explanation

A Formula column uses other columns on the same item to compute a result, such as a due date offset or a budget variance. It recalculates automatically when referenced values change, so users do not maintain the result manually. It is not a Mirror column, which instead displays data from connected items.

Question 28Board structure, data model and item hierarchy

A parent item with three subitems is deleted from a board. What happens to those subitems in the monday.com data model?

  1. The subitems are converted into separate boards for archival purposes.
  2. The subitems remain on the board as standalone items in the same group.
  3. The subitems are automatically reassigned to the next parent item in the group.
  4. They are deleted with the parent and cannot exist without a parent. Correct answer.

Explanation

Subitems are structurally dependent on a parent item and cannot exist independently on the board. Deleting the parent also removes its subitems, typically sending them to the trash along with the parent. To preserve subitem data, a user must move or duplicate the subitems before deleting the parent.

Question 29Board structure, data model and item hierarchy

In the monday.com Work Management data model, where are subitems stored relative to their parent board?

  1. In the parent board's group metadata rather than in a board structure.
  2. On a workspace-level board that is shared by all boards in the workspace.
  3. On a separate hidden board that is linked to the parent board. Correct answer.
  4. Inside the parent item's row as a JSON field in the same table.

Explanation

Subitems in monday.com are implemented as items on a dedicated hidden board associated with the parent board. That hidden board stores subitem columns and values, and the parent board's Subitems column displays the linked subitems. This design lets subitems have their own columns, updates, and automations while remaining tied to the parent item.

Question 30Board structure, data model and item hierarchy

A board has a group named 'Archive' that users drag finished items into. How does this differ from using the item's Archive action?

  1. It permanently deletes the item, while the Archive action hides it from the board.
  2. It removes the item from all views, while the Archive action keeps it visible on the board.
  3. It only changes the item's group, while the Archive action hides the item. Correct answer.
  4. It moves the item to another board, while the Archive action keeps it on the same board.

Explanation

A group named Archive is still an active group on the board, so dragging an item there changes only its group assignment and the item remains visible in that group. The Archive action instead hides the item from the board while preserving it for later restoration. The two actions serve different purposes: grouping for organization versus archiving for removal from active views.

Question 31Board structure, data model and item hierarchy

Which sequence correctly orders monday.com Work Management containers from broadest to most granular?

  1. Workspace → Folder → Board → Group → Item → Subitem Correct answer.
  2. Workspace → Board → Subitem → Group → Item
  3. Folder → Workspace → Board → Item → Group
  4. Board → Workspace → Group → Subitem → Item

Explanation

A workspace is the top-level container for folders and boards. A board contains groups, groups contain items, and items can contain subitems, so the remaining sequences place containers in the wrong order.

Question 32Board structure, data model and item hierarchy

A board has a group named Q1 Leads containing 12 items. A board admin deletes that group. What happens to the 12 items?

  1. They are moved to the first remaining group.
  2. They are deleted together with the group. Correct answer.
  3. They become subitems of the first item in the next group.
  4. They are archived but remain searchable.

Explanation

Deleting a group removes the group and the items inside it from the board. Archiving is a separate action that preserves items in an archived state, so it is not the result of deleting the group.

Question 33Board structure, data model and item hierarchy

Which field must every item on a monday.com board have, regardless of the board's columns?

  1. Date
  2. Item name Correct answer.
  3. Person
  4. Status

Explanation

Every item has a name, which identifies it in the board and in views. Status, Person, and Date are optional columns configured by the board builder, so they cannot be required for every item.

Question 34Board structure, data model and item hierarchy

A builder needs a column on a project board where a single item can carry several predefined labels, such as Frontend, Backend, and QA, at the same time. Which column type fits?

  1. Dropdown Correct answer.
  2. Status
  3. Date
  4. Numbers

Explanation

A Dropdown column allows an item to carry multiple predefined labels at once. A Status column is designed to hold one selected label per item, and Numbers and Date store different kinds of values.

Question 35Board structure, data model and item hierarchy

An item with values in a Status column and a Text column is moved from Board A to Board B. Board B has a Status column with the same name but no Text column. What is the expected treatment of the item's column values?

  1. The Status value can be mapped to Board B's Status column, while the Text value has no matching column and is not retained. Correct answer.
  2. The move is blocked until Board B has an identical Text column.
  3. Both values are retained because moving an item copies all columns into a hidden section.
  4. Both values are automatically stored in Board B's Item name field.

Explanation

Moving an item to another board maps values into columns on the target board. A matching Status column can receive the status value, but a column with no target equivalent has no place to store its data.

Question 36Board structure, data model and item hierarchy

A builder adds a new Text column called Notes to the parent board after subitems already exist. Which statement describes the effect on the subitems table?

  1. The Notes column is automatically added to the subitems table with copied values.
  2. The subitems table keeps its own column set, so the parent's Notes column does not automatically appear there. Correct answer.
  3. The Notes column is added to subitems only after each subitem is edited.
  4. The Notes column replaces the subitems' first Text column.

Explanation

Subitems have a separate column structure from their parent board. Adding a column to the parent board does not automatically add that column to the subitems table, so subitem columns must be managed separately.

Question 37Board structure, data model and item hierarchy

A board has Table, Kanban, and Gantt views. A user with edit permissions deletes the Kanban view. What is the effect on the board's items?

  1. The status values changed in the Kanban view are reverted.
  2. The items remain unchanged; only that view definition is removed. Correct answer.
  3. The board's groups are merged into one group.
  4. Items that appeared only in the Kanban view are deleted.

Explanation

Views are saved presentations of the same board data, so deleting one removes only that display configuration. The underlying items, column values, and group structure remain in place.

Question 38Board structure, data model and item hierarchy

In the monday.com item hierarchy, a subitem is directly attached to which entity?

  1. A workspace
  2. Another subitem
  3. A parent item Correct answer.
  4. A group

Explanation

A subitem belongs to a parent item on the board, and subitems cannot themselves contain further subitems. Groups and workspaces are higher-level containers, not the direct parent of a subitem.

Question 39Board structure, data model and item hierarchy

A builder wants Board A to show a client's current status from Board B and keep it synchronized when Board B's status changes. Which combination of column types on Board A is required?

  1. Mirror and Formula
  2. Status and Formula
  3. Dropdown and Connect Boards
  4. Connect Boards and Mirror Correct answer.

Explanation

A Connect Boards column creates the link to the specific item on Board B. A Mirror column then displays a column value from that linked item and updates when the source value changes.

Question 40Board structure, data model and item hierarchy

A builder duplicates an entire board that contains items with subitems. Which statement best describes the duplicate's data model?

  1. The duplicate shares the same item and subitem records as the original.
  2. The duplicate creates a new view of the original board rather than a separate board.
  3. The duplicate copies only parent items; subitems remain linked to the original parent items.
  4. The duplicate contains new copies of the items and their subitems, independent of the original records. Correct answer.

Explanation

Duplicating a board creates a separate board with its own copied structure and records. The copied items and subitems are independent, so later edits in the duplicate do not change the original board.

Question 41Automations, integrations and workflow logic

A monday.com automation recipe is described as 'when this happens, do that.' Which element of the recipe specifies the event that must occur for the recipe to run?

  1. The condition
  2. The integration
  3. The trigger Correct answer.
  4. The action

Explanation

A recipe is structured as a trigger followed by one or more actions. The trigger is the event that starts the recipe, such as a status change or a new item being created. Conditions are optional filters that must also be true before the actions run.

Question 42Automations, integrations and workflow logic

Which statement describes how a monday.com integration differs from an automation?

  1. An integration runs on a fixed schedule, whereas an automation runs only when a date column is reached.
  2. An integration is available only on Enterprise, whereas an automation is available on every plan including Free.
  3. An integration is built from triggers and actions, whereas an automation is installed from the integrations marketplace.
  4. An integration links the board to an external application, whereas an automation performs monday.com actions from a recipe. Correct answer.

Explanation

Integrations connect a monday.com board to a third-party application and can sync data, for example creating items from form submissions or posting updates to a chat channel. Automations stay inside monday.com and execute a trigger-action recipe on the board's own items. Both are configured from the board, but only the integration reaches an external system.

Question 43Automations, integrations and workflow logic

A project manager needs a recipe that creates a recurring status-update item every Monday at 08:00, whether or not any existing item has changed. Which trigger should the recipe use?

  1. Every time period Correct answer.
  2. When date arrives
  3. When item is created
  4. When a column changes

Explanation

The 'Every time period' trigger runs a recipe on a recurring schedule, such as every Monday at 08:00. 'When date arrives' also involves time, but it is evaluated per item against a date column value, so it depends on item data rather than a fixed recurring timetable. Item-created and column-change triggers are event driven.

Question 44Automations, integrations and workflow logic

A board has a status column 'Stage' and a checkbox column 'Budget approved'. The team wants an item moved to the 'Kickoff' group only when Stage becomes 'Approved' and Budget approved is checked. What is the most appropriate implementation?

  1. Set the item's default group to Kickoff so that newly created items land there, and rely on the Status column for reporting.
  2. Add a mirror column that reflects the checkbox value from a connected board and use the mirror as the automation trigger.
  3. Use a custom automation with the status trigger, a condition on the checkbox, and a move-item action. Correct answer.
  4. Create two separate automations, one that reacts to Stage and one that reacts to the checkbox, and let whichever fires first move the item.

Explanation

A custom automation can combine a trigger, one or more conditions, and one or more actions in a single recipe. The condition ensures the move happens only when the status change and the checkbox state are both true. Splitting the logic across two independent automations would move the item as soon as either column alone changed.

Question 45Automations, integrations and workflow logic

Board A is connected to Board B with a Connect Boards column. Users on Board A need to see, but not edit, the value of a timeline column that lives on the connected item in Board B. Which column type should be added to Board A?

  1. Formula column
  2. Mirror column Correct answer.
  3. Timeline column
  4. Connect Boards column

Explanation

The Mirror column displays values from items connected through a Connect Boards column and is read-only on the board where it appears. The Connect Boards column itself only creates the link and shows the connected item name. A local Timeline column would hold separate values, and a Formula column cannot read another board's columns directly.

Question 46Automations, integrations and workflow logic

A team adds the automation 'When date arrives, notify the item's owner' to a board that already contains 40 items with past due dates. After enabling it, no notifications are sent for those 40 items. What explains this behavior?

  1. Automations act on events that occur after they are enabled; they do not run retroactively on items whose date already passed. Correct answer.
  2. The notify action requires the item owner to be an account admin.
  3. The board must be refreshed manually before scheduled automations can fire.
  4. Date-based automations require a Timeline column rather than a Date column.

Explanation

Automations listen for events going forward from the moment they are enabled; they do not scan historical items. Items whose date has already passed will not fire the 'When date arrives' trigger because that event occurred before the recipe existed. To handle existing overdue items you would update their dates or run a one-time manual action.

Question 47Automations, integrations and workflow logic

Agency staff want monday.com to send a message to a client's external email address when a deliverable status changes to 'Ready for review'. The client does not use monday.com. Which action should the automation use?

  1. Assign the item to the client
  2. Create an update
  3. Send an email Correct answer.
  4. Notify someone

Explanation

The 'Send an email' action delivers a message to any email address, including people outside the account. 'Notify someone' only reaches monday.com users through in-app notifications, and 'Create an update' posts inside the item's conversation. Assigning a person requires them to be a monday.com user with access to the board.

Question 48Automations, integrations and workflow logic

A board's key automation stopped running after the employee who originally built it was deactivated and removed from the board's subscribers. Other team members still have edit access and the automation is still toggled on. What is the most likely cause?

  1. Automations are disabled automatically whenever a board exceeds its recipe count.
  2. The automation's trigger column was deleted when the employee was deactivated.
  3. Only account admins can own automations, so the recipe was never valid.
  4. Automations execute with the permissions of the user who created them, so removing that user's board access breaks the recipe. Correct answer.

Explanation

monday.com executes automations under the permissions of the user who created them. If that user is deactivated or loses access to the board, the recipe can no longer perform its actions even though it is still listed and switched on. Recreating the recipe under an active user with board access restores it.

Question 49Automations, integrations and workflow logic

Which pair of automations on the same board is most likely to produce an endless loop?

  1. 'When Status changes to Done, set Priority to High' and 'When Priority changes to High, set Status to Done'. Correct answer.
  2. 'Every Monday at 09:00, create an item' and 'When item is created, set Status to New'.
  3. 'When Date arrives, move item to the Archive group' and 'When item is moved to a group, notify the owner'.
  4. 'When Status changes to Done, notify the item's owner' and 'When Status changes to Done, create a subitem'.

Explanation

A loop occurs when an automation's action triggers another automation whose action re-triggers the first one. In the status and priority pair, each change feeds the other indefinitely. The other pairs end after a single pass or are started by independent events that are not re-created by their own actions.

Question 50Automations, integrations and workflow logic

A team wants an automation that fires when a subitem's own status column changes to 'Complete'. How should this be configured?

  1. Apply a regular item automation to the parent board and reference the subitem's status column inside the recipe condition.
  2. Use the subitem automations area, which offers subitem-specific triggers such as a subitem status change. Correct answer.
  3. Convert each subitem into a regular item, since subitems themselves cannot be used as automation triggers.
  4. Add a mirror column to the parent item that reflects subitem status and let the mirror column trigger a standard automation.

Explanation

Subitems are managed through their own set of automation recipes, available in the subitem automations area of the board. Those recipes include triggers such as a subitem's status changing, and they act on the subitem rather than on its parent. Standard item recipes cannot be triggered directly by a subitem event.