Salesforce Data-Cloud-Consultant Salesforce Certified Data Cloud Consultant(WI24) Exam Practice Test

A streaming insight is a type of insight that analyzes streaming data in real time and triggers actions based on predefined conditions. A data action is a type of action that executes a flow, a data action target, or a data action script when an insight is triggered. By using a streaming insight paired with a data action, a consultant can accommodate Cumulus Financial’s request to track the daily transaction volume of each customer and send out a notification when the volume is outside the normal range. A calculated insight is a type of insight that performs calculations on data in a data space and stores the results in a data extension. A streaming data transform is a type of data transform that applies transformations to streaming data in real time and stores the results in a data extension. A flow is a type of automation that executes a series of actions when triggered by an event, a schedule, or another flow. None of these options can achieve the same functionality as a streaming insight paired with a data action. References: Use Insights in Data Cloud Unit, Streaming Insights and Data Actions Use Cases, Streaming Insights and Data Actions Limits and Behaviors

 Nested segments are segments that include or exclude one or more existing segments. They allow the marketing team to reuse filters and maintain consistency in their data by using an existing segment to build a new one. For example, the marketing team can create a nested segment that includes High Investment Balance Customers and excludes customers who have opted out of email marketing. This way, they can leverage the foundational segment and apply additional criteria without duplicating the rules. The other options are not the best features to ensure consistency because:

• B. A calculated insight is a data object that performs calculations on data lake objects or CRM data and returns a result. It is not a segment and cannot be used for activation or personalization.
• C. A data kit is a bundle of packageable metadata that can be exported and imported across Data Cloud orgs. It is not a feature for creating segments, but rather for sharing components.
• D. Cloning a segment creates a copy of the segment with the same rules and filters. It does not allow the marketing team to add or remove criteria from the original segment, and it may create confusion and redundancy. References: Create a Nested Segment - Salesforce, Save Time with Nested Segments (Generally Available) - Salesforce, Calculated Insights - Salesforce, Create and Publish a Data Kit Unit | Salesforce Trailhead, Create a Segment in Data Cloud - Salesforce

The correct answer is A. Deactivate the segment. If a segment is no longer needed, it can be deactivated through Data Cloud and applies to all chosen targets. A deactivated segment no longer publishes, but it can be reactivated at any time1. This option allows the user to pause a segment activation with the intent of using that segment again.

The other options are incorrect for the following reasons:

• B. Delete the segment. This option permanently removes the segment from Data Cloud and cannot be undone2. This option does not allow the user to use the segment again.
• C. Skip the activation. This option skips the current activation cycle for the segment, but does not affect the future activation cycles3. This option does not pause the segment activation indefinitely.
• D. Stop the publish schedule. This option stops the segment from publishing to the chosen targets, but does not deactivate the segment4. This option does not pause the segment activation completely.

References:

• 1: Deactivated Segment article on Salesforce Help
• 2: Delete a Segment article on Salesforce Help
• 3: Skip an Activation article on Salesforce Help
• 4: Stop a Publish Schedule article on Salesforce Help

The Data Cloud User permission set is the minimum permission set needed to accommodate this use case. The Data Cloud User permission set grants access to the Data Explorer feature, which allows the user to review individual rows of ingested data and validate that it has been modeled successfully to its linked data model object. The user can also make changes to the data model object fields, such as adding or removing fields, changing field types, or creating formula fields. The Data Cloud User permission set does not grant access to other Data Cloud features or tasks, such as creating data streams, creating segments, creating activations, or managing users. The other permission sets are either too restrictive or too permissive for this use case. The Data Cloud for Marketing Specialist permission set only grants access to the segmentation and activation features, but not to the Data Explorer feature. The Data Cloud Admin permission set grants access to all Data Cloud features and tasks, including the Data Explorer feature, but it is more than what the user needs. The Data Cloud for Marketing Data Aware Specialist permission set grants access to the Data Explorer feature, but also to the segmentation and activation features, which are not required for this use case. References: Data Cloud Standard Permission Sets, Data Explorer, Set Up Data Cloud Unit

When ingesting data from an Amazon S3 bucket, the consultant should configure the following options:

• The refresh mode should be set to “Upsert”, which means that new and updated records will be added or updated in Data Cloud, while existing records will be preserved. This ensures that the data is always up to date and consistent with the source.
• The filename should contain a wildcard to accommodate the timestamp, which means that the file name pattern should include a variable part that matches the timestamp format. For example, if the file name is store_transactions_2023-12-18.csv, the wildcard could be store_transactions_*.csv. This ensures that the ingestion process can identify and process the correct file every day.

The other options are not necessary or relevant for this scenario:

• Deletion of old files is a feature of the Amazon S3 bucket, not the Data Cloud ingestion process. Data Cloud does not delete any files from the source, nor does it require the source files to be deleted after ingestion.
• Full Refresh is a refresh mode that deletes all existing records in Data Cloud and replaces them with the records from the source file. This is not suitable for this scenario, as it would result in data loss and inconsistency, especially if the source file only contains the summary of the last 24 hours of transactions. References: Ingest Data from Amazon S3, Refresh Modes

The consolidation rate is a metric that measures the amount by which source profiles are combined to produce unified profiles in Data Cloud, calculated as 1 - (number of unified profiles / number of source profiles). A higher consolidation rate means that more source profiles are matched and merged into fewer unified profiles, while a lower consolidation rate means that fewer source profiles are matched and more unified profiles are created. There are two likely explanations for why the consolidation rate has recently increased for a customer:

• New data sources have been added to Data Cloud that largely overlap with the existing profiles. This means that the new data sources contain many profiles that are similar or identical to the profiles from the existing data sources. For example, if a customer adds a new CRM system that has the same customer records as their old CRM system, the new data source will overlap with the existing one. When Data Cloud ingests the new data source, it will use the identity resolution ruleset to match and merge the overlapping profiles into unified profiles, resulting in a higher consolidation rate.
• Identity resolution rules have been added to the ruleset to increase the number of matched profiles. This means that the customer has modified their identity resolution ruleset to include more match rules or more match criteria that can identify more profiles as belonging to the same individual. For example, if a customer adds a match rule that matches profiles based on email address and phone number, instead of just email address, the ruleset will be able to match more profiles that have the same email address and phone number, resulting in a higher consolidation rate.

References: Identity Resolution Calculated Insight: Consolidation Rates for Unified Profiles, Configure Identity Resolution Rulesets

 To ensure that freshly imported data from an Amazon S3 Bucket is ready and available to use for any segment, the following processes should be run in this order:

• Refresh Data Stream: This process updates the data lake objects in Data Cloud with the latest data from the source system. It can be configured to run automatically or manually, depending on the data stream settings1. Refreshing the data stream ensures that Data Cloud has the most recent and accurate data from the Amazon S3 Bucket.
• Identity Resolution: This process creates unified individual profiles by matching and consolidating source profiles from different data streams based on the identity resolution ruleset. It runs daily by default, but can be triggered manually as well2. Identity resolution ensures that Data Cloud has a single view of each customer across different data sources.
• Calculated Insight: This process performs calculations on data lake objects or CRM data and returns a result as a new data object. It can be used to create metrics or measures for segmentation or analysis purposes3. Calculated insights ensure that Data Cloud has the derived data that can be used for personalization or activation.

References:

• 1: Configure Data Stream Refresh and Frequency - Salesforce
• 2: Identity Resolution Ruleset Processing Results - Salesforce
• 3: Calculated Insights - Salesforce

The best option to map the data to be used for both segmentation and identity resolution is to create custom fields on the standard Individual DMO. This way, the consultant can leverage the existing fields and functionality of the Individual DMO, such as identity resolution rulesets, calculated insights, and data actions, while adding the additional fields that are specific to the beauty company’s data1. Creating a custom DMO from scratch or duplicating the standard Individual DMO would require more effort and maintenance, and might not be compatible with the existing features of Data Cloud. Creating a custom DMO with only the additional fields and mapping it to the standard Individual DMO would create unnecessary complexity and redundancy, and might not allow the use of the custom fields for identity resolution. References:

• 1: Data Model Objects in Data Cloud

The most likely cause of this issue is that value suggestion is still processing and takes up to 24 hours to be available. Value suggestion is a feature that enables you to see suggested values for data model object (DMO) fields when creating segment filters. However, this feature needs to be enabled for each DMO field, and it can take up to 24 hours for the suggested values to appear after enabling the feature1. Therefore, if a user is not seeing suggested values from newly-modeled data, it could be that the data has not been processed yet by the value suggestion feature. References:

• Use Value Suggestions in Segmentation

To support separate Amazon S3 buckets for data ingestion and activation, you need to configure dedicated S3 data sources in Data Cloud setup. Data sources are used to identify the origin and type of the data that you ingest into Data Cloud1. You can create different data sources for each S3 bucket that you want to use for ingestion or activation, and specify the bucket name, region, and access credentials2. This way, you can separate and organize your data by different criteria, such as brand, region, product, or business unit3. The other options are incorrect because they do not support separate S3 buckets for data ingestion and activation. Multiple S3 connectors are not a valid configuration in Data Cloud setup, as there is only one S3 connector available4. Dedicated S3 data sources in activation setup are not a valid configuration either, as activation setup does not require data sources, but activation targets5. Separate user credentials for data stream and activation target are not sufficient to support separate S3 buckets, as you also need to specify the bucket name and region for each data source2. References: Data Sources Overview, Amazon S3 Storage Connector, Data Spaces Overview, Data Streams Overview, Data Activation Overview

 Data Cloud is a platform that enables you to activate all your customer data across Salesforce applications and other systems. Data Cloud allows you to create a unified profile of each customer by ingesting, transforming, and linking data from various sources, such as CRM, marketing, commerce, service, and external data providers. Data Cloud also provides insights and analytics on customer behavior, preferences, and needs, as well as tools to segment, target, and personalize customer interactions. Data Cloud’s primary value to customers is to provide a unified view of a customer and their related data, which can help you deliver better customer experiences, increase loyalty, and drive growth. References: Salesforce Data Cloud, When Data Creates Competitive Advantage

A streaming insight is a feature that allows users to create and monitor real-time metrics from streaming data sources, such as web and mobile events. A streaming insight can also trigger data actions, such as sending notifications, creating records, or updating fields, based on the metric values and conditions. Therefore, a streaming insight is the best feature to achieve the goal of identifying candidates who have browsed the jobs page on the website at least twice within the last 24 hours, and adding them to the recruiting system. The other options are incorrect because:

• A streaming data transform is a feature that allows users to transform and enrich streaming data using SQL expressions, such as filtering, joining, aggregating, or calculating values. However, a streaming data transform does not provide the ability to monitor metrics or trigger data actions based on conditions.
• A calculated insight is a feature that allows users to define and calculate multidimensional metrics from data using SQL expressions, such as LTV, CSAT, or average order value. However, a calculated insight is not suitable for real-time data analysis, as it runs on a scheduled basis and does not support data actions.
• A batch data transform is a feature that allows users to create and schedule complex data transformations using a visual editor, such as joining, aggregating, filtering, or appending data. However, a batch data transform is not suitable for real-time data analysis, as it runs on a scheduled basis and does not support data actions. References: Streaming Insights, Create a Streaming Insight, Use Insights in Data Cloud, Learn About Data Cloud Insights, Data Cloud Insights Using SQL, Streaming Data Transforms, Get Started with Batch Data Transforms in Data Cloud, Transformations for Batch Data Transforms, Batch Data Transforms in Data Cloud: Quick Look, Salesforce Data Cloud: AI CDP.

To configure an activation to a Marketing Cloud activation target, you need to choose a segment and select contact points. Choosing a segment allows you to specify which unified individuals you want to activate. Selecting contact points allows you to map the attributes from the segment to the fields in the Marketing Cloud data extension. You do not need to add additional attributes or add the calculated insight in the activation, as these are already part of the segment definition. References: Create a Marketing Cloud Activation Target; Types of Data Targets in Data Cloud

 To create a multi-dimensional metric to identify unified individual lifetime value (LTV), the sequence of data model object (DMO) joins that is necessary within the calculated Insight is Unified Individual > Unified Link Individual > Sales Order. This is because the Unified Individual DMO represents the unified profile of an individual or entity that is created by identity resolution1. The Unified Link Individual DMO represents the link between a unified individual and an individual from a source system2. The Sales Order DMO represents the sales order information from a source system3. By joining these three DMOs, you can calculate the LTV of a unified individual based on the sales order data from different source systems. The other options are incorrect because they do not join the correct DMOs to enable the LTV calculation. Option B is incorrect because the Individual DMO represents the source profile of an individual or entity from a source system, not the unified profile4. Option C is incorrect because the join order is reversed, and you need to start with the Unified Individual DMO to identify the unified profile. Option D is incorrect because it is missing the Unified Link Individual DMO, which is needed to link the unified profile with the source profile. References: Unified Individual Data Model Object, Unified Link Individual Data Model Object, Sales Order Data Model Object, Individual Data Model Object

The correct answer is D. The CRM Connector allows standard fields to stream into Data Cloud in real time. This means that any changes to the standard fields in the CRM data source are reflected in Data Cloud almost instantly, without waiting for the next scheduled synchronization. This feature enables Data Cloud to have the most up-to-date and accurate CRM data for segmentation and activation1.

The other options are incorrect for the following reasons:

• A. CRM data can be manually refreshed at any time by clicking the Refresh button on the data stream detail page2. This option is false.
• B. The CRM Connector’s synchronization times can be customized to up to 60-minute intervals, not 15-minute intervals3. This option is false.
• C. Formula fields are not refreshed at regular sync intervals, but only at the next full refresh4. A full refresh is a complete data ingestion process that occurs once every 24 hours or when manually triggered. This option is false.

References:

• 1: Connect and Ingest Data in Data Cloud article on Salesforce Help
• 2: Data Sources in Data Cloud unit on Trailhead
• 3: Data Cloud for Admins module on Trailhead
• 4: [Formula Fields in Data Cloud] unit on Trailhead
• : [Data Streams in Data Cloud] unit on Trailhead

The feature that the consultant should use to solution for this use case is C. Activation alert. Activation alerts are notifications that are sent to users when an activation fails or succeeds for a segment. Activation alerts can be configured in the Activation Settings page, where the consultant can specify the recipients, the frequency, and the conditions for sending the alerts. Activation alerts can help the customer to monitor the status of their activations and troubleshoot any issues that may arise. References: Salesforce Data Cloud Consultant Exam Guide, Activation Alerts

 To address this new use case, the consultant should map the primary key from the two systems to Party Identification, using CRM ID as the identification name for both, and create a matching rule based on party identification that matches on CRM ID as the party identification name. This way, the consultant can ensure that the CRM Contacts and Marketing Contacts are matched based on their CRM ID, which is a unique identifier for each individual. By using Party Identification, the consultant can also leverage the benefits of this attribute, such as being able to match across different entities and sources, and being able to handle multiple values for the same individual. The other options are incorrect because they either do not use the CRM ID as the primary key, or they do not use Party Identification as the attribute type. References: Configure Identity Resolution Rulesets, Identity Resolution Match Rules, Data Cloud Identity Resolution Ruleset, Data Cloud Identity Resolution Config Input

The time zone that is used to publish and refresh data when performing segmentation or activation is D. Time zone set by the Salesforce Data Cloud org. This time zone is the one that is configured in the org settings when Data Cloud is provisioned, and it applies to all users and activities in Data Cloud. This time zone determines when the segments are scheduled to refresh and when the activations are scheduled to publish. Therefore, it is important to consider the time zone difference between the Data Cloud org and the destination systems or channels when planning the segmentation and activation strategies. References: Salesforce Data Cloud Consultant Exam Guide, Segmentation, Activation

 Batch transforms are a feature that allows creating new data lake objects based on existing data lake objects and applying transformations on them. This can be useful for splitting, merging, or reshaping data to fit the data model or business requirements. In this case, the consultant can use batch transforms to create a second data lake object that contains only the airline points from the original loyalty data object. The original object can be modified to contain only the hotel points. This way, the client can have two separate records for each point system and track and process them accordingly. References: Batch Transforms, Create a Batch Transform

Value suggestion is a feature that allows users to see suggested values for data model object (DMO) fields when creating segment filters. However, this feature can take up to 24 hours to process and display the values for newly-modeled data. Therefore, if a user is not seeing suggested values from newly-modeled data, it is likely that the value suggestion is still processing and will be available soon. The other options are incorrect because value suggestion does not require any specific permissions, can work on both direct and related attributes, and can return more than 50 values for a specific attribute, depending on the data type and frequency of the values. References: Use Value Suggestions in Segmentation, Data Cloud Limits and Guidelines

 The error “Segment references too many data lake objects (DLOs)” occurs when a segment query exceeds the limit of 50 DLOs that can be referenced in a single query. This can happen when the segment has too many filters, nested segments, or exclusion criteria that involve different DLOs. To remedy this issue, the consultant can try the following troubleshooting tips:

• Split the segment into smaller segments. The consultant can divide the segment into multiple segments that have fewer filters, nested segments, or exclusion criteria. This can reduce the number of DLOs that are referenced in each segment query and avoid the error. The consultant can then use the smaller segments as nested segments in a larger segment, or activate them separately.
• Use calculated insights in order to reduce the complexity of the segmentation query. The consultant can create calculated insights that are derived from existing data using formulas. Calculated insights can simplify the segmentation query by replacing multiple filters or nested segments with a single attribute. For example, instead of using multiple filters to segment individuals based on their purchase history, the consultant can create a calculated insight that calculates the lifetime value of each individual and use that as a filter.

The other options are not troubleshooting tips that can help remedy this issue. Refining segmentation criteria to limit up to five custom data model objects (DMOs) is not a valid option, as the limit of 50 DLOs applies to both standard and custom DMOs. Spacing out the segment schedules to reduce DLO load is not a valid option, as the error is not related to the DLO load, but to the segment query complexity.

References:

• Troubleshoot Segment Errors
• Create a Calculated Insight
• Create a Segment in Data Cloud

 The Ignore Empty Value option in identity resolution allows customers to ignore empty fields when running reconciliation rules. Reconciliation rules are used to determine the final value of an attribute for a unified individual profile, based on the values from different sources. The Ignore Empty Value option can be set to true or false for each attribute in a reconciliation rule. If set to true, the reconciliation rule will skip any source that has an empty value for that attribute and move on to the next source in the priority order. If set to false, the reconciliation rule will consider any source that has an empty value for that attribute as a valid source and use it to populate the attribute value for the unified individual profile.

The other options are not correct descriptions of what the Ignore Empty Value option does in identity resolution. The Ignore Empty Value option does not affect the custom match rules or the standard match rules, which are used to identify and link individuals across different sources based on their attributes. The Ignore Empty Value option also does not ignore individual object records with empty fields when running identity resolution rules, as identity resolution rules operate on the attribute level, not the record level.

References:

• Data Cloud Identity Resolution Reconciliation Rule Input
• Configure Identity Resolution Rulesets
• Data and Identity in Data Cloud

The correct answer is A. Streaming transforms. Streaming transforms are a feature of Data Cloud that allows real-time data integration with Salesforce CRM. Streaming transforms use the Data Cloud Streaming API to synchronize micro-batches of updates between the CRM data source and Data Cloud in near-real time1. Streaming transforms enable Data Cloud to have the most current and accurate CRM data for segmentation and activation2.

The other options are incorrect for the following reasons:

• B. Data model triggers. Data model triggers are a feature of Data Cloud that allows custom logic to be executed when data model objects are created, updated, or deleted3. Data model triggers do not integrate data with Salesforce CRM, but rather manipulate data within Data Cloud.
• C. Sales and Service bundle. Sales and Service bundle is a feature of Data Cloud that allows pre-built data streams, data model objects, segments, and activations for Sales Cloud and Service Cloud data sources4. Sales and Service bundle does not integrate data in real time with Salesforce CRM, but rather ingests data at scheduled intervals.
• D. Data actions and Lightning web components. Data actions and Lightning web components are features of Data Cloud that allow custom user interfaces and workflows to be built and embedded in Salesforce applications5. Data actions and Lightning web components do not integrate data with Salesforce CRM, but rather display and interact with data within Salesforce applications.

References:

• 1: Load Data into Data Cloud
• 2: [Data Streams in Data Cloud]
• 3: [Data Model Triggers in Data Cloud] unit on Trailhead
• 4: [Sales and Service Bundle in Data Cloud] unit on Trailhead
• 5: [Data Actions and Lightning Web Components in Data Cloud] unit on Trailhead
• : [Data Model in Data Cloud] unit on Trailhead
• : [Create a Data Model Object] article on Salesforce Help
• : [Data Sources in Data Cloud] unit on Trailhead
• : [Connect and Ingest Data in Data Cloud] article on Salesforce Help
• : [Data Spaces in Data Cloud] unit on Trailhead
• : [Create a Data Space] article on Salesforce Help
• : [Segments in Data Cloud] unit on Trailhead
• : [Create a Segment] article on Salesforce Help
• : [Activations in Data Cloud] unit on Trailhead
• : [Create an Activation] article on Salesforce Help

 Identity resolution is the process of creating unified profiles of individuals by matching and merging data from different sources. When there is conflicting information in the data model, such as different names, addresses, or phone numbers for the same person, identity resolution leverages reconciliation rules to select the most accurate and complete attributes for the unified profile. Reconciliation rules are configurable rules that define how to resolve conflicts based on criteria such as recency, frequency, source priority, or completeness. For example, a reconciliation rule can specify that the most recent name or the most frequent phone number should be selected for the unified profile. Reconciliation rules can be applied at the attribute level or the contact point level. References: Identity Resolution, Reconciliation Rules, Salesforce Data Cloud Exam Questions

 The field type Text should be chosen to ensure that leading zeros in the purchase order number are preserved. This is because text fields store alphanumeric characters as strings, and do not remove any leading or trailing characters. On the other hand, number, decimal, and serial fields store numeric values as numbers, and automatically remove any leading zeros when displaying or exporting the data123. Therefore, text fields are more suitable for storing data that needs to retain its original format, such as purchase order numbers, zip codes, phone numbers, etc. References:

• Zeros at the start of a field appear to be omitted in Data Exports
• Keep First ‘0’ When Importing a CSV File
• Import and export address fields that begin with a zero or contain a plus symbol

 The best option that the consultant should do to ensure the ecommerce data is ready for use for each of the scheduled activations is A. Use Flow to trigger a change data event on the ecommerce data to refresh calculated insights and segments before the activations are scheduled to run. This option allows the consultant to use the Flow feature of Data Cloud, which enables automation and orchestration of data processing tasks based on events or schedules. Flow can be used to trigger a change data event on the ecommerce data, which is a type of event that indicates that the data has been updated or changed. This event can then trigger the refresh of the calculated insights and segments that depend on the ecommerce data, ensuring that they reflect the latest data. The refresh of the calculated insights and segments can be completed before the activations are scheduled to run, ensuring that the customer’s scheduled campaign messages are accurate and relevant.

The other options are not as good as option A. Option B is incorrect because setting a refresh schedule for the calculated insights to occur every hour may not be sufficient or efficient. The refresh schedule may not align with the activation schedule, resulting in outdated or inconsistent data. The refresh schedule may also consume more resources and time than necessary, as the ecommerce data may not change every hour. Option C is incorrect because ensuring the activations are set to Incremental Activation and automatically publish every hour may not solve the problem. Incremental Activation is a feature that allows only the new or changed records in a segment to be activated, reducing the activation time and size. However, this feature does not ensure that the segment data is updated or refreshed based on the ecommerce data. The activation schedule may also not match the ecommerce data update schedule, resulting in inaccurate or irrelevant campaign messages. Option D is incorrect because ensuring the segments are set to Rapid Publish and set to refresh every hour may not be optimal or effective. Rapid Publish is a feature that allows segments to be published faster by skipping some validation steps, such as checking for duplicate records or invalid values. However, this feature may compromise the quality or accuracy of the segment data, and may not be suitable for all use cases. The refresh schedule may also have the same issues as option B, as it may not sync with the ecommerce data update schedule or the activation schedule, resulting in outdated or inconsistent data. References: Salesforce Data Cloud Consultant Exam Guide, Flow, Change Data Events, Calculated Insights, Segments, [Activation]

 A Unified Individual is a profile that combines data from multiple sources using identity resolution rules in Data Cloud. A Unified Individual can have multiple contact points, such as email, phone, or address, that link to different systems and records. A consultant can use the following features to display all cases associated with a Unified Individual on a contact record:

• Profile API: This is a REST API that allows you to retrieve and update Unified Individual profiles and related attributes in Data Cloud. You can use the Profile API to query the cases that are related to a Unified Individual by using the contact point ID or the unified ID as a filter. You can also use the Profile API to update the Unified Individual profile with new or modified case information from other systems.
• Lightning Web Components: These are custom HTML elements that you can use to create reusable UI components for your Salesforce apps. You can use Lightning Web Components to create a custom component that displays the cases related to a Unified Individual on a contact record. You can use the Profile API to fetch the data from Data Cloud and display it in a table, list, or chart format. You can also use Lightning Web Components to enable actions, such as creating, editing, or deleting cases, from the contact record.

The other two options are not relevant for this use case. A Data Action is a type of action that executes a flow, a data action target, or a data action script when an insight is triggered. A Data Action is used for activation and personalization, not for displaying data on a contact record. A Query APL is a query language that allows you to access and manipulate data in Data Cloud. A Query APL is used for data exploration and analysis, not for displaying data on a contact record. References: Profile API Developer Guide, Lightning Web Components Developer Guide, Create Unified Individual Profiles Unit

Building a trust-based, first-party data asset means collecting, managing, and activating data from your own customers and prospects in a way that respects their privacy and preferences. It also means providing them with clear and honest information about how you use their data, what benefits they can expect from sharing their data, and how they can control their data. By doing so, you can create a mutually beneficial relationship with your customers, where they trust you to use their data responsibly and ethically, and you can deliver more relevant and personalized experiences to them. A trust-based, first-party data asset can help you improve customer loyalty, retention, and growth, as well as comply with data protection regulations and standards. References: Use first-party data for a powerful digital experience, Why first-party data is the key to data privacy, Build a first-party data strategy

To use the Amazon S3 Storage Connector in Data Cloud, the consultant needs to provide the S3 bucket name, region, and access key and secret key for authentication. The access key and secret key are generated by AWS and can be managed in the IAM console. The other options are not supported by the S3 Storage Connector or by Data Cloud. References: Amazon S3 Storage Connector - Salesforce, How to Use the Amazon S3 Storage Connector in Data Cloud | Salesforce Developers Blog

Learn more

1

help.salesforce.com2

developer.salesforce.com

The consolidation rate is the amount by which source profiles are combined to produce unified profiles, calculated as 1 - (number of unified individuals / number of source individuals). For example, if you ingest 100 source records and create 80 unified profiles, your consolidation rate is 20%. To increase the consolidation rate, you need to increase the number of matches between source profiles, which can be done by adding more match rules. Match rules define the criteria for matching source profiles based on their attributes. By increasing the number of match rules, you can increase the chances of finding matches between source profiles and thus increase the consolidation rate. On the other hand, changing reconciliation rules, including additional attributes, or reducing the number of match rules can decrease the consolidation rate, as they can either reduce the number of matches or increase the number of unified profiles. References: Identity Resolution Calculated Insight: Consolidation Rates for Unified Profiles, Identity Resolution Ruleset Processing Results, Configure Identity Resolution Rulesets

 The consultant should use B. Segmentation exclude rules to remove the recent customers. Segmentation exclude rules are filters that can be applied to a segment to exclude records that meet certain criteria. The consultant can use segmentation exclude rules to exclude customers who have made purchases within the last week from the segment that contains customers who have purchased within the past 6 months. This way, the segment will only include customers who are eligible for the promotional campaign.

The other options are not correct. Option A is incorrect because batch transforms are data processing tasks that can be applied to data streams or data lake objects to modify or enrich the data. Batch transforms are not used for segmentation or activation. Option C is incorrect because related attributes are attributes that are derived from the relationships between data model objects. Related attributes are not used for excluding records from a segment. Option D is incorrect because streaming insights are derived attributes that are calculated at the time of data ingestion. Streaming insights are not used for excluding records from a segment. References: Salesforce Data Cloud Consultant Exam Guide, Segmentation, Segmentation Exclude Rules