Setup And Administration practice questions

Data Cloud Streaming API License

Why it fails: This license is specifically for streaming API integrations, not general user administration.

Customer Data Platform Integration License

Why it fails: This is not the correct name for the base license.

Salesforce CRM Integration License

Why it fails: This license is for integrating external CRM data sources, not the core Data Cloud user license.

Data Cloud Marketing Specialist

Why it fails: This permission set is tailored for marketers building segments and activations.

Data Cloud Analytics User

Why it fails: This is not a standard out-of-the-box Data Cloud permission set name.

Data Cloud Integration User

Why it fails: This permission set is intended for integration-specific tasks.

Calculated insights must be rebuilt before a DMO field is available for segmentation.

Why it fails: Calculated insights are not required for standard DMO field availability in segmentation.

Data Cloud requires a manual restart of the segment job engine to recognize schema changes.

Why it fails: Segment engines update dynamically and do not require manual restarts for schema changes.

The custom field must be explicitly added to the Identity Resolution ruleset configuration.

Why it fails: Identity resolution rulesets only use specific match keys, not every custom field added to a DMO.

Setup > Platform Tools > Data Cloud Administration

Why it fails: This is not the standard path in Salesforce Setup.

Setup > Apps > Connected Apps > Data Cloud

Why it fails: Connected Apps is for external API integrations, not initial org provisioning.

Setup > Feature Settings > Data Cloud > Data Cloud Setup

Why it fails: This is an incorrect path structure.

Salesforce Optimizer

Why it fails: Salesforce Optimizer analyses org metadata and configuration to recommend best practises; it holds no Data Cloud stream telemetry such as row counts or refresh status. It is tempting as a health-check tool, and would be correct for auditing standard Salesforce org setup, not Data Cloud ingestion.

Data Cloud Setup > Monitoring > System Overview

Why it fails: Data Cloud Setup hosts connectors, data streams and data spaces, but no Monitoring > System Overview page reporting stream health or row counts. The nested naming is tempting, yet it would be correct only if such a monitoring node existed in the Data Cloud Setup tree.

Setup > Environments > Data Cloud Health Check

Why it fails: No such Setup path exists; Data Cloud health monitoring is not surfaced under Environments. The naming is tempting because it mimics genuine Setup menu structures, but it would only be correct if Salesforce actually exposed stream diagnostics there, which it does not.

Data Cloud Integration User

Why it fails: Data Cloud Integration User covers configuring connectors and ingesting data from source systems, not segment building. It is tempting because segments rely on ingested data, and it would be the right permission set for setting up and maintaining data connections rather than for creating and running segments.

Data Cloud Stream Viewer

Why it fails: Data Cloud Stream Viewer grants read-only visibility into ingestion streams, so it cannot create or run segments. It is tempting because segments depend on streamed data, and it would be correct for a user who only needs to monitor stream health and ingestion status without building anything.

Data Cloud Data Engineer

Why it fails: Data Cloud Data Engineer covers ingestion, transformation and data model work, not segment creation and activation. It is tempting because engineers handle the underlying data that segments consume, and it would be the right permission set for building data streams, DMOs and transformations rather than for creating and running segments.

Data Cloud Setup > Setup Audit Trail

Why it fails: The Audit Trail tracks administrative changes, not storage or credit usage.

Salesforce Optimizer

Why it fails: Optimizer checks org health and best practices, not granular Data Cloud capacity consumption.

Setup > Company Information > Feature Licenses

Why it fails: Company Information shows license counts, but Data Cloud specific consumption metrics (like data storage and compute) are found in Data Cloud Setup.

Assign the users to a custom profile with Read-Only access to Calculated Insights.

Why it fails: Data Cloud does not use custom profiles for object-level security in the same manner as core CRM.

Set the sharing model for Calculated Insight objects to Private in Sharing Settings.

Why it fails: Sharing Settings in core CRM do not apply to Data Cloud calculated insights.

Place the calculated insights into a locked Data Space that blocks all users except administrators.

Why it fails: Data Spaces partition data and insights, but user access within a space is still governed by permission sets.

Salesforce Billing and Invoice Manager

Why it fails: Billing manager handles core subscription invoicing, not real-time Data Cloud credit consumption.

Data Manager > System Monitoring > Credits

Why it fails: Credit consumption is tracked under Data Cloud Setup > Usage Dashboard.

Setup > Company Information > Credit Ledger

Why it fails: This is not a standard Salesforce setup path.

Assign the Global Segment Administrator permission set to all users.

Why it fails: Global Segment Administrator grants organisation-wide segment access, directly contradicting the requirement that each region sees only its own Data Space segments. It is tempting because it simplifies administration, and would be correct where one team manages all segments, but Data Space scoping demands per-space permission sets.

Apply a global filter in the Segment canvas referencing the user's region profile.

Why it fails: A global filter narrows segment membership by criteria such as region, but it does not restrict which Data Space a user can create or view segments in. It is tempting because filters shape segment populations, and would be correct for targeting a regional audience, yet Data Space access requires permission-set assignment.

Configure sharing rules on the Segment DMO in Object Manager.

Why it fails: Sharing rules govern record visibility on DMOs, not which Data Space a segment belongs to or who may create segments there. It is tempting because sharing rules control access elsewhere in the platform, and would be correct for row-level DMO access, but segment isolation is enforced through Data Space membership and permissions.

The Calculated Insight must be exported to Amazon S3 before it can be used in segments.

Why it fails: Calculated Insights become segment-eligible only once their Data Space is activated for segmentation; exporting to Amazon S3 addresses external data sharing, not segment availability. The S3 export path is genuinely used when feeding insights into external analytics or downstream platforms, which is why it looks relevant here.

The user lacks the 'View Setup and Configuration' permission in core CRM.

Why it fails: Segment availability of a Calculated Insight depends on Data Space configuration and the user's Data 360 segment permissions, not core CRM object permissions. 'View Setup and Configuration' governs access to CRM setup menus, so it would matter for administering CRM metadata, not for consuming Data 360 insights.

Calculated insights cannot be used in segments; only Data Model Objects can be used.

Why it fails: Calculated Insights are usable in segments when their dimensions and measures are properly configured, so this blanket prohibition is false. The likely oversight is that the insight lacks a segment-compatible dimension or is not activated for segmentation. This option would be correct only if the platform genuinely restricted segments to Data Model Objects.

Customer Data Platform Integration License

Why it fails: This is not the correct name for the base license.

Salesforce Marketing Cloud Engagement License

Why it fails: This is a Marketing Cloud license, not the Data Cloud permission set license.

Platform Analytics License

Why it fails: Platform Analytics is for CRM Analytics, not Data Cloud.

Add the user to the Salesforce CRM Administrator public group.

Why it fails: Public groups do not govern Data Cloud administrative access.

Grant the user the 'Customize Application' permission on their core Salesforce profile.

Why it fails: 'Customize Application' is for core CRM setup, not Data Cloud administration.

Enable the user as a Marketing Cloud administrator in Engagement setup.

Why it fails: Marketing Cloud roles do not dictate Data Cloud administration.

Scheduled nightly CSV batch drops via Amazon S3

Why it fails: Scheduled CSV drops are batch ingestion; events land only after each nightly run, so latency is hours rather than seconds. It is tempting because S3 is familiar and cheap for bulk transfers, but scheduled batch is the correct choice for historical loads, not real-time event streams.

Salesforce CRM nightly change data capture bundle

Why it fails: A nightly CDC bundle delivers changes once per day, so the pipeline is batch rather than streaming and events are stale on arrival. It is tempting because CDC captures incremental changes efficiently, but nightly bundling suits daily synchronisation, whereas streaming ingestion requires continuous event delivery.

Manual file upload via Data Cloud Setup every 12 hours

Why it fails: Manual uploads are discrete batch operations, not continuous streams, so events arrive up to twelve hours late and cannot support real-time processing. It is tempting when volumes are low or tooling is limited, but manual upload suits one-off backfills or ad-hoc data loads rather than streaming ingestion.

Data Cloud Ingestion API

Why it fails: The Data Cloud Ingestion API is a REST API for pushing data into Data Cloud, not for pulling data from external sources. It does not handle authentication to external APIs. The scenario requires pulling data from an external REST API, so the Ingestion API is not applicable. It is used when external systems push data to Data Cloud, not when Data Cloud pulls data.

External Credential

Why it fails: External Credentials are used with Named Credentials to define authentication protocols, but they are not the primary feature for storing credentials and configuring the connection. While External Credentials are part of the authentication setup, the Named Credential is the endpoint that Data Cloud references. The question asks for the feature to securely store credentials and configure authentication, which is the Named Credential.

Connected App

Why it fails: A Connected App is used to enable external applications to integrate with Salesforce using APIs, not for Data Cloud to authenticate to external services. While Connected Apps can be used for OAuth flows, they are not the feature used to store credentials for Data Cloud ingestion. Data Cloud uses Named Credentials for outbound authentication, not Connected Apps.

Sharing Rule

Why it fails: Sharing Rules are used in Salesforce to extend sharing access to records, but they do not apply to Data Cloud Data Spaces. Data Cloud uses Data Spaces for isolation, not sharing rules. Sharing Rules are not a feature of Data Cloud and cannot be used to segment data within Data Cloud. Therefore, they are not applicable here.

Permission Set

Why it fails: Permission Sets control user access to objects and fields but do not provide data isolation. They can restrict which users can see certain Data Cloud features, but they do not segment data by business unit. Without a Data Space, users with appropriate permission sets could still access data from other parts of the organization. Permission Sets alone cannot achieve the required data isolation.

Data Stream

Why it fails: A Data Stream is used to ingest data from a source into Data Cloud. It does not provide data isolation or access control. While you can have separate data streams for different data sources, they all reside within a Data Space. Data Streams themselves do not restrict user access to data; they are merely ingestion pipelines. The scenario requires isolating data for a subsidiary, which is done via Data Spaces.

Configure a data stream refresh schedule that runs only during loyalty program hours.

Why it fails: Refresh schedules control when data is ingested, not who can access a Data Space. Scheduling streams for specific hours does not grant the Loyalty team visibility into the space. Access is governed by Data Space membership via permission sets. This action is unrelated to making the Data Space available and would not satisfy the requirement.

Create a new Salesforce profile for the Loyalty team and assign it the 'Data Cloud User' license.

Why it fails: Data Cloud access is granted through permission sets, not profiles alone. While users need a Data Cloud license, creating a new profile does not assign Data Space membership. Profiles do not control Data Space access; permission sets with Data Space membership do. This action would not make the Data Space available to the team and could complicate user management.

Enable the 'Data Space Access' setting in Salesforce Setup under Data Cloud Settings.

Why it fails: There is no global 'Data Space Access' setting that must be enabled. Data Space access is controlled through permission sets and membership assignments, not a single org-wide toggle. Enabling a nonexistent setting would not grant the Loyalty team access. The administrator should focus on creating the space and assigning users via permission sets.

Data Model Object

Why it fails: Data Model Objects (DMOs) are the target schema for ingested data. They define the structure but do not filter data. While you can map only certain fields, you cannot filter records at the DMO level. Filtering must occur earlier in the pipeline. Therefore, DMOs are not used for filtering during ingestion.

Data Space

Why it fails: Data Spaces are used for logical isolation of data, not for filtering records during ingestion. While you can have separate Data Spaces for different data sets, they do not provide row-level filtering. Data Spaces are about access control and segregation, not about conditionally ingesting records based on field values. Therefore, they are not used for filtering ingestion.

Identity Resolution

Why it fails: Identity Resolution is used to match and merge records from different sources to create unified profiles. It does not filter data during ingestion; it operates on already ingested data. While it can help deduplicate, it is not a filtering mechanism for data streams. The scenario requires filtering records before ingestion, so Identity Resolution is not appropriate.

Create a formula field on Loyalty_Tier__c that concatenates the record ID and name, then refresh the Data Cloud metadata cache.

Why it fails: Adding a formula field to the CRM object does not register the object with Data Cloud and there is no manual 'metadata cache refresh' step that publishes custom objects as DMOs. Data Cloud discovers CRM objects when a data stream is configured through the Salesforce CRM connector. This option invents a nonexistent mechanism and does not achieve the ingestion goal.

Export Loyalty_Tier__c records to Amazon S3 as CSV and ingest them through the Amazon S3 connector into a standard DMO.

Why it fails: While the Amazon S3 connector can ingest CSV files, this approach bypasses the native Salesforce CRM connector and forces the data into a standard DMO rather than a purpose-built custom DMO for loyalty tiers. It adds unnecessary ETL overhead and loses the direct CRM-to-Data-Cloud lineage. It is not the recommended first action when the source is already a Salesforce object.

Enable the Loyalty_Tier__c object for Data Cloud in Salesforce Setup by selecting it under Data Cloud Object Settings.

Why it fails: There is no 'Data Cloud Object Settings' page in Salesforce Setup where you toggle custom objects for Data Cloud ingestion. Data Cloud ingests CRM objects through configured data streams using the Salesforce CRM connector, not through a per-object enablement toggle in Setup. This distractor reflects a misunderstanding of how Data Cloud discovers and maps CRM metadata.

Create a permission set that grants access to the selected objects and assign it to the Data Cloud integration user.

Why it fails: While the integration user needs permissions to read the selected objects, creating and assigning a permission set is about access control, not about scoping which objects are ingested. The connector configuration itself determines object selection. This action supports the ingestion but does not define the object scope, so it is not one of the required steps to limit the data stream to specific objects.

Configure object-level filters on each data stream to exclude records that do not match project criteria.

Why it fails: Object-level filters refine which records within a selected object are ingested, but they do not determine which objects are included. The architect still needs to select the objects at the connector level. Filters are useful for record-level scoping, not for choosing which objects to ingest, so this action alone does not meet the requirement.

After ingestion, create a batch transform to filter out records from objects that should not be included.

Why it fails: Batch transforms operate after ingestion and can filter records, but they do not prevent unwanted objects from being ingested in the first place. The requirement is to scope the data stream to specific objects, which is handled at connector configuration time. Using a transform would still ingest the unwanted objects, increasing volume and credit consumption.