Free Salesforce Media Cloud Practice Test Questions (2026)

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

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:

A Media Planner in Salesforce Media Cloud typically needs access to tools for designing media plans, managing campaign components, and interacting with runtime features. Here's why these three permission sets are essential:

OmniStudioUser: Grants access to OmniStudio tools like FlexCards and OmniScripts, which are used to build and manage guided user experiences—key for Media Planners working with dynamic interfaces.

MediaCloudPlus Runtime: Provides advanced runtime capabilities required for Advertising Sales Management (ASM) features, such as media plan configuration and placement management.

Media Cloud Base User: Offers foundational access to Media Cloud objects and data, enabling the user to interact with core media planning components.

Why Not the Others?

C. Rule Engine Runtime: Typically used for users managing business rules or logic flows. Not strictly required for Media Planners unless they’re involved in rule configuration.

D. MediaCloud Runtime: This is a more general runtime permission set, but MediaCloudPlus Runtime includes its capabilities and more—making it the better fit.

Explanation:

The IDX Build Tool is the recommended solution for automating CI/CD workflows involving OmniStudio DataPacks and Salesforce metadata. It is a command-line interface (CLI) tool designed specifically for:

Automating the packaging and deployment of OmniStudio components (like OmniScripts, FlexCards, DataRaptors)
Supporting source control integration (e.g., Git)
Enabling automated pipelines for development, testing, and production environments

This makes it ideal for teams working in distributed developer orgs and needing to promote changes through sandboxes to production.

Why Not the Others?

B. IDX Workbench: A desktop application used for manual migrations. It’s great for one-off or small-scale deployments but not suitable for automation in CI/CD pipelines.

C. Backup and Restore Automation: This is used for data recovery, not for migrating metadata or OmniStudio components.

D. Data Loader: A tool for data import/export, not for handling OmniStudio DataPacks or metadata deployment.

Explanation:

When implementing Salesforce Industries Order Management (OM)—especially in Media Cloud—it's important to orchestrate order fulfillment steps across multiple systems such as inventory, billing, and ad servers. Salesforce recommends using orchestration plan definitions that align with modularity, flexibility, and maintainability.

Let’s evaluate the options:

C. Create a master end-to-end plan to sequence the major milestones of all orders.
Correct.
This is a Salesforce best practice: to define a master orchestration plan that sequences high-level order lifecycle stages (e.g., reserve inventory, assign ad placements, bill customer).
This plan ensures coordination of steps across fulfillment subplans and external systems.

D. Create separate orchestration plan definitions for provisioning, logistics, inventory, and/or billing Correct.
Modular orchestration allows for reuse and better maintainability.
Each fulfillment area (e.g., ad placement, billing, reporting) can have its own swim lane and orchestration plan definition, making the system easier to manage and extend.

A. Fully describe all Commercial product entities using product attributes
Incorrect.
While product modeling is important, orchestration planning focuses on how to fulfill orders, not on how to describe products.
This guideline is more relevant to product catalog setup, not orchestration design.

B. Use a single swim lane or orchestration plan for all callouts to all external systems
Incorrect.
Using a single swim lane for all callouts reduces flexibility, violates separation of concerns, and makes orchestration harder to maintain.
Best practice is to separate them based on functional areas (e.g., provisioning, billing).

Explanation:

When designing orchestration plans in Salesforce Industries Order Management, the goal is to create modular, scalable, and maintainable workflows that reflect the complexity of real-world fulfillment systems. Here's why C and D are the best choices:

C. Create a master end-to-end plan to sequence the major milestones of all orders
This is a Salesforce-recommended best practice.
It ensures that the orchestration process captures the full lifecycle of an order—from initiation to completion.
Helps in tracking progress, managing dependencies, and ensuring that all fulfillment steps are executed in the correct sequence.

D. Create separate orchestration plan definitions for provisioning, logistics, inventory, and/or billing
This promotes separation of concerns and modularity.
Each external system (e.g., billing, inventory) can be managed independently, making it easier to maintain and update orchestration logic.
It also allows for parallel processing where appropriate, improving efficiency.

Why Not the Others?

A. Fully describe all Commercial product entities using product attributes
While important for product modeling, this is not directly related to orchestration plan design.

B. Use a single swim lane or orchestration plan for all callouts to all external systems
This goes against best practices. It creates a monolithic and hard-to-maintain orchestration structure.
Salesforce recommends using multiple swimlanes, each representing a different external system or function2.

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:
In Salesforce Media Cloud (built on Salesforce Industries/Vlocity), when modeling Digital Advertising products that share common characteristics, the most efficient and scalable approach is to:

Define a Product Object Type (also known as Product Specification Type)
Assign Attributes (e.g., size, duration, format, placement)
Use that Object Type to create multiple products that inherit these shared attributes

This setup allows for consistency, reuse, and easier product catalog management, especially when dealing with a large volume of products with similar characteristics.

Why Option B is Correct:

Object Types define a template or structure for a category of products.
Attributes are reusable and can be shared across multiple products.
It enables product managers to manage products efficiently and ensure data consistency.
This approach aligns with Salesforce Industries’ product modeling best practices.

Let’s eliminate the incorrect options:

A. Use a Product Family for those products (Incorrect)
Product Families are used primarily for reporting and UI grouping, not for defining shared structure or characteristics.
They don’t carry shared attributes or behavior.

C. Use a Standalone Product and add Attributes (Incorrect)
While you can create a standalone product and add attributes, doing so for each product individually is not efficient when managing many products.
This approach leads to redundancy and higher maintenance effort.

D. Clone an existing ad product and assign Attributes (Incorrect)
Cloning is manual and inefficient, especially at scale.
Any changes to shared characteristics would need to be manually replicated across cloned products.

Explanation:

This setup leverages Salesforce’s native record-level security model:

OWD = Private ensures that Sales Reps only see their own Opportunities, which satisfies the first requirement.
Role Hierarchy automatically grants Managers access to records owned by users beneath them in the hierarchy—perfect for reporting and oversight.

This approach is scalable, declarative, and aligns with Salesforce best practices for data visibility.

Why Not the Others?

A. Use sharing rules → Unnecessary here. Role hierarchy already provides the required access. Sharing rules would add complexity without benefit.

C. OWD = Public → This would expose all Opportunities to all users, violating the requirement that Sales Reps should only see their own.

D. Apex Sharing → Overkill. Apex should be used only when declarative options (like role hierarchy) can’t meet the need.

Explanation:
Before testing the Google Ad Manager (GAM) integration with Advertising Sales Management (ASM) in Salesforce Media Cloud, the Consultant must ensure that the system is securely and properly configured to communicate with GAM. Here's why A and D are the right choices:

A. Create a new Named Credential to store the GAM endpoint
Named Credentials are used in Salesforce to securely store external service endpoints and authentication details.
This is essential for authenticated callouts to GAM APIs.
It simplifies integration by abstracting authentication logic from Apex or OmniStudio components.

D. Add the GAM URL as a new CSP Trusted Site
Salesforce enforces Content Security Policy (CSP) to prevent unauthorized external access.
To allow callouts or embedded content from GAM, its URL must be added to the CSP Trusted Sites list.
Without this, Salesforce may block requests to GAM during testing or runtime.

Why Not the Others?

B. Add the GAM endpoint in the OmniStudio Integration Procedure → While the Integration Procedure may reference the endpoint, it should leverage the Named Credential instead of hardcoding URLs. This ensures security and maintainability.

C. Create a new Auth. Provider that specifies the Consumer Key and Consumer Secret from GAM → GAM typically uses OAuth 2.0 credentials, but these are stored within the Named Credential, not a separate Auth. Provider in this context.