InServiceNow, aMany-to-Many (M2M) relationshipexists whenrecords in one tablecan be associated withmultiple records in another table, and vice versa.
A classic example of anM2M relationshipis:
#Vendors can sell multiple products
#Products can be sold by multiple vendors
Vendors oftensell multiple productsacross different categories.
A single product can beavailable from multiple vendors.
This requires anintermediary (join) tableto track the many-to-many relationship.
A: Requests & Items
Incorrectbecause eachRequest (REQ#)can havemultiple requested items (RITM#), but anitem does not belong to multiple requests. This is aone-to-many (1:M) relationship.
C: Tasks & Workflows
Incorrectbecause workflows are associatedat an individual task level, and while multiple workflows may be involved, they do not create a trueM2M relationship.
D: Configuration Items & Classes
Incorrectbecause a Configuration Item (CI)belongs to only one class, making this aone-to-many relationship, not M2M.
Reference:ServiceNow CSA Documentation - Many-to-Many Relationships
ServiceNow Product Documentation - Relationship Types & Example Use Cases(https://docs.servicenow.com)
Final answer: B. Vendors can sell multiple products; and products can be sold by multiple vendors.