Explanation:

When a consultant encounters an OAuth 2.0 authentication issue while setting up a data stream in Marketing Cloud Intelligence, the correct place to verify and configure the authentication settings within Salesforce is the Named Credential.

B — Named Credential (Correct)
Named Credentials in Salesforce store the authentication settings and endpoint URL for external system connections — including OAuth 2.0 configurations.
When setting up a Marketing Cloud Intelligence data stream, Salesforce uses a Named Credential to securely handle the OAuth 2.0 token exchange between Salesforce and Marketing Cloud Intelligence.

A Named Credential encapsulates:
- The authentication protocol (e.g., OAuth 2.0)
- The endpoint URL of the external service
- The credentials and token settings needed to authenticate

If there is an OAuth 2.0 authentication issue, the consultant should navigate to:

Setup → Security → Named Credentials
and verify that the credential linked to Marketing Cloud Intelligence is correctly configured with the right:

- Client ID & Client Secret
- Token endpoint URL
- OAuth scopes
- Callback/Redirect URL

Why the Other Options Are Incorrect:

A — Custom Metadata:
Custom Metadata is used to store application configuration data and custom settings. While it can store some configuration values, it does not directly manage OAuth 2.0 authentication flows or external endpoint credentials.

C — Connected App:
A Connected App defines how external applications connect TO Salesforce (inbound). It is not where you configure Salesforce's outbound authentication to external systems like Marketing Cloud Intelligence.

D — Auth. Provider:
Auth Providers are used to configure SSO and third-party authentication, but they work in conjunction with Named Credentials. The primary place to troubleshoot and verify the data stream's OAuth 2.0 setup is the Named Credential, not the Auth Provider directly.

Key Takeaway:
In Salesforce, Named Credentials are the go-to configuration point for managing outbound OAuth 2.0 authentication to external platforms like Marketing Cloud Intelligence. When a data stream setup fails due to an authentication error, always check the Named Credential configuration first.

Reference:
Salesforce Help: Named Credentials – Defining Authentication for Callouts
Salesforce Marketing Cloud Intelligence: Data Stream Setup and Authentication
Salesforce Media Cloud Accredited Professional (AP-217) Study Guide

Explanation:

Salesforce Media Cloud includes a purpose-built Party Model designed to support the complex relationships that exist in media and advertising industries — such as between clients (advertisers), agencies, and individuals. In this model, advertisers and agencies are both modeled as Accounts, and contacts within those organizations are standard Contacts.
The Party Model enables the use of Party Roles and Party Relationship Groups, which allow organizations to define many-to-many relationships with clearly defined roles, such as “Agency of Record,” “Creative Agency,” or “Media Buying Agency.” This structure is much more flexible and scalable than custom-built relationships or account hierarchies. It also supports reporting and future scalability if more relationship types or additional entities need to be mapped. This is the recommended and standard method in Media Cloud for managing these types of relationships.

❌ Incorrect Answer:

B. Advertisers and agencies should be created as Accounts, with agencies listed as child Accounts to the client Accounts, with Contacts related to those.
This misuses the Account hierarchy, which is generally intended for modeling corporate structures (e.g., parent companies and subsidiaries), not business partnerships. Using child Accounts to represent agencies implies a legal or organizational dependency that doesn’t exist in a client-agency relationship. It also does not allow for role definition (e.g., identifying which agency is the “Agency of Record”) and is not scalable for complex many-to-many relationships.

C. Advertisers should be created as Accounts, and agencies should be represented by a custom field added to the Contact object. Contacts should then be assigned to the Accounts.
This is a poor data modeling practice because it treats agencies as fields rather than as entities. Agencies are companies (Accounts), not attributes of Contacts. This model fails to support multiple agencies, agency roles, or the ability to manage relationships over time. It also lacks scalability and clarity for reporting or workflow automation.

D. Advertisers and agencies should be created as Accounts, and a custom lookup field should be created to represent the client/agency relationship. Contacts should be created under the Accounts.
While technically feasible, this approach involves custom development and does not leverage the existing Media Cloud Party Model, which was specifically designed for this purpose. A single custom lookup cannot handle multiple relationships with distinct roles, and you would have to build logic, validation, and reporting layers manually. This increases technical debt and undermines the flexibility that the Party Model already provides out of the box.

Explanation:

In Salesforce Media Cloud with Advertising Sales Management (ASM), the View Insights button on the Add and Configure Placements screen is designed to pull analytical insights from Marketing Cloud Intelligence (formerly Datorama).

Marketing Cloud Intelligence is Salesforce’s integrated marketing analytics and reporting platform that aggregates data from various sources (ad servers, DSPs, CRMs, etc.).

The View Insights feature allows media planners to see historical performance, pacing, delivery metrics, and audience insights directly within the media planning workflow without leaving Media Cloud.

This integration helps optimize placement decisions based on real-time or near-real-time data.

❌ Why the others are incorrect:

A. Custom Ad Server
While a custom ad server can be integrated with Media Cloud (typically via API or Apex), the out-of-the-box View Insights button is not designed for custom ad servers. It specifically leverages Marketing Cloud Intelligence’s analytics layer.

B. Google Ad Manager (GAM)
Google Ad Manager is the supported ad serving system for trafficking and delivering ads, but the View Insights button pulls from Marketing Cloud Intelligence, not directly from GAM. GAM provides raw delivery data, but MCI processes and visualizes it for insights.

C. Tableau
Tableau is a powerful business intelligence tool that can integrate with Salesforce, but it is not the system powering the View Insights button inside Media Cloud’s placement configuration screen. That feature is specifically wired to Marketing Cloud Intelligence.

📘 Reference (Public Salesforce Documentation):
• Salesforce Media Cloud Help: “Marketing Cloud Intelligence Integration” — Explains that the View Insights button in ASM placements leverages Marketing Cloud Intelligence to show historical and predictive analytics.
• Trailhead: “Media Cloud Analytics with Marketing Cloud Intelligence” — Covers how Marketing Cloud Intelligence provides actionable insights within media planning.

Explanation:

Auth. Provider in Salesforce is used to set up authentication with an external service, such as Google, especially when OAuth 2.0 is involved.
➡️ Since the publishing company already has the client ID and secret from Google, this implies they are planning to use OAuth 2.0 to authenticate with Google's platform.
➡️ An Auth. Provider is the Salesforce configuration that allows you to define how Salesforce will connect to an external identity provider (like Google) using those credentials.
➡️ Once set up, it can be used in conjunction with Named Credentials or Apex code to authenticate requests.

❌ Incorrect Options Explained:

A. Named Credentials

➡️ Useful for storing endpoint URLs and authentication information to call external services.
➡️ However, it depends on an Auth. Provider when OAuth is used.
➡️ You create the Auth. Provider first, then use it in the Named Credential.
➡️ So this is not the first step—Auth. Provider is needed before this.

C. Connected App

➡️ Used when external apps need access to Salesforce, i.e., Salesforce is the provider of data.
➡️ In this case, Salesforce is the consumer, not the provider, of Google’s APIs.
➡️ So a Connected App is not relevant here.

D. Custom Metadata

➡️ Used to store configuration or business data like IDs, flags, or custom values.
➡️ Not used for secure authentication like client IDs and secrets.
➡️ So it's not appropriate for storing sensitive credentials or managing OAuth.

Explanation:

Marketing Cloud Intelligence (formerly known as Datorama) provides multiple integration methods to ingest and unify data from all available channels, including first-party and third-party data sources, to build a cross-channel optimization platform.

Here's a breakdown of each correct answer:

✅ A — API Connectors
API Connectors allow direct integration with third-party platforms (e.g., Google Ads, Facebook, Salesforce CRM) via their native APIs.
They enable automated, scheduled data pulls from hundreds of marketing and advertising platforms.
This is one of the most widely used methods for ingesting channel-specific data into Marketing Cloud Intelligence.

✅ C — TotalConnect
TotalConnect is a proprietary Marketing Cloud Intelligence technology that uses AI-powered data harmonization.
It can ingest data from virtually any source — even those without a native API connector — including flat files, custom data streams, and legacy platforms.
It maps and normalizes data automatically, making it ideal for integrating diverse and non-standard data sources.

✅ D — Marketing Cloud Intelligence Data Lake Stream
The Data Lake Stream enables ingestion of large-scale, raw data from cloud storage solutions (e.g., AWS S3, Azure Blob).

It supports first-party data ingestion at scale, making it ideal for enterprise-level cross-channel optimization.

It is especially useful when dealing with high-volume, structured/semi-structured data that needs to flow continuously into the platform.

❌ Why the Other Options Are Incorrect:

B — Data Raptor
Data Raptor is a Salesforce Industries (Vlocity) tool used for data transformation within OmniStudio. It is not a Marketing Cloud Intelligence integration method.

E — Data Mapping Visualizer
This is a feature within Marketing Cloud Intelligence used to visualize and manage data model mappings — it is a UI tool, not an integration/ingestion method.

📌 Reference:
Salesforce Marketing Cloud Intelligence (Datorama) – Data Integration Documentation
Salesforce Trailhead: Marketing Cloud Intelligence Data Ingestion Methods
Salesforce Media Cloud Accredited Professional (AP-217) Study Guide