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, 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 Advertising Sales Management (ASM), the Industries Order Management (OM) orchestration plan follows a structured sequence to ensure that all fulfillment steps are executed in the correct order. Here's how it flows:

Create Order
The orchestration begins with the creation of the parent order that encapsulates the overall transaction.

Create Line Items
Next, line items (representing individual ad placements or products) are added to the order.

Approve Order
Once the order and its line items are configured, it goes through an approval process to validate pricing, availability, and compliance.

Activate Order
After approval, the order is activated, triggering downstream fulfillment processes like inventory reservation and billing.

Add Creative
Finally, creative assets (e.g., banners, videos) are attached to the order for delivery. This sequence ensures that the order is fully structured and validated before any creative content is assigned, aligning with best practices for fulfillment and campaign execution.

Explanation:

✅ A. Tableau

⭐ Tableau is a Salesforce-owned business intelligence platform that allows users to create rich, interactive visualizations and analyze large historical datasets.
⭐ It is especially effective for trend analysis over multiple years, such as comparing ad inventory performance each June over the last five years.
⭐ You can pull in data from ASM, correlate it with other sources, and generate dashboards and forecasts to guide sales strategy.

✅ D. CRM Analytics (formerly Einstein Analytics)

⭐ CRM Analytics is a native Salesforce analytics tool tightly integrated with Media Cloud and other Salesforce apps.
⭐ It provides prebuilt templates, predictive models, and the ability to combine historical data with current pipeline metrics.
⭐ Useful for sales cycle insights, inventory forecasting, and decision-making support for advertising campaigns.

❌ Incorrect Options Explained:

B. Ad Manager

🔻 Google Ad Manager is an external ad serving and monetization platform, not a Salesforce reporting tool.
🔻 While data can be pulled from Ad Manager into Salesforce, it is not a Salesforce reporting component and does not fulfill the role of building custom performance trend analysis reports directly.

C. Marketing Cloud Intelligence (formerly Datorama)

🔻 While powerful for marketing performance analytics, it is focused on cross-channel marketing campaign data like impressions, clicks, conversions — not typically ad inventory sales from ASM.
🔻 It is not optimized for sales-driven metrics and inventory trends tied to Media Cloud ASM unless extensively customized.

Explanation:

🟢 A. QuoteGroup
QuoteGroup is the out-of-the-box custom object designed to represent sub-deals or line-level deal groups in Media Cloud and Salesforce Industries CPQ.
It allows tracking of specific details for each sub-deal, such as amounts, dates, and other relevant financial or timing attributes.
It essentially helps segment the main deal or quote into multiple logical components (sub-deals) for reporting and management purposes.

❌ Incorrect Options

🔴 B. QuotePricingAdjustment
Represents discounts, markups, or adjustments applied to a quote or quote line item.
Not used to track sub-deal structures themselves.

🔴 C. QuoteMember
Typically relates to members associated with the quote, often representing individuals or accounts involved in the quoting process.
Does not represent financial sub-deals or their transactional details.

🔴 D. QuoteProductRollup
Used for aggregating product-level information within a quote, such as totals for related line items.
Not intended to represent distinct sub-deals.

📚 Reference
Salesforce Industries CPQ Data Model Guide
Salesforce Media Cloud CPQ Documentation