Salesforce Updated Rev-Con-201 Exam Questions and Answers by liana

Comprehensive and Detailed Explanation From Exact Extract:

Revenue Cloud’s document generation (DocGen) capabilities for Revenue Lifecycle Management leverage Microsoft Word as the template and clause authoring environment via an add-in. Salesforce provides a dedicated permission set for users who need to actually design and edit templates in Microsoft Word.

The documentation for DocGen and template design describes a permission set similar to:

Microsoft 365 Word Designer

Assign this permission set to users who design and edit document templates using the Microsoft 365 Word add-in for Revenue Lifecycle Management. This permission set enables access to the Word-based template designer experience.

The DocGen Designer permission set allows the user to manage document packages, configurations, and related document-generation assets within Salesforce. The Clause Designer User permission set allows management and usage of clauses, including organizing and inserting them into templates. However, to open Microsoft Word and actually build/edit the Master Subscription Agreement (MSA) document template with clauses, the consultant must also have Microsoft 365 Word Designer.

Why the other options are incorrect:

Option A – OmniStudio AdminThis permission set is related to OmniStudio tools (FlexCards, OmniScripts, etc.), which are not required to build Word-based DocGen templates. It’s not referenced as a requirement in the Revenue Cloud / RLM DocGen template design flow.

Option B – Obligation AssigneeObligation-related permission sets are used to manage obligations and related tasks (for example, tracking contractual obligations, assignments, or approvals). They are not required just to design or edit a document template with clauses. The documentation clearly separates obligation management from template design.

Therefore, the correct additional permission set required to start building the MSA template with clauses in Word is Microsoft 365 Word Designer (Option C).

References (Salesforce Revenue Cloud documentation / study materials):

Salesforce Revenue Lifecycle Management / Revenue Cloud: DocGen Setup and Permissions

Salesforce Revenue Lifecycle Management Implementation Guide: Document Generation and Clause Management

Salesforce Help: Permission Sets – DocGen Designer, Clause Designer User, Microsoft 365 Word Designer

===========

Explanation (150–250 words)

In Salesforce CPQ and Revenue Cloud, configurable bundle products are designed to give users flexibility during the quoting process. They contain multiple product options and optional features that can be customized based on customer needs. Each bundle can include predefined components (static) or user-selectable options (configurable), along with configurable attributes such as size, term, or license type.

This model allows sales representatives to create tailored product combinations by selecting or deselecting components, setting quantities, and adjusting attributes directly in the Quote Line Editor. This flexibility enhances accuracy in pricing and ensures the quote reflects the customer’s precise requirements.

By contrast, simple products are standalone and sold as-is, while static bundles have fixed options that cannot be altered during quoting. Therefore, option C correctly describes the behavior of configurable bundled products—allowing customization of both components and attributes at quote time.

Exact Extract from Salesforce CPQ Implementation Guide:

“Configurable bundles allow users to customize product components and define attributes at the time of quoting. This enables flexibility in configuring products to match customer requirements.”

Comprehensive and Detailed Explanation From Exact Extract:

In Salesforce Revenue Lifecycle Management, eligibility and availability rules are built using Decision Tables. The predefined templates for product eligibility and product availability rely on Qualification objects.

From the Revenue Lifecycle Management Implementation Guide:

“Eligibility and availability rules are driven by Product Qualifications and Product Category Qualifications, which determine whether a product can be selected for a specific customer or scenario.”

“Decision table templates for eligibility and availability use Qualification objects as the evaluation criteria.”

These objects are designed specifically for determining whether a product should be selectable based on business rules, customer attributes, and catalog categorizations.

Why other options are incorrect:

Product Price Book and Product Schedule are used for pricing, not eligibility.

Product Relationship and Product Attribute are used in configuration rules, not eligibility templates.

Comprehensive and Detailed Explanation From Exact Extract:

Revenue Cloud provides Usage Management, which fully supports usage-based pricing, rating, and invoicing.

From the Subscription Management and Billing Implementation Guides:

“Usage Management allows ingestion of raw usage records.”

“Usage data is aggregated, rated, and billed based on the product’s rate plan.”

“Tiered pricing is supported natively through usage rate tiers.”

Option B refers to Digital Wallet, which is for prepaid drawdowns—not rating usage or supporting tiered charges.

Option A is unnecessary because Salesforce provides end-to-end usage aggregation, rating, and billing out of the box.