Which table stores the many-to-many relationship between GRC profiles and their types?

Which table stores the many-to-many relationship between GRC profiles and their types?

• A. [sn_compliance_m2m_profile_profile_type]
• B. [sn_risk_m2m_risk_profile]
• C. [sn_compliance_m2m_policy_profile]
• D. [sn_grc_m2m_profile_profile_type]

Answer: (D)

In ServiceNow, a many-to-many link is stored in a bridge table that references both sides of the relationship. For GRC, a profile can have multiple types and a type can belong to multiple profiles, so the connecting table holds pairs of references to a GRC profile and a profile type. The naming convention for GRC bridge tables is sn_grc_m2m_<left>_<right>, where the left side is the profile and the right side is the profile type. That makes sn_grc_m2m_profile_profile_type the table that stores the links between GRC profiles and their types. Other options point to different domains (like compliance or risk) and wouldn’t represent this GRC-specific relationship.

In ServiceNow, a many-to-many link is stored in a bridge table that references both sides of the relationship. For GRC, a profile can have multiple types and a type can belong to multiple profiles, so the connecting table holds pairs of references to a GRC profile and a profile type. The naming convention for GRC bridge tables is sn_grc_m2m__, where the left side is the profile and the right side is the profile type. That makes sn_grc_m2m_profile_profile_type the table that stores the links between GRC profiles and their types. Other options point to different domains (like compliance or risk) and wouldn’t represent this GRC-specific relationship.