Which table links Policy Profiles to Policy Types?

Which table links Policy Profiles to Policy Types?

• A. [sn_compliance_m2m_policy_profile]
• B. [sn_compliance_m2m_policy_profile_type]
• C. [sn_compliance_m2m_statement_profile_type]
• D. [sn_risk_m2m_risk_profile]

Answer: (B)

Understanding how Policy Profiles relate to Policy Types helps clarify why this is the right link. In ServiceNow, a many-to-many relationship between two tables is implemented with a bridging (join) table. For Policy Profiles and Policy Types, the bridging table is sn_compliance_m2m_policy_profile_type. It stores pairs of references: one to a Policy Profile and one to a Policy Type, allowing a profile to include multiple types and a type to appear in multiple profiles. The name itself signals the connection between policy_profile and type, reinforcing its role as the link. Other tables listed either represent the main policy profile entity, a different join for another pairing (such as Statement Profile Type), or relate to risk profiles, not policy types.

Understanding how Policy Profiles relate to Policy Types helps clarify why this is the right link. In ServiceNow, a many-to-many relationship between two tables is implemented with a bridging (join) table. For Policy Profiles and Policy Types, the bridging table is sn_compliance_m2m_policy_profile_type. It stores pairs of references: one to a Policy Profile and one to a Policy Type, allowing a profile to include multiple types and a type to appear in multiple profiles. The name itself signals the connection between policy_profile and type, reinforcing its role as the link.

Other tables listed either represent the main policy profile entity, a different join for another pairing (such as Statement Profile Type), or relate to risk profiles, not policy types.