Which table stores the link from Entity Types to Control Objectives?

Which table stores the link from Entity Types to Control Objectives?

• 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: (C)

In IRM, relationships between different objects are stored in dedicated many-to-many join tables. To connect an Entity Type to a Control Objective, you use the join table that records associations between the relevant compliance pieces—specifically the statement/profile type side and the control objective side. The table sn_compliance_m2m_statement_profile_type is designed to capture those links, acting as the bridge that ties each entity type to its associated control objectives through the statement profile type framework. The other tables listed are intended for different kinds of mappings (for example, between policy profiles and profiles or between risk-related profiles), so they don’t represent the link between Entity Types and Control Objectives.

In IRM, relationships between different objects are stored in dedicated many-to-many join tables. To connect an Entity Type to a Control Objective, you use the join table that records associations between the relevant compliance pieces—specifically the statement/profile type side and the control objective side. The table sn_compliance_m2m_statement_profile_type is designed to capture those links, acting as the bridge that ties each entity type to its associated control objectives through the statement profile type framework.

The other tables listed are intended for different kinds of mappings (for example, between policy profiles and profiles or between risk-related profiles), so they don’t represent the link between Entity Types and Control Objectives.