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:

To empower sales teams with real-time digital delivery performance insights directly on the Salesforce account page, the most efficient and scalable solution is:

CRM Analytics (formerly Einstein Analytics):
Salesforce’s native analytics platform that supports custom dashboards, record-level filtering, and embedded visualizations.

Ad Delivery Connector:
A prebuilt integration that pulls ad server delivery data (e.g., impressions, clicks, spend) into Salesforce objects like Ad Delivery, enabling CRM Analytics to visualize this data.

By embedding a CRM Analytics dashboard on the account page, sales reps can:
View delivery performance specific to each advertiser or agency
Use filters and dynamic views tailored to the publisher’s business logic
Avoid switching between systems or relying on external BI tools

Why Not the Others?

A. Tableau with BigQuery/Snowflake → While powerful, this setup is external to Salesforce and requires complex integration. CRM Analytics is preferred for native embedding and real-time access.

C. FlexCards with Marketing Cloud Intelligence → FlexCards are UI components, not analytics dashboards. Marketing Cloud Intelligence focuses on marketing campaign data, not ad delivery performance.

D. Integration Procedures with report chart → This approach is manual and limited in visualization capabilities. CRM Analytics offers interactive dashboards, better suited for this use case.

Explanation:

Before upgrading Advertising Sales Management (ASM) in a Media Cloud org, it’s critical to preserve any customizations or modifications made to the existing (older) ASM components. These could include:

Custom FlexCards, OmniScripts, or Lightning Web Components
Modified DataRaptors, Integration Procedures, or custom fields
Any overridden logic or UI elements

Upgrading ASM may overwrite or conflict with these customizations, so backing them up ensures you can restore or reapply them if needed.

Why Not the Others?

A. Take a backup of any newer ASM components → This doesn’t make sense before migration, since the newer components haven’t been installed yet.

B. Customize or modify the newer ASM components → You should never modify new components before validating the upgrade. Always test in a sandbox first.

D. Activate Custom Lightning Web Components and FlexCards → Activation comes after migration and testing, not before.

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:

OmniScript Definitions:
These are declarative, reusable interaction flows used to create guided experiences. They are packaged as part of the managed package to ensure consistent deployment across environments.

CPQ APIs:
APIs that support Configure, Price, and Quote (CPQ) functionalities are essential for media sales processes and are delivered via the managed package for extensibility and integration purposes.

Apex Classes:
Custom server-side business logic and utility functions are implemented using Apex. Managed packages typically include Apex classes to support backend processes.

Lightning Web Components (LWC):
LWCs are modern Salesforce UI components built using the latest web standards. They are included in the managed package to provide flexible, performant, and customizable user interfaces.

Incorrect Options:

Option A: FlexiPages, Custom Labels, Vlocity Integration Settings, Custom Layouts
While FlexiPages and Custom Labels might be included for UI configuration and localization, they are not core functional assets like APIs, OmniScripts, or LWCs. Vlocity Integration Settings and Custom Layouts are more likely environment-specific configurations and not standard deliverables in the core managed package.

Option C: OmniScript Definitions, CPQ APIs, FlexiPages, Custom Labels
Although OmniScripts and CPQ APIs are correct, FlexiPages and Custom Labels are not primary functional deliverables but rather configuration metadata supporting UI customization and localization.

Option D: FlexiPages, Custom Labels, Data Model, Media Service
The Data Model and Media Service are foundational parts of Media Cloud but are typically part of the platform metadata and service configurations, not deployed as managed package components directly. FlexiPages and Custom Labels again fall under UI configuration, not core functional components.

Reference:
Salesforce Industries Documentation
Salesforce Media Cloud Overview
OmniStudio Admin Guide (Salesforce)
Salesforce CPQ API Reference