Explanation:

Media Cloud is a Salesforce Industry Cloud solution designed for media and publishing companies. Like other Salesforce Industry Cloud products (e.g., Communications Cloud, Financial Services Cloud), Media Cloud builds on the core Salesforce platform.

➡️ It uses Standard Salesforce Objects (such as Account, Contact, Opportunity, etc.) for fundamental CRM functionality.
➡️ It also introduces Custom Objects specific to media use cases, such as managing subscriptions, advertising sales, content rights, packages, etc.

Thus, Media Cloud uses both Standard and Custom Objects to deliver its functionality.

❌ Incorrect Options Explained:

B. It is composed exclusively of Custom Objects

🔹 Incorrect because Media Cloud extends the standard Salesforce data model, not replaces it.
🔹 Standard Objects like Account, Opportunity, and Order are still essential parts of the model.

C. It is composed exclusively of Standard Objects

🔹 Also incorrect.
🔹 While it relies on standard objects, custom objects are added to support media-specific business logic and data structures.

D. It is composed of Custom and Standard Objects with no extensions

🔹 Misleading.
🔹 Media Cloud does include extensions, such as custom fields, relationships, and metadata that extend standard objects for industry-specific purposes.

Explanation:

In Salesforce Media Cloud Advertising Sales Management (ASM), the most efficient and scalable approach for modeling digital advertising products (e.g., banners, video inserts) is to:

Use the Product Designer to define the product catalog

Associate products with Ad Space Specifications, which define where and how the ad will appear (e.g., placement type, dimensions, format)

This leverages Salesforce Industries’ powerful product modeling engine, including object types, attributes, and relationships, allowing for reusability, flexibility, and easy configuration of inventory.

Why Option B is Correct:

Product Designer allows structured product creation and classification
Ad Space Specification links the product to an ad placement (e.g., homepage top banner, pre-roll video)
This aligns with the standard ASM architecture and is designed for media product modeling

Why the other options are incorrect:

A. Create characteristics in Product object + use page layout Incorrect.
This is too manual and inefficient.
Page layouts are for UI, not meant for structured, scalable product modeling
Doesn’t utilize Ad Space Specification or object types

C. Configure an OmniScript to retrieve from GAM Incorrect.
GAM integration is for ad delivery and forecasting, not for core product catalog modeling Products should be modeled inside ASM first, even if GAM is used downstream

D. Create a custom object + link to Product2 Incorrect.
This adds unnecessary complexity and bypasses the built-in Industries Product Model
ASM is designed to be configured without needing to build custom objects for standard ad products

Explanation:

Salesforce Advertising Sales Management (ASM) includes a feature known as Self-Care, which is purpose-built to support self-service workflows for Advertisers and Agencies. This feature enables approved external users — such as small and medium businesses (SMBs) — to log into an Experience Cloud portal where they can create, submit, and track their own media plans, without relying on direct intervention from the Sales team.

This approach is ideal for companies targeting the SMB segment, where scaling human-led sales efforts is not feasible due to the volume of prospects. The Self-Care feature reduces sales overhead, empowers advertisers to work on their own timelines, and ensures data consistency by using the same underlying data model as internal Sales and Ad Ops teams. It also integrates with existing Salesforce processes for approvals, order generation, and campaign execution — streamlining the end-to-end sales process in a scalable, user-friendly way.

❌ Incorrect Answer:

A. Build an Experience Cloud with the Customer Service template for the Advertiser to navigate the product catalog and configure the products in the site.
While using Experience Cloud is a valid direction, the Customer Service template is designed for support-related interactions, not for media plan creation or ad sales workflows. It lacks the tailored features needed for media planning and would require significant customization to meet the use case. The better choice is to use the ASM Self-Care feature, which is built specifically for this purpose.

B. Set up Web-to-Lead and have the Advertiser/Agency submit their media plan through a website so the Sales team can later take ownership of the record and follow up to finalize the media plan.
This solution introduces manual effort and delays. While Web-to-Lead is a lightweight way to collect lead information, it doesn’t support interactive, multi-step workflows like configuring media plans, selecting products, or tracking approval status. It also increases the dependency on Sales teams to act as intermediaries — which is exactly what this solution aims to minimize when targeting the high-volume SMB segment.

C. Set up a public user, which anyone can use to create their own media plan, and provide their company information in the record detail.
Using a public user in this context is not secure or scalable. It violates standard authentication and security best practices, makes user tracking difficult, and lacks support for role-based access and record ownership. This approach also doesn’t offer personalization or accountability — both of which are important when dealing with customer-generated media plans and sensitive business information.

Explanation:

In Salesforce Media Cloud, media planners and sales teams typically use the system to plan campaigns, including forecasting revenue based on rate cards, impressions, and pricing models. However, actual delivery data (e.g., actual impressions and revenue) comes from the Ad Server, which tracks how the campaign performed once it went live.

Let's evaluate each option:

A. Planned revenue from Media Cloud and actuals from Ad Server ✅ Correct.
This is a common and realistic scenario:
Planned revenue is estimated in Media Cloud when the campaign is booked or proposed.
Actual revenue is calculated from Ad Server delivery data (e.g., actual impressions delivered, actual CPM or CPC).
This allows comparison of what was planned vs what was actually delivered.

B. Planned revenue and actuals from Media Cloud ✅
Also correct, if the Ad Server data is integrated into Media Cloud.
Media Cloud can store both planned and actual revenue if actuals are imported via integration from the Ad Server or a data lake.
Some organizations bring actual delivery data into Media Cloud for full lifecycle reporting.

Why Not Others?

C. Planned revenue from Ad Server and actuals from Media Cloud ❌ Incorrect.
The Ad Server does not handle planning — it's responsible for execution and measurement.
Media Cloud is the system where planning happens.

D. Planned revenue and actuals from Ad Server ❌ Incorrect.
The Ad Server does not handle planning. It only handles actuals and performance measurement.
Revenue planning tools and forecasting are not part of typical Ad Server capabilities.

Explanation:

In Media Cloud, especially when working with streaming packages and pricing configuration, the correct data model for tracking pricing configuration and changes involves:

✦ Product – Represents the streaming package or offering.
✦ Pricing Plan – Defines how the product is priced over time, including tiers, discounts, or promotional logic.
✦ Pricing Plan Step – Represents individual steps or components of the pricing logic (e.g., base price, discount, calculation steps).
✦ Price List – The set of prices applicable to a market, region, or customer segment. Tied to the product and pricing plans.

This combination allows you to trace changes in pricing over time and see what logic was applied, making it ideal for an audit report on price list changes.

❌ Incorrect Options Explained:

A. Product, Pricing Variable, Pricing Variable Binding

✦ These objects are used in dynamic pricing and rule-based calculations, not directly tied to auditing price list changes.
✦ More about inputs to pricing logic than the actual configured price outputs.

C. Product, Price Book, Price Book Entry, Price List

✦ This is the standard Salesforce Sales Cloud pricing model.
✦ Media Cloud uses Industry-specific pricing structures, like Pricing Plans, so this option doesn’t reflect the Media Cloud data model.

D. Product, Price List Entry, Pricing Element

✦ These may exist in some contexts but do not represent the full configuration and logic (like steps or dynamic rules).
✦ Missing the Pricing Plan and Plan Steps, which are essential to understanding how prices are configured.