Salesforce-Revenue-Cloud-Consultant Practice Test Questions

Summary:
The requirement is to introduce a timed, conditional delay between two fulfillment steps (hardware delivery and software provisioning). This is a scheduling feature within the orchestration plan. The specific capability to configure a future start date for a task step is controlled by a global DRO setting. If this setting is not enabled, the option to set the delay will not be visible on the task configuration screen, preventing the designer from implementing the business requirement.

Correct Option:

A: Future-Dated Steps in the DRO settings:
This is the correct action. The "Future-Dated Steps" setting is a master switch in the DRO configuration that, when enabled, allows a Fulfillment Designer to define a specific start date and time for a task step. This is the direct feature needed to create the 2-day delay after the preceding hardware delivery step is completed.

Incorrect Option:

B: Modify All Data permission in the Fulfillment Designer's profile:
While a Fulfillment Designer needs appropriate permissions, "Modify All Data" is an overly broad system-level permission that is not required to see a specific configuration option on a DRO task. The visibility of the "Future-Dated" option is controlled by the DRO-specific setting, not by object-level CRUD permissions.

C: Link Task to Step Source button in the DRO settings:
This is not a standard DRO setting or button. The "Step Source" is a field on a task that defines the record (like a Work Order Line Item) it operates on. There is no global "Link Task to Step Source" setting that controls the visibility of scheduling options.

Reference:
Salesforce Help: Configure Dynamic Revenue Orchestrator - The official documentation for enabling DRO features includes "Future-Dated Steps" as a configuration option. Enabling this setting makes the scheduling fields available on the task definition, allowing for the creation of delayed steps.

Summary:
The primary business goal is omni-channel selling, which requires connecting a third-party e-commerce website to the Revenue Cloud data model (Products, Quotes, Orders) seamlessly. This is a classic integration scenario. While flows and Apex can be used for internal automation, the core challenge is building a secure, scalable, and real-time connection between two separate systems, which is fundamentally an API-based integration task.

Correct Option:

A: Expertise in Salesforce Integration, including REST APIs:
This is the most critical skill set. Enabling a third-party website to create and manage sales data in Salesforce requires building and exposing REST APIs. The business analysts would define the data contracts, and the administrators would help with security and object modeling, but the implementation hinges on experts who can design, build, and secure these system-to-system integrations.

Incorrect Option:

B: Expertise in Salesforce flows:
Flows are powerful for automating internal business processes within the Salesforce platform, such as quote approval or fulfillment orchestration. They are not the primary tool for building the external-facing APIs needed for a third-party website to interact with Salesforce.

C:Expertise in Apex and Lightning Web Component development:
Apex and LWC are used for building custom user interfaces and business logic within the Salesforce UI. While Apex can be used to create custom API endpoints, the core skill required here is broader "integration" knowledge, including API design, security, and best practices for connecting disparate systems, which encompasses but is not limited to just Apex coding.

Reference:
Salesforce Architect: Integration - The Salesforce Integration capabilities documentation emphasizes the use of REST APIs for building connected experiences and enabling B2C commerce, which is the foundational capability for the described omni-channel use case.

Summary:
The user has the correct data-level permissions (to view and amend records) but cannot see the assets on the Account page layout. This indicates a user interface (UI) configuration issue, not a data access problem. In Salesforce, even if a user has access to records, they must have a UI component, like a related list or a Lightning component, added to the page layout to view and interact with those records from a specific page.

Correct Option:

A: The Managed Asset Viewer component and the Asset related list are missing from the Account page layout.
This is the most direct and likely cause. The Asset related list is the standard out-of-the-box component for displaying assets on an account. The Managed Asset Viewer is a common component for asset management actions. If these are not present on the page layout the user is viewing, the assets will be functionally invisible from that page, despite the user's permissions.

Incorrect Option:

B: The asset records have expired and, as a result, are no longer displayed on the Account page.
Expired assets are typically still visible on the account; their status is simply set to "Expired." The problem states the user cannot see the assets at all, which is a visibility issue, not a status-based filtering issue.

C: The consultant needs to set up the Amend, Renew, and Cancel flow to allow amendments and renewals.
This configuration is necessary to define the actions a user can take on an asset (like amending it), but it does not control the initial visibility of the asset records on the Account page. The user should still be able to see the assets even if this flow isn't fully configured.

Reference:
Salesforce Help: Customize Page Layouts - The official documentation explains that page layouts control which fields and related lists users can see on a record's detail page. The Asset related list must be added to the Account page layout for users to see assets from that context.

Summary:
Contracts AI extracts clauses and field data from contract documents using Contract Extraction Templates. These templates determine which fields, clauses, and metadata are pulled from uploaded PDFs. If a new custom field—such as Payment Method—needs to be included after the first extraction, the consultant must update the extraction template so the AI engine knows to look for and map this new field. Only modifying the extraction template enables AI to retrieve it on subsequent runs.

Correct Option:

A — Modify the contract extraction template to define the attribute mapping and context mapping for payment method
Contract extraction templates are the core configuration layer for Contracts AI. They control which fields are extracted, how values are mapped, and what contextual rules guide the extraction. By adding the new custom field to the template’s attribute mapping and context mapping, AI will identify and extract the field from the PDF. This is the correct and supported method for updating extraction requirements.

Incorrect Option:

B — Modify the AI prompt template
AI prompt templates control the language and structure used when presenting extracted clause summaries or generating contract intelligence, not the extraction rules themselves. Prompt templates do not define field mappings or determine which custom fields Contracts AI retrieves from documents. Changing the prompt would not enable extraction of the payment method field.

C — Log a support case with Salesforce
Salesforce support is not required to add new fields to Contract Extraction Templates. The consultant has full admin-level capability to update extraction templates directly in the Contracts AI settings. This option would be unnecessary and would not provide any configuration benefit, as custom fields are meant to be self-managed in templates.

Reference:
Salesforce CLM & Contracts AI Documentation → Contract Extraction Templates, Attribute Mapping & Context Mapping for Field Extraction.

Summary:
The Transaction Line Editor (TLE), used for creating and managing quotes, orders, and invoices, is designed for efficiency in a high-volume data entry environment. A key capability is allowing users to quickly narrow down a long list of line items to find specific products or review certain entries. This is achieved through its built-in filtering functionality, which is a core feature for navigating complex transactions.

Correct Option:

B: Filtering:
This is the correct capability. The TLE provides a filter button that allows users to display only the line items that meet specific criteria (e.g., a certain product name, a specific start date). This is essential for managing large transactions and is a standard, well-documented feature of the TLE interface.

Incorrect Option:

A: Drag to Sort:
The TLE does not support manually reordering line items by dragging them. The sort order is typically controlled by system-defined sequences (like the order of addition) or by using the standard column header sorting (e.g., clicking the "Product Name" header), not by drag-and-drop interactions.

C: Auto Save Changes:
The TLE does not automatically save changes as you type. Users must explicitly save the transaction (e.g., by clicking a "Save" or "Quick Save" button) to persist their edits. This prevents unintended changes from being saved and allows users to review modifications before committing.

Reference:
Salesforce Help: Use the Transaction Line Editor - The official documentation explicitly lists "Filter line items" as a key action, describing how users can "filter the line items in the transaction" to find the information they need.

Summary:
To build CLM document templates that include clauses, Salesforce requires specific permissions related to document generation and template editing. The consultant already has DocGen Designer and Clause Designer User, which allow clause creation and basic document template editing. However, because Salesforce CLM uses Microsoft Word Online for advanced template editing — including clause insertion — the consultant must also have the Microsoft 365 Word Designer permission set to work with the template in Word Online.

Correct Option:

C — Microsoft 365 Word Designer
This permission set allows users to open, edit, and design contract templates directly in Microsoft Word Online, which is required for inserting clauses into an MSA document template. It activates the CLM integration with Microsoft 365 so the consultant can add clause placeholders, dynamic fields, and formatting. Without this permission, the template cannot be opened in the Word-based editor where clause design work is performed.

Incorrect Option:

A — OmniStudio Admin
OmniStudio Admin is unrelated to CLM document design. It provides access to OmniStudio tools such as DataRaptors, FlexCards, and Integration Procedures. These tools do not influence document template creation, clause insertion, or CLM Word-based editing. Therefore, this permission does not help with building an MSA template.

B — Obligation Assignee
This permission set is used for the obligations management component in CLM, allowing users to be assigned or track contractual obligations. It has no function related to document template design, clause editing, or Word Online access. Assigning this permission would not enable the consultant to begin building the MSA template.

Reference:
Salesforce CLM Documentation → Document Templates, Microsoft 365 Word Integration, Required Permission Sets for Template & Clause Design.

Summary:
Adding a new product to an existing bundle in Product Catalog Management does not automatically add it to the pre-existing constraint model. The constraint model, defined in Constraint Modeling Language (CML), operates independently. To include the new product in the bundle's compatibility rules, the product designer must first define the new product as a "type" within the CML model and then synchronize the bundle structure from the product catalog to create the association between the logical type and the physical product.

Correct Option:

C: Create a new type for the child product in the Constraint Modeling Language (CML) Editor, then import the associations for the type from Product Catalog Management.
This is the correct two-step process. First, the new product must be declared as a type within the CML code of the constraint model. Second, the "Import Associations" action must be performed to link this newly defined CML type to the actual product that was added to the bundle in the product catalog, thereby enforcing constraints on it.

Incorrect Option:

A: Use the Visual Builder to add the child product to the constraint model, then import the associations for the type from Product Catalog Management.
The Visual Builder is an alternative tool for creating a constraint model visually. However, for an existing model that is already written in CML, the modification must be made directly within the CML Editor, not the Visual Builder.

B: Once a bundle is updated in Product Catalog Management, create a constraint model, then import the associations from Product Catalog Management.
This is incorrect because a constraint model already exists and is in use. The designer should not create a new model, as this would overwrite the existing rules. The correct action is to modify the existing constraint model.

Reference:
Salesforce Help: Add a Product to a Constraint Model - The official documentation outlines the process of adding a new product to an existing CML-based model, which involves defining the new type in the CML editor and then using the "Import Associations" action to synchronize the product catalog structure.

Summary:
When a discount is calculated at the quote or order level, Salesforce Pricing needs a mechanism to distribute that discount evenly across all individual line items. Without a specific distribution step, the discount remains at the header level and does not adjust each product’s net price. Salesforce provides a dedicated pricing engine element called Discount Distribution Service, which must be placed at the end of the pricing procedure to allocate the discount proportionally or evenly across all lines.

Correct Option:

C — Add and configure the Discount Distribution Service element as the last step of the pricing procedure
The Discount Distribution Service is explicitly designed to distribute header-level discounts across all line items. When configured as the final step, it takes the overall discount amount and spreads it evenly or proportionally based on business logic. This ensures consistent pricing, accurate extended amounts, and correct tax calculations. It is the official and recommended approach for distributing calculated discounts among line items.

Incorrect Option:

A — Add Formula Based Pricing with ItemTotalPrice context tag
Formula Based Pricing helps calculate custom prices or discounts, but it does not distribute discounts automatically across line items. Adding a formula with ItemTotalPrice would only compute values, not spread them. It can modify individual line prices but cannot allocate a quote-level discount across all lines, making it insufficient for the requirement.

B — Add Aggregate Price element with SUM function
Aggregate Price elements calculate totals across groups of line items, often used for tiered pricing or bundle pricing. A SUM function can aggregate values but cannot distribute discounts back downward to individual lines. This option would compute a total but would not break it into proportional line-level discounts, so it does not fulfill the requirement.

Reference:
Salesforce Pricing Guidance → Discount Distribution Service, Pricing Procedures and Elements, Header-to-Line Discount Allocation Best Practices.

Summary:
The Product Discovery (Browse Catalog) experience is driven by a specific, configurable flow. Simply activating an updated version of this flow is not enough to put it into use. The system needs to be explicitly told which flow to run. This is done by specifying the active flow's name in the Product Discovery settings, which acts as the pointer for the guided selling interface.

Correct Option:

B: Adding the Flow Name in the Product Discovery Setup.
This is the critical missed step. The Product Discovery Setup page contains a field to specify the "Browse Products Flow." After creating and activating a new or modified flow, its API name must be entered into this setup area to direct the system to use it. Without this reference, the interface will continue to use the previously configured flow.

Incorrect Option:

A: Adding the Flow Name in the Pricing Settings Setup.
This setup area is for defining pricing procedures, price books, and other pricing-related configurations. It does not control the flow used for browsing the product catalog.

C: Adding the Flow Name in the Revenue Settings Setup.
This is not a standard setup menu in Revenue Cloud. The central location for configuring the guided selling experience, including the browse flow, is the dedicated "Product Discovery Setup."

Reference:
Salesforce Help: Set Up Product Discovery - The official documentation outlines the setup steps, which include specifying the "Browse Products Flow" in the Product Discovery settings to determine which flow is used to display the product catalog to users.

Summary:
The company wants sales reps to trigger subscription renewals directly from a record page with a single click. Revenue Cloud provides an out-of-the-box invocable action called InitiateRenewal, which can be used inside a screen flow. When this flow is exposed as a quick action, reps can easily generate renewal opportunities, quotes, and related assets without relying on backend automation or code. This is the standard and recommended approach for user-initiated renewals.

Correct Option:

B — A screen flow using the InitiateRenewal invocable action exposed as a quick action
The InitiateRenewal invocable action is specifically built to start the renewal lifecycle from Active Assets, Contracts, or Accounts. By placing this inside a simple screen flow, the consultant can create a seamless “Renew Now” button. Exposing the flow as a quick action on Account or Contract pages allows sales reps to initiate renewals instantly with one click. This method uses declarative tools, requires no code, and directly supports Revenue Cloud renewal logic.

Incorrect Option:

A — Apex trigger on Contract to clone the contract and assets
An Apex trigger is unnecessary and not recommended because Salesforce already provides declarative renewal functionality. Coding contract cloning manually introduces complexity, maintenance risk, and potential conflicts with CPQ’s renewal engine. It would also not guarantee correct creation of renewal opportunities, quotes, or subscription mappings the way the InitiateRenewal action does.

C — A custom Renewal checkbox on Asset triggering Process Builder
This approach is not aligned with Salesforce CPQ renewal best practices. Checking a box on the Asset object does not natively create renewal opportunities or renewal quotes. Process Builder also cannot properly replicate CPQ’s structured renewal logic. This solution would be unreliable, incomplete, and lacks support for automated mapping of subscription products in the renewal lifecycle.

Reference:
Salesforce Revenue Cloud Documentation → InitiateRenewal Invocable Action, Renewal Automation Using Flows, Subscription Lifecycle Management.