nerdexam
ServiceNow

CSA · Question #197

Tables may be set up with Many to Many relationships. What is a classic example of a scenario where the tables would have many to many relationships?

The correct answer is B. A Task can trigger many Workflows; and a Workflow can trigger many Tasks.. A classic example of a many-to-many relationship is where a single task can initiate multiple workflows, and conversely, a single workflow can be triggered by multiple distinct tasks.

Submitted by haruto_sh· Apr 18, 2026Self-Service and Process Automation

Question

Tables may be set up with Many to Many relationships. What is a classic example of a scenario where the tables would have many to many relationships?

Options

  • AVendors can sell multiple products; and products can be sold by multiple vendors.
  • BA Task can trigger many Workflows; and a Workflow can trigger many Tasks.
  • CRequests can contain many Items; and Items can be any item from the catalog.
  • DA Configuration Item can belong to multiple Classes, and Classes can contain multiple

How the community answered

(38 responses)
  • A
    3% (1)
  • B
    89% (34)
  • C
    5% (2)
  • D
    3% (1)

Why each option

A classic example of a many-to-many relationship is where a single task can initiate multiple workflows, and conversely, a single workflow can be triggered by multiple distinct tasks.

AVendors can sell multiple products; and products can be sold by multiple vendors.

While technically a many-to-many relationship in a general database sense, this option describes a business scenario rather than an internal platform relationship often highlighted as 'many-to-many' within ServiceNow's core architecture discussions like Task to Workflow or User to Role.

BA Task can trigger many Workflows; and a Workflow can trigger many Tasks.Correct

In a many-to-many relationship, records from one table can be associated with multiple records from another table, and vice-versa. The scenario where a Task can trigger many Workflows, and a Workflow can be triggered by many Tasks perfectly illustrates this, typically implemented using an intermediary relationship table to link the two primary tables.

CRequests can contain many Items; and Items can be any item from the catalog.

This describes a one-to-many relationship (one Request can have many Items, but each Item belongs to only one Request), not a many-to-many.

DA Configuration Item can belong to multiple Classes, and Classes can contain multiple

This describes a one-to-many relationship (a Class can have many CIs, but each CI belongs to one Class via inheritance), not a many-to-many.

Concept tested: Understanding Many-to-Many relationships

Source: https://docs.servicenow.com/bundle/utah-platform-user-interface/page/administer/m2m/concept/m2m-relationships.html

Topics

#Many-to-Many relationships#Database relationships#Data model#Workflow

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full CSA Practice