The two ways to achieve this outcome are A and C. Include campaign identifier in the activation name and include campaign identifier in the filename specification. These two options allow the user to specify the Salesforce CRM Campaign ID in the name of the file that is exported to Amazon S3. The activation name and the filename specification are both configurable settings in the activation wizard, where the user can enter the campaign identifier as a text or a variable. The activation name is used as the prefix of the filename, and the filename specification is used as the suffix of the filename. For example, if the activation name is
"Campaign_123" and the filename specification is "{segmentName}_{date}", the resulting file name will be
"Campaign_123_SegmentA_2023-12-18.csv". This way, the user can easily identify the file that corresponds to the campaign and import it into Salesforce CRM.
The other options are not correct. Option B is incorrect because hard coding the campaign identifier as a new attribute in the campaign activation is not possible. The campaign activation does not have any attributes, only settings. Option D is incorrect because including the campaign identifier in the segment name is not sufficient. The segment name is not used in the filename of the exported file, unless it is specified in the filename specification. Therefore, the user will not be able to see the campaign identifier in the file name.

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

Explanation
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

Explanation
The correct answer is D, both team members; Data Cloud adjusts the segment and activation schedules to the time zone of the logged-in user. Data Cloud uses the time zone settings of the logged-in user to display the segment and activation schedules. This means that each user will see the schedules in their own home time zone, regardless of the org time zone setting or the location of other team members. This feature helps users to avoid confusion and errors when scheduling segments and activations across different time zones. The other options are incorrect because they do not reflect how Data Cloud handles time zones. The team member in the Pacific time zone will not see the same time zone as the org time zone setting, unless their personal time zone setting matches the org time zone setting. The team member in the Eastern time zone will not see the schedules in the org time zone setting, unless their personal time zone setting matches the org time zone setting. Data Cloud does not show all schedules in GMT, but rather in the user's local time zone. References:
* Data Cloud Time Zones
* Change default time zones for Users and the organization
* Change your time zone settings in Salesforce, Google & Outlook
* DateTime field and Time Zone Settings in Salesforce