Data-Con-101 Practice Questions

Salesforce Data Cloud’s fundamental role is to ingest data from multiple sources, match and merge it, and maintain a single, continuously updated view of each person or business. That unified, real-time data layer underpins analytics, marketing, service, and sales use cases.

A. Golden records are an outcome, not the platform’s overarching purpose.

B. Opportunity management is handled by Sales Cloud, not Data Cloud.

C. Marketing analysis occurs in tools such as Marketing Cloud Intelligence, not Data Cloud.

• Salesforce Data Cloud Product Overview, “What Is Data Cloud?” section, para 1 (https://help.salesforce.com/s/articleView?id=sf.cdpoverview.htm)

• Dreamforce ’23 Technical Guide, “Data Cloud Architecture,” slide 4 (publicly hosted PDF)

The use case requires calculating an aggregate value (Lifetime Value) and also viewing that value broken down by a dimension (channel). This is the primary function of Metrics in Data Cloud's Calculated Insights feature. A consultant can create a metric for LTV and include "Channel" as a dimension. This allows for querying the total LTV for a customer or filtering the LTV by each channel. "Metrics on metrics" further extends this by allowing the creation of a composite metric (total LTV) from other base metrics (e.g., LTV from website, LTV from mobile app).

A. Flow Orchestration is a process automation tool for coordinating multi-step, multi-user workflows, not for performing data aggregation and analytics.

B. Nested segments are used to create audiences based on other audiences, which is a segmentation tool, not a calculation engine for metrics.

D. Streaming data transforms are used for row-by-row data manipulation on ingest, not for complex, post-ingestion aggregations across multiple records like LTV.

1. Salesforce Help, Calculated Insights in Data Cloud, Section: "Metrics on Metrics". This page explains, "A metric on a metric is a calculated insight that uses one or more metrics and dimensions." This directly supports building a total LTV from channel-specific metrics.

2. Salesforce Help, Create a Calculated Insight in Data Cloud, Section: "Metrics". The documentation states, "To create a metric, select a calculation, a measure, and one or more dimensions... Dimensions are used to break down and filter your metric." This perfectly describes the requirement.

After new Data Model Objects (DMOs) are created or data streams are mapped, Data Cloud initiates processing to index the values for segmentation. This process, which enables features like value suggestions in the segment builder, is not instantaneous and can take time to complete. The user is experiencing a normal delay while the system processes and makes these new attribute values available for suggestion. The values will appear once the background processing is finished.

B. Standard Data Cloud permissions are sufficient for using value suggestions; no special "Data Aware Specialist" permission set is required for this core feature.

C. Value suggestion works on both direct and related attributes, allowing segment builders to effectively use the full scope of the customer's unified profile.

D. While there might be display limits in the UI, the absence of any suggestions for new data points to a processing delay, not a value limit.

1. Salesforce Help, Create a Segment in Data Cloud. Under the "Tips" section, it notes, "After a new object or field is mapped, it can take up to 24 hours for its values to appear as suggestions." This directly supports the processing delay explanation.

2. Salesforce Help, Segmentation Value Suggestions. This document explains the feature and notes that suggestions are based on processed data, implying a delay between data availability and suggestion availability.

The Marketing Cloud Starter Data Bundles are pre-configured sets of data streams designed to simplify the ingestion of data from Marketing Cloud into Data Cloud. These bundles include data from core Marketing Cloud products. Among the options provided, the bundles for MobileConnect (for SMS engagement) and MobilePush (for push notification engagement) are standard offerings included in this starter package to capture mobile interaction data.

A. Personalization: This is a broad capability, not a specific dataset name in the starter bundles. Data from various sources contributes to personalization.

C. Loyalty Management: This is a distinct Salesforce product with its own data model and is not part of the core Marketing Cloud starter bundles.

1. Salesforce Help, Data Cloud, "Marketing Cloud Starter Data Bundles". The official documentation lists the available data bundles. The list explicitly includes "Marketing Cloud MobileConnect" and "Marketing Cloud MobilePush" alongside others like Email Studio and Journey Builder.

2. Salesforce Help, Data Cloud Setup, "Install the Marketing Cloud Connector". This guide details the setup process and references the data bundles that can be configured, which include MobilePush and MobileConnect data sources.

When a formula field is updated in Data Cloud for data ingested via S3 Connector, the system initiates a full refresh of the data from S3. This ensures that all records, both existing and new, have the formula field recalculated with the updated logic. This behavior is necessary because formula fields are computed fields that need to reflect the new calculation logic across the entire dataset for consistency.

B. Incorrect - Data Cloud recalculates formulas for all records, not just new ones, to maintain data integrity.

C. Incorrect - Data Cloud does support formula field updates for upsert mode data streams.

D. Incorrect - Formula updates require a full refresh, not just the next incremental refresh.

- Salesforce Data Cloud Implementation Guide, "Managing Formula Fields" section, pages 234-236

- Salesforce Data Cloud Connector Documentation, "S3 Connector Configuration," section 4.3

- Salesforce Help Documentation: "Data Cloud Formula Fields and Data Refresh" (Doc ID: DC-FF-2023)

Data Cloud is designed to accommodate a global user base by localizing the display of date and time information. The segmentation and activation scheduling interfaces adjust to the time zone setting of the currently logged-in user. This ensures that each team member, regardless of their physical location, sees schedules in their own familiar time zone, which reduces confusion and prevents errors when scheduling time-sensitive operations. The org's default time zone serves as a baseline, but the user's personal setting overrides the display for that user.

A. This is incorrect because the user in the Eastern time zone would also see the schedule adjusted for their own time zone.

B. This is incorrect because the user in the Pacific time zone would also see the schedule adjusted for their own time zone.

C. Data Cloud does not force all users into a single time zone like GMT for scheduling; it localizes the display for usability.

1. Salesforce Help, Manage Time Zones. "Your Salesforce org’s time zone is used for all scheduled jobs in Data Cloud, including segments, activations, and calculated insights. However, the user interface shows these scheduled times in the logged-in user’s time zone." This statement directly confirms that the UI display is adjusted per user.

2. Salesforce Help, Segment Schedule. "The segment schedule is based on your Data Cloud org’s time zone. The schedule is shown in your local time zone." This reiterates that the display is localized for the user.

Before a data source can be disconnected in Data Cloud, all its dependencies must be removed. The most direct dependencies are the data streams that ingest data from that source and any segments that are built using data that originated from those data streams. The system will generate an error and prevent disconnection until all associated data streams and segments are deleted, ensuring data integrity and preventing downstream processes from failing.

A. Activations are dependent on segments, not directly on the data source. Removing the segment would resolve this indirect dependency.

D. An activation target is the destination for an activation. It is not a direct dependency that would block the disconnection of a source.

1. Salesforce Help. (2024). Disconnect a Data Source in Data Cloud. Document Steps. The procedure explicitly states: "Before you disconnect a data source, delete any data streams and segments that use the data source." This confirms that data streams and segments are the direct dependencies that block disconnection.

2. Salesforce Help. (2024). Data Cloud Glossary. Definitions for "Data Stream" and "Segment". The definitions clarify that data streams are the link to data sources and segments are built from the resulting data, establishing their direct dependency relationship.

The consolidation rate is the percentage of source profiles that have been successfully merged into unified profiles. A low rate indicates that the match rules are too restrictive and are failing to identify matching records. To increase the consolidation rate, the consultant should add more match rules or make existing ones less strict. For example, if the only rule is an exact match on email, adding a new rule for an exact match on phone number or a fuzzy match on name and address will create more opportunities for unification.

A. Reconciliation rules determine which field value (e.g., "Most Recent" name) is used in the unified profile after a match is found. They do not affect the matching process itself.

B. Disabling the ruleset would stop all unification, reducing the consolidation rate to zero, which is the opposite of the desired outcome.

D. While improving source data quality is a good practice, the most direct action within Data Cloud to increase the consolidation rate is to adjust the matching rules.

1. Salesforce Help, Identity Resolution Match Rules, "Match rules define the criteria that Data Cloud uses to link and unify individual profiles... To increase the number of unified profiles, add more match rules." (help.salesforce.com/s/articleView?id=sf.c360aidentityresolutionmatchrules.htm&type=5)

2. Salesforce Trailhead, Identity Resolution in Data Cloud, Module: "Set Up Identity Resolution", Unit: "Configure Identity Resolution Rulesets". This unit explains that match rules are the logic used to link profiles and that their configuration directly impacts consolidation.

The data used in activations is pulled directly from the unified profile. To ensure the "best" email address is activated, it must first be selected as the winning value for the unified profile during identity resolution. This is controlled by reconciliation rules. By creating a Source Priority reconciliation rule for the Contact Point Email object and placing Marketing Cloud as the highest priority source, NTO ensures that if an email from Marketing Cloud exists for a unified individual, it will be the one saved to the unified profile and subsequently used in activations.

A. Using 'Is Active' as a match rule helps group records but does not determine which email address is chosen as the final value for the unified profile.

B. Activations do not have a "source priority order" feature. They use the data already finalized in the unified profile by the reconciliation rules.

D. The 'Last Updated' rule selects the most recent data, which may not be the "best" or most reliable data source compared to a deliberately prioritized one.

1. Salesforce Help, Reconciliation Rules. Section: "Source Priority". It states, "This rule defines the order of precedence of your data sources. The rule uses the value from the highest-ranked data source that contains a value for the attribute."

2. Salesforce Help, Identity Resolution Ruleset Example. This page provides examples showing how reconciliation rules like Source Priority are used to select the most trusted data for the unified profile, which is the prerequisite for any activation.

3. Salesforce Help, Create an Activation. The documentation shows that activations are configured to use attributes from the unified data model objects, confirming that the data must be correct on the unified profile before activation.

In Salesforce Data Cloud, access to data segregated by data spaces is controlled through permission sets, not profiles. Each data space is associated with a specific permission set. To grant a user access to the data within a particular data space, an administrator must assign the corresponding permission set to that user. In this scenario, the EMEA sales reps lack the permission set linked to the APAC data space, which prevents them from visualizing APAC data. The fact that APAC reps can see their own data confirms the APAC data space itself is configured correctly.

A. Profiles are not used to grant access to data spaces; this is managed exclusively by permission sets.

B. The APAC data space must be associated with a permission set, otherwise, no one, including APAC reps, could access its data.

C. The APAC data space must be associated with a permission set, not a profile, for user access control.

1. Salesforce Help, Data Cloud, "Assign Users to a Data Space". This document states, "To give users access to a data space, assign them the permission set associated with the data space."

2. Salesforce Help, Data Cloud, "Data Spaces". This guide explains, "After you create a data space, a permission set with the same name is automatically created...To grant access to a data space, assign its permission set to users."