SCDC
Free SCDC practice questions
10 questions from our SCDC practice tests, each with the correct answer and a written explanation. Read them with the answers shown, or switch to quiz mode and answer first.
Question 1 of 10, Solution Positioning
During discovery, a B2B software vendor says its main goal is to identify accounts whose users show rising product usage so sales can target expansion deals. Which Data 360 design element is MOST important to confirm early?
- AA data space per product line so each team sees only its own usage
- BA rapid publish segment on Unified Individual with an email activation
- CAccount-level unification and insights that roll usage up to each unified account Correct answer
- DIndividual-level fuzzy matching on first name for every product user across all sources
Answer and explanation: The use case is account-based, so unifying accounts and building insights that aggregate usage per unified account is central. Individual fuzzy name matching addresses person-level duplicates rather than account rollups. An email activation on individuals targets people, not account expansion. Separate data spaces would split the usage data that must be combined.
Question 2 of 10, Data 360 Setup and Administration
A new marketing analyst must build and publish segments and activations in Data 360 but must not change data streams, mappings, or identity resolution. What is the BEST way to grant access?
- AAssign the standard marketing-focused Data 360 permission set that covers segmentation and activation Correct answer
- BGive the analyst the System Administrator profile with a restrictive permission set group muting
- CShare the data model objects with the analyst through a criteria-based sharing rule
- DAssign the Data 360 admin permission set, then remove the analyst's access to Setup through a custom profile
Answer and explanation: Data 360 ships standard permission sets scoped to personas, and the marketing-oriented ones allow segmentation and activation without administrative control of streams, mappings, or rulesets. The admin permission set grants full configuration rights. A System Administrator profile is far too broad. Sharing rules do not grant Data 360 feature permissions.
Question 3 of 10, Data Source Connection and Ingestion
An e-commerce company must send cart-abandon events from its custom checkout service to Data 360 within minutes, and also load a nightly file of several million historical orders from the same service. Which design meets both needs with the LEAST custom tooling?
- AOne Ingestion API connector with both objects in its schema: streaming for cart events, bulk for nightly orders Correct answer
- BA streaming data transform that receives the cart events and a batch data transform that loads the nightly orders
- CThe Web SDK for cart events captured in the browser and the Salesforce CRM connector for the historical orders
- DTwo Amazon S3 data streams, one refreshed every few minutes for cart events and one nightly for the order file
Answer and explanation: An Ingestion API connector supports both streaming (near real-time micro-batches) and bulk (large CSV jobs) patterns against objects defined in one schema. S3 streams do not deliver near real-time events reliably. The Web SDK captures browser behavior, not server-side checkout events, and the CRM connector reads Salesforce objects only. Data transforms process data already in Data 360 rather than ingesting it.
Question 4 of 10, Data Source Connection and Ingestion
A retailer is creating a data stream for point-of-sale transactions that each have a timestamp. The data will drive purchase-based segments. Which category should the data stream use?
- AOther, because transactions are neither people nor web behavior
- BEngagement, with the record ingestion date selected as the event time field
- CEngagement, with the transaction timestamp selected as the event time field Correct answer
- DProfile, so that each transaction is linked to an individual identifier
Answer and explanation: Time-series behavioral data such as transactions belongs in the Engagement category, and the event time field should be the business timestamp of the transaction so time-based filters work correctly. Profile is for records describing people or accounts. Other suits reference data such as products or stores. Using the ingestion date would distort when purchases actually happened.
Question 5 of 10, Harmonization and Unification
A consultant maps a loyalty file to the Individual data model object. The same file contains an email address and a phone number. Which additional mapping is required so these values can be used by match rules?
- AMap email and phone as custom fields on the Individual object and then flag both fields as match keys in the ruleset
- BMap email and phone to the Party Identification object with an identification type of contact
- CMap email to Contact Point Email and phone to Contact Point Phone, each with Party linked to the Individual ID Correct answer
- DMap email and phone to the Unified Individual object so the values are available after unification
Answer and explanation: Match rules on email and phone use the contact point objects, and each contact point must reference the Individual through its Party field. Custom fields on Individual are not usable as contact point match criteria. Party Identification is meant for identifiers such as loyalty or customer numbers. Unified objects are generated by identity resolution and are not mapping targets.
Question 6 of 10, Harmonization and Unification
Identity resolution produces very few merges even though the business knows many customers exist in both the CRM and e-commerce sources with identical email addresses. What should the consultant check FIRST?
- AWhether segment publishing is set to rapid publish so that unified profiles are recalculated more often
- BWhether the e-commerce email is mapped to Contact Point Email with Party linked to the Individual ID Correct answer
- CWhether the e-commerce data stream uses the Engagement category instead of Profile
- DWhether the reconciliation rule for email uses Source Priority instead of Most Frequent
Answer and explanation: Email match rules only work when emails are mapped to Contact Point Email and linked to the person through the Party field; a missing link prevents matches. Reconciliation rules choose values after linking. A profile source would normally use Profile, but the category alone is not what blocks email matching. Segment publishing does not affect identity resolution.
Question 7 of 10, Data Enhancements, Sharing, and Analysis
Order lines from two acquired brands arrive in different shapes. The team wants a single cleaned data lake object combining both sources, deduplicated on order line ID, refreshed daily, which will then be mapped to the data model. Which approach should be used?
- AA batch data transform that joins, unions, and deduplicates both sources into a new output data lake object Correct answer
- BA streaming data transform that reads both sources and writes events as they arrive throughout the day
- CTwo formula fields per stream that rename the columns, with both streams then mapped directly to the same object
- DA calculated insight that unions both sources and exposes the order lines as dimensions for mapping
Answer and explanation: Batch data transforms combine, reshape, and deduplicate data across sources on a schedule and write the result to an output data lake object for mapping. Formula fields work only on single rows within one stream and cannot deduplicate across sources. Streaming transforms suit continuous single-source processing rather than daily set operations. Calculated insights produce aggregates and cannot be mapped like a data lake object.
Question 8 of 10, Data Enhancements, Sharing, and Analysis
Marketing wants a lifetime spend value for every unified individual, refreshed daily, to use as a segment filter. Which feature should the consultant build?
- AA calculated insight that sums order amounts grouped by unified individual ID Correct answer
- BA formula field on the order data stream that stores the running total
- CA data action that writes each order amount to the Contact record
- DA streaming insight that totals order amounts over a five-minute window
Answer and explanation: Calculated insights run batch SQL aggregations, such as total spend per unified individual, and the results can be used in segmentation. Streaming insights evaluate short time windows for near real-time use cases, not lifetime totals. Formula fields work row by row and cannot aggregate across records. Data actions send events to targets and do not compute aggregates.
Question 9 of 10, Data Activations and Utilization. Choose 2.
A bank wants to activate an audience to an advertising platform but must respect customers who opted out of marketing. Which TWO steps help ensure opted-out customers are excluded? (Choose two.)
- AIngest and map consent data so opt-out status is available on the profile Correct answer
- BSet a reconciliation rule that drops contact points of opted-out customers
- CRely on the advertising platform to remove opted-out members after matching
- DMove opted-out customers to a separate data space after each identity run
- EFilter the segment or activation on consent status to exclude opted-out members Correct answer
Answer and explanation: Consent must be ingested and modeled so it can be evaluated, and the segment or activation must filter on that status to exclude opted-out people. Advertising platforms do not know the bank's consent records. Moving people between data spaces is not a consent mechanism. Reconciliation rules select values and do not remove contact points based on consent.
Question 10 of 10, Data Activations and Utilization. Choose 2.
A marketer wants to grow a campaign audience by finding customers who resemble the best existing buyers. Which TWO features can help? (Choose two.)
- AA data share of the seed audience to an external warehouse
- BA reconciliation rule that copies attributes from top buyers
- CAn Einstein lookalike segment based on the seed audience Correct answer
- DA data space that contains only the best existing customers
- EModel Builder predictions used as segment filter attributes Correct answer
Answer and explanation: Lookalike segments find profiles similar to a seed audience, and model predictions such as propensity scores can be used as segment attributes to find similar prospects. Data shares move data out without creating audiences. Reconciliation rules do not copy attributes between people. Data spaces partition data but do not discover similar customers.