Salesforce Marketing-Cloud-Intelligence Exam With Confidence Using Practice Dumps

Since the data sources are linked by shared Media Buy names and all other measurements are mapped to appropriate fields without additional manipulations, each unique Media Buy Name from Google DV360 will pair with its corresponding Media Buy Name in Google Campaign Manager. The number of records in the merged table will equal the number of unique Media Buy Names in Google DV360, provided there is a matching name in Google Campaign Manager. The sample shows 4 unique Media Buy Names in Google DV360, thus resulting in 4 records.

In Marketing Cloud Intelligence, when linking two data streams, the parent data stream (File A) provides the main structure. Since 'Override Media Buy Hierarchies' is checked for File A, the hierarchies from File B will be aligned with File A. Given 'Data Updates Permissions' set for file B as 'Update Attributes and Hierarchy', this means that attributes and hierarchy will be updated in the parent file based on the child file (File B), but the child file’s metrics won’t be associated with the parent file’s date.

Hence, when filtering on the entire date range (1-30/8), the resulting view will align with the structure of the parent data stream, showing the KPIs (‘Tasks Completed’ from File A and ‘Tasks Assigned’ from File B) alongside the employee names and squads from the respective files. Since the employee IDs align, the data can be linked properly. However, since the dates do not align (File A data is from 01/08/2019 and File B from 15/08/2019), only attributes from File B will be updated without date association.

The result will look like Option C, where the employee names are corrected based on File B's data, the squads are added from File B, and the tasks_completed and tasks_assigned are displayed from their respective files. The tasks_assigned from File B are shown without date association as File B's date doesn't match with File A's.

To create both 'Platform' and 'Line of Business' fields using Patterns in the Harmonization Center without mapping manipulations, the engineer would need to create separate patterns for each data source mentioned. According to the provided images:

One pattern for LinkedIn Ads, to extract the 'Campaign Name' at position 4 for the Platform and 'Media Buy Name' at position 7 for Line of Business.

One pattern for AdRoll, to extract 'Media Buy Name' at position 3 for Platform and at position 2 for Line of Business.

One pattern for Google Analytics, which seems not required for the Platform but could apply if the Line of Business extraction is necessary, although it states N/A.

Hence, a minimum of 3 patterns would be necessary to create the fields required.