Question 1
Choose 1
In Data 360, which mechanism ensures different business units can use the same Data 360 home org while
keeping their data and metadata logically separated, to meet governance or compliance requirements?
Correct answer:
C. Use separate data spaces for each business unit
Explanation:
This question tests understanding of logical data isolation in Salesforce Data 360. The requirement is governance-level separation between business units while still operating under the same home org. The solution must isolate both data and metadata, not just access or UI-level visibility.
🟢 C. Use separate data spaces for each business unit
Data Spaces in Data 360 are designed specifically for logical separation of data, metadata, and configurations within a single org. Each business unit can operate in its own isolated environment while sharing the same underlying Data 360 instance. This ensures compliance, governance boundaries, and independent data management without requiring separate orgs.
🔴 A. Use separate companion connections within the same data space
Companion connections are used for connecting external systems or data sources, not for isolating business units. They do not provide logical separation of data or metadata within Data 360.
🔴 B. Use different permission sets within the same data space
Permission sets control user access and visibility but do not separate data or metadata. All business units would still share the same underlying data space, which fails governance isolation requirements.
🔴 D. Use separate objects per business unit with record-type filtering
Using separate objects or record types only provides logical segmentation at the data model level, not true isolation. It introduces complexity and does not enforce strict separation of metadata, configurations, or governance boundaries.
🔧 Reference:
⇒ Salesforce Data Cloud Data Spaces Overview
Explains how Data Spaces provide logical separation of data, metadata, and configurations for multi-business-unit scenarios.
This question tests understanding of logical data isolation in Salesforce Data 360. The requirement is governance-level separation between business units while still operating under the same home org. The solution must isolate both data and metadata, not just access or UI-level visibility.
🟢 C. Use separate data spaces for each business unit
Data Spaces in Data 360 are designed specifically for logical separation of data, metadata, and configurations within a single org. Each business unit can operate in its own isolated environment while sharing the same underlying Data 360 instance. This ensures compliance, governance boundaries, and independent data management without requiring separate orgs.
🔴 A. Use separate companion connections within the same data space
Companion connections are used for connecting external systems or data sources, not for isolating business units. They do not provide logical separation of data or metadata within Data 360.
🔴 B. Use different permission sets within the same data space
Permission sets control user access and visibility but do not separate data or metadata. All business units would still share the same underlying data space, which fails governance isolation requirements.
🔴 D. Use separate objects per business unit with record-type filtering
Using separate objects or record types only provides logical segmentation at the data model level, not true isolation. It introduces complexity and does not enforce strict separation of metadata, configurations, or governance boundaries.
🔧 Reference:
⇒ Salesforce Data Cloud Data Spaces Overview
Explains how Data Spaces provide logical separation of data, metadata, and configurations for multi-business-unit scenarios.