What are unstable measurements?
Answer : C
Unstable measurements refer to metrics that are not aggregated in a standard manner across different grains of data, which can result in inconsistent or unpredictable results when reporting across different dimensions or time frames.
Option C describes a scenario where measurements have manual (Not Auto) aggregation settings, meaning they do not automatically adjust to the aggregation level of the report. Combined with a Granularity setting of 'None', this can lead to instability because the metric isn't bound to a specific granularity, which can cause data inconsistencies or misinterpretations when analyzed at varying levels of detail.
A client's data consists of three data streams as follows:
Data Stream A:

* The data streams should be linked together through a parent-child relationship.
* Out of the three data streams, Data Stream C is considered the source of truth for both the dimensions and measurements.
How should the "Override Media Buy Hierarchies'' checkbox be set in order to meet the client's requirements?
Answer : A
If Data Stream C is the source of truth, the 'Override Media Buy Hierarchies' checkbox should be checked for Data Stream C. This means that the hierarchy defined within Data Stream C will take precedence over any other media buy hierarchies present in Data Streams A or B. By doing so, it enforces that the hierarchy from the source of truth (Data Stream C) is used throughout the dataset, maintaining the integrity of the hierarchical relationships as defined by the most reliable data source.
A technical architect is provided with the logic and Opportunity file shown below:
The opportunity status logic is as follows:
For the opportunity stages ''Interest'', ''Confirmed Interest'' and ''Registered'', the status should be ''Open''.
For the opportunity stage ''Closed'', the opportunity status should be closed Otherwise, return null for the opportunity status.

Given the above file and logic and assume that the file is mapped in the OPPORTUNITIES Data Stream type with the following mapping:
''Day'' --- ''Created Date''
''Opportunity Key'' + Opportunity Key
''Opportunity Stage'' --- Opportunity Stage
A pivot table was created to present the count of opportunities in each stage. The pivot table is filtered on Jan 11th. What is the number of 'opportunities in the Confirmed Interest stage?
Answer : D
pivot table is filtered on January 11th, we refer to the Opportunity file and see that there are no records for January 11th. Thus, there would be zero opportunities in the Confirmed Interest stage on that date. The Salesforce Marketing Cloud Intelligence's pivot table feature allows for the display of counts of entities based on the filtered criteria, which in this scenario would show zero since no records exist for the filtered date. Reference: Salesforce Marketing Cloud Intelligence documentation on pivot table functionalities.
Your client provided the following sources:
Source 1:

Source 2:

Source 3:

As can be seen, the Product values present in sources 2 and 3 are similar and can be linked with the first extraction from 'Media Buy Name' in source1
The end goal is to achieve a final view of Product Group alongside Clicks and Sign Ups, as described below:

Which two options will meet the client's requirement and enable the desired view?
Answer : A, D
To achieve a final view of Product Group alongside Clicks and Sign Ups, we should use:
Option A:
Custom Classification: By using a Custom Classification key populated with the extraction of the Media Buy Name in Source 1, we can then map 'Product' in Source 2 to this key and 'Product Group' to a Custom Classification level. This will allow for grouping and analysis by Product Group, as well as enable the desired view to be created.
Option D:
Harmonization Center: With patterns from Sources 1 and 3, we can create a harmonized dimension 'Product'. Then, by applying a Data Classification rule using Source 2, we can enhance the harmonized dimension. This allows us to align 'Product Group' with the 'Product' from Sources 1 and 3, facilitating an integrated view of Clicks and Sign Ups by Product Group.
A technical architect is provided with the logic and Opportunity file shown below:
The opportunity status logic is as follows:
For the opportunity stages ''Interest'', ''Confirmed Interest'' and ''Registered'', the status should be ''Open''.
For the opportunity stage ''Closed'', the opportunity status should be closed
Otherwise, return null for the opportunity status

Given the above file and logic and assuming that the file is mapped in a GENERIC data stream type with the following mapping:
''Day'' --- Standard ''Day'' field
''Opportunity Key'' > Main Generic Entity Key
''Opportunity Stage'' --- Generic Entity Key 2
''Opportunity Count'' --- Generic Custom Metric
A pivot table was created to present the count of opportunities in each stage. The pivot table is filtered on January (entire month). What is the number of opportunities in the Interest stage?
Answer : B
Based on the Opportunity file, the Opportunity Stage of 'Interest' occurs 3 times across unique Opportunity Keys. Since the pivot table is filtered to present the entire month of January and the Opportunity Stage 'Interest' is listed three times with different Opportunity Keys, the count of opportunities in the 'Interest' stage would be 3.
Which two statements are correct regarding the Parent-Child configuration?
Answer : A, C
Parent-Child configurations in Marketing Cloud Intelligence are used to link different data tables based on shared key values, allowing for the relational organization of data across various streams. While this setup enhances data analysis and reporting by maintaining logical relationships between parent and child tables, it can also introduce performance issues. The complexity increases with the number of relationships and the volume of data, potentially slowing down query processing and data manipulation. Additionally, Parent-Child configurations facilitate the sharing of dimensions and measurements across linked tables, enhancing the data's usability without duplicating it.
A client would like to integrate the following two sources:
Google Campaign Manager:

IAS:

After configuring a Parent-Child relationship between the files, which query should an implementation engineer run in order to QA the setup?
Answer : A
To QA the Parent-Child relationship setup between Google Campaign Manager and IAS data sources, it is essential to query fields that are common to both sources and that are relevant to the relationship. 'Media Buy Type' and 'Media Buy Name' are common identifiers between the two datasets. 'Impressions' from the Google Campaign Manager and 'Analyzed Impressions' from the IAS data are the metrics that should be compared to ensure they match or correlate as expected due to the Parent-Child relationship. The QA process involves checking that the data is correctly aligned and that the metrics from the parent source (Google Campaign Manager) are properly related to the metrics from the child source (IAS). Reference: Salesforce Marketing Cloud Intelligence documentation on data integration, Parent-Child relationships, and QA procedures for data setup.