Explanation:

In Salesforce Media Cloud and OmniStudio environments, each persona (such as Media Planner, Ad Ops, Sales Rep) needs a specific set of permission sets to access the functionality required for their role.

When we talk about types of permission sets required for a persona to be present in the environment, we are referring to the baseline permissions that enable them to:
Access the UI components and data objects (Media Cloud)
Use guided flows and integrations (OmniStudio)
Administer and modify configurations if applicable

Correct Permissions:

A. OmniStudioUser
Required for runtime access to OmniStudio components:
OmniScripts
DataRaptors
Integration Procedures
Almost every persona in ASM uses guided workflows, so this is essential.

C. OmniStudioAdmin
Grants access to design and configure OmniStudio components
Required for personas that modify OmniScripts or other OmniStudio artifacts
Needed to enable the persona's presence in environments where admin-level control is part of their role (e.g., consultants or solution designers)

D. Media Cloud Base User
This is a foundational permission set for all Media Cloud users
Grants access to core data models: Accounts, Campaigns, Orders, Media Plans, etc.
Required for any persona to function in the Media Cloud data model

Incorrect Permissions:

B. Rule Engine Runtime
Incorrect.
Used for Industry Rule Engine runtime evaluations, not required for every persona
Only needed if your implementation uses custom rules that must be executed dynamically

E. DocGenInd CME Designer User
Incorrect.
Related to Document Generation in Communications, Media & Energy (CME) industries
Not a core requirement for general Media Cloud personas unless document generation is explicitly used (e.g., contract PDFs)

Explanation:

When using Salesforce Media Cloud in conjunction with Google Ad Manager (GAM) for ad order orchestration, much of the order lifecycle — such as campaign creation, line item setup, and inventory booking — can be automated via integration. However, there are still manual steps required in GAM by the Media Planner, particularly when it comes to managing creatives, which are assets (images, videos, or HTML) that will be displayed in ads.

✅ A. Check if creatives are loaded in GAM
Before a campaign can go live, the Media Planner must verify that the correct creatives have been uploaded into GAM. While orders and line items may be pushed from Salesforce automatically, creative files are not always handled via API and must often be uploaded or verified manually.

✅ C. Associate the creatives to a line item in GAM
Even if creatives are uploaded, they need to be manually associated with the specific line items in GAM. This assignment tells GAM which creative should run for which ad slot. This is another step that typically requires manual action from the Media Planner.

❌ Incorrect Answers:

B. Create order in GAM
This step is typically automated when using Salesforce Media Cloud with GAM. Once a media plan is approved in Salesforce, the integration can automatically push the order to GAM via API, eliminating the need for manual order creation.

D. Check availability of inventory in GAM
Inventory checks (e.g., forecasting availability) can also be automated through API calls from Salesforce to GAM. The availability results can be displayed in Salesforce during the media planning process, so the Media Planner does not need to manually log into GAM for this step.

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:

In Salesforce Advertising Sales Management (ASM), managing the relationships between the publisher, the agency, and the end advertiser (the brand) requires a specific Account architecture to properly generate Media Proposals, contracts, and invoices.

Why C is correct:

• Home is the client/advertiser selling the products. In Salesforce, they should be created as a standard Account (typically using the Advertiser or Brand record type, depending on documentation nuance, or just a standard business account).

• Agents is the external media agency representing Home. ASM provides a dedicated Agency Account Record Type specifically designed for this purpose.

• Once both are created as Accounts, ASM uses the Account Relationship framework to link them, allowing the publisher to track that Agents is acting on behalf of Home on specific media plans. This ensures that media proposals can be billed to the agency while performance metrics are tied back to the brand.

Why A is incorrect:

Agents is explicitly stated to be the agency, not the brand. Assigning a Brand record type to the agency flips their business roles.

Why B is incorrect:

Account Record Types are critical in ASM to drive specialized business logic, page layouts, data validation rules, and automated workflows unique to the media buying ecosystem. Leaving them generic disables these features.

Why D is incorrect:

Agents is an independent business entity (an agency), not an individual employee or point of contact. Treating an entire agency as a single Contact record prevents proper business-to-business accounting, credit checks, and multi-user relationship tracking.

Salesforce Media Cloud Context & Reference

In the ASM standard data model, the Media Proposal object relies heavily on identifying both the Advertiser Account and the Agency Account:

[Media Proposal]
├── Advertiser Lookup ──> [Home Account]
└── Agency Lookup ──> [Agents Account (Agency Record Type)]

This structural separation ensures that when the proposal is converted into an order, the system knows exactly who is executing the campaign (the Agency) and whose inventory/products are being promoted (the Advertiser).

Explanation:

Salesforce Media Cloud's Advertising Sales Management (ASM) supports specific targeting capabilities for digital ad products. Out of the four options listed, only Geo Targeting is a natively supported targeting type within Media Cloud's standard offering.

✅ C — Geo Targeting (Correct)
Geo Targeting is a built-in, out-of-the-box targeting option within Salesforce Media Cloud's ASM module.
It allows Sales Representatives and Media Planners to define geographic parameters (e.g., country, region, city, DMA) when configuring digital ad products.
Geo Targeting is part of the standard targeting framework within Media Cloud's product catalog and order management capabilities.
It directly maps to the Ad Product configuration in the Media Cloud data model, making it a supported targeting selection during the sales and planning process.

❌ Why the Other Options Are Incorrect:

A. Content Targeting
While common in ad tech, Content Targeting is not part of Media Cloud's standard targeting model. It would require custom configuration or third-party integration.

B. Day/Time Targeting
Day-parting (Day/Time Targeting) is not included in Media Cloud's native targeting options out of the box. It may be handled by ad-serving platforms, but is not a standard Media Cloud targeting type.

D. User's OS Targeting
OS/Device Targeting is typically managed at the ad server level (e.g., Google Ad Manager), not within Salesforce Media Cloud's native targeting framework.

💡 Key Takeaway:
Salesforce Media Cloud's targeting capabilities are focused on high-level sales and planning targeting, with Geo Targeting being the primary supported type. More granular targeting options (like OS, day-parting, or content) are typically handled downstream by ad serving and trafficking platforms that integrate with Media Cloud.

📌 Reference:
• Salesforce Media Cloud Documentation: Ad Product Targeting Configuration
• Salesforce Industries: Advertising Sales Management (ASM) Data Model
• Salesforce Media Cloud Accredited Professional (AP-217) Study Guide