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:

A) Named Credential
A Named Credential in Salesforce is used to securely store and manage authentication details for external service callouts, including the callout URL and authentication settings (e.g., OAuth, Basic Authentication). In the context of Salesforce Media Cloud integrating with Google Ad Manager, a Named Credential is the appropriate component to specify the callout URL for the Google Ad Manager API endpoint (e.g., https://ads.google.com/apis/ads/publisher).

Named Credentials simplify the process by:

Storing the endpoint URL for the Google Ad Manager API.
Managing authentication details, such as OAuth 2.0 tokens or API keys, required for secure communication.
Allowing Media Cloud’s integration processes (e.g., OmniStudio Integration Procedures or Apex callouts) to reference the Named Credential without hardcoding sensitive information.

For Cloud Kicks, the consultant would create a Named Credential to define the Google Ad Manager API URL and configure authentication (likely OAuth 2.0, given Google’s API standards), enabling Media Cloud to send order data (e.g., ad campaign details from Contract Line Items) securely to Google Ad Manager. This ensures seamless integration and compliance with Salesforce security best practices.

Incorrect Options:

B) Connected App
A Connected App is used to integrate external applications with Salesforce, allowing them to access Salesforce data via APIs (e.g., a third-party app accessing Salesforce via OAuth). In this scenario, Cloud Kicks needs to send data from Salesforce Media Cloud to Google Ad Manager, not the other way around. A Connected App would be relevant if Google Ad Manager were initiating access to Salesforce data, but for specifying a callout URL to an external service, a Connected App is not required. Instead, a Named Credential handles the outbound integration, making this option incorrect.

C) Custom Metadata
Custom Metadata is used to store customizable, application-specific metadata that can be deployed and queried, such as configuration settings or mappings. While Custom Metadata could theoretically store a URL as a text field, it is not the standard or secure method for specifying callout URLs in Salesforce. Custom Metadata does not inherently support authentication management or secure callout handling, which are critical for integrating with Google Ad Manager. Named Credentials are specifically designed for this purpose, providing both URL specification and secure authentication, so this option is incorrect.

D) Auth. Provider
An Auth. Provider (Authentication Provider) is used to configure single sign-on (SSO) or OAuth-based authentication for external identity providers (e.g., Google, Salesforce) to allow users to log into Salesforce or enable external apps to authenticate with Salesforce. While an Auth. Provider might be used in conjunction with a Named Credential to define OAuth settings for Google Ad Manager, it does not directly specify the callout URL. The Named Credential encapsulates both the URL and the authentication configuration (referencing the Auth. Provider if needed), making the Named Credential the primary component required, not the Auth. Provider alone. This option is incorrect because it does not fully address the requirement of specifying the callout URL.

Reference:
Salesforce Help: “Named Credentials”
Salesforce Media Cloud Documentation: “Google Ad Manager Integration”
Trailhead: “Media Cloud Basics” module
Salesforce Developer Guide: “External Services and Named Credentials”

Explanation:

In Salesforce Media Cloud, media planning supports multiple channels, but only certain media types are available out-of-the-box (OOTB) for structured media planning.

✅ B. Linear — Correct
Represents traditional broadcast media such as:

• TV
• Radio

Fully supported in Media Cloud’s native media planning model.
Includes scheduled, time-based ad placements.

✅ C. Digital — Correct
Represents online advertising such as:

• Display ads
• Social ads
• Programmatic campaigns

Core OOTB media type in Media Cloud.
Fully integrated into media planning and execution workflows.

❌ Why the other options are incorrect:

Event ❌
Not an OOTB media type in Media Cloud planning.
Events are typically handled via custom objects or industry-specific extensions.

Print ❌
Not included as a native OOTB planning media type.
Can be modeled, but not standard in the core media planning schema.

Key Exam Insight:
Salesforce Media Cloud natively focuses on:

• Digital
• Linear

Other media types (like print and event) are generally modeled through extensions or custom configurations, not core planning objects.

Explanation:

In Salesforce, an Approval Process can be set up on standard or custom objects, including the Quote object. Since the business requirement states that a Sales Executive creates a quote, and the submission for approval must be triggered when the Quote status changes to "Client Approved," the most direct and maintainable solution is to create an Approval Process on the Quote object itself.

Salesforce supports assigning a Queue as an Approver — this means any member of the queue can respond to the approval request, which suits scenarios where a group (not an individual) needs to manage approvals. This aligns exactly with the requirement of routing the approval to a queue.

To automate the approval submission when the status changes to “Client Approved,” you can use a Flow or Process Builder to monitor the status field and auto-submit the record into the approval process when the criteria are met. This avoids requiring the Sales Executive to manually submit the quote.

Using the Quote directly avoids unnecessary indirection or complexity, keeps the approval process focused on the relevant object, and leverages standard Salesforce features.

❌ Incorrect Answer:

A. Invoke Approval Process created on individual QuoteLineItem and keep Queue as Approver.
This is not valid because Approval Processes cannot be created on Quote Line Items, as they are a child object of the Quote and not intended to drive approval processes. Additionally, approvals typically occur at the Quote level, not for each individual line item, as that would create fragmented and redundant workflows.

B. Invoke Approval Process created on Opportunity linked to the Quote and keep Queue as Approver.
While Opportunities can have Approval Processes, the requirement is specifically tied to the Quote status reaching “Client Approved.” Linking this logic to the Opportunity instead of the Quote would create a misalignment between business logic and data structure, and would also require complex automation to keep Quote and Opportunity statuses in sync — introducing risk and maintenance overhead.

C. Invoke Approval Process created on a custom object having lookup to Quote and keep Queue as Approver.
This option introduces unnecessary complexity by requiring the creation of a custom object to serve as a proxy for the approval. Since the requirement is already fully addressable using the standard Quote object, adding a custom object only complicates the model, reduces clarity, and increases the maintenance burden — without adding any functional benefit.

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.