Complete Rev-Con-201 Salesforce Materials

For the Revenue Management behavior tested by this question bank, a ramped subscription cancellation could not be entered with an effective date earlier than the transaction date. Because the customer contacts the sales rep onJuly 5, 2025, the earliest valid effective date under that behavior is July 5, making option A correct for this certification item.

Option B would cancel from the original lifecycle start date and effectively remove the customer ' s service for a period in which it was legitimately active. Option C unnecessarily requires waiting until the end of the one-year subscription term; lifecycle-managed subscriptions can be canceled before their scheduled expiration.

There is an important current-product distinction. Salesforce has subsequently introduced support forbackdated Amend, Renew, and Cancel transactions, including ramped assets in newer Revenue Management functionality. Current documentation states that an effective date can be entered in the past on or after the asset ' s lifecycle start date, with asset periods and Revenue Cloud Billing adjustments updated accordingly.

Therefore,A is the answer explicitly keyed by the supplied certification source, while current production capability should be evaluated against the Salesforce release enabled in the target org.

Study Guide Reference:Asset Management — Renewals and Cancellations; ramped assets; effective-dated lifecycle transactions.

The Managed Asset Viewer is a Lightning component and must be explicitly placed on the appropriate Lightning record page. Salesforce documents that administrators use Lightning App Builder to add the Managed Asset Viewer to Account and Contract record pages. Once installed, the component provides a consolidated representation of lifecycle-managed assets, including standalone and bundled assets.

The optional side panel is particularly relevant because it enables users to open an asset and inspect additional details and product attributes without navigating away from the viewer. Salesforce specifically documents that users can edit asset information either directly within the viewer or through this side panel. Therefore, option A describes the correct configuration mechanism.

Option B confuses an Assets related list with the Managed Asset Viewer. A related list does not automatically instantiate the specialized lifecycle-management component. Option C also mixes record-level access requirements with component placement; permissions remain necessary, but assigning Account/Asset access does not itself make an absent Lightning component appear.

Salesforce ' s current setup documentation explicitly instructs administrators to add and configure the Managed Asset Viewer on the record page using Lightning App Builder.

Study Guide Reference:Asset Management — Asset Lifecycle Management with Agentforce Revenue Management; Managed Asset Viewer configuration.

===============

Contracts AI extraction is controlled through aContract Extraction Templatetogether with the underlying context definition and mappings. Salesforce documents that an extraction template defines attribute mapping, context mapping, and extraction instructions used by generative AI to retrieve contract information from uploaded files.

For a new custom field such as Payment Method, the consultant must ensure that the context definition contains the appropriate user-defined attribute and that a corresponding persistence/context mapping exists to the custom field on the Contract record. The extraction template is then configured to include that attribute so Contracts AI knows which information to identify and where to place the extracted result.

Option B incorrectly treats a generic AI prompt template as the primary data-mapping layer. Prompts or field-level extraction instructions can influence how information is interpreted, but the structured field and context mappings belong to the Contracts AI extraction-template configuration. Option C is unnecessary because Salesforce supports user-defined extraction fields through customizable context definitions and mappings.

Study Guide Reference:Contracts and Orders — Generative AI for Salesforce Contracts; Contracts AI; Contract Extraction Templates; custom field extraction.

===============

Before build work begins, the project needs a controlledenvironment and deployment strategy. Separate development, testing/UAT, and production environments allow configuration and code to move through progressively controlled stages without exposing production users to unfinished functionality.

The team should also establish the deployment mechanism before significant configuration begins. Revenue Management implementations can include metadata, Context Service definitions, Product Catalog Management configuration, decision tables, pricing procedures, flows, permissions, and other deployable artifacts. Understanding how these components will move between environments helps prevent late-stage release failures and manual inconsistencies.

Option B contains activities that primarily belong to discovery and design. User stories, requirement workshops, and initial test-case definition should already be sufficiently mature before the project transitions into build. They can be refined during implementation, but they are not the central readiness action at this phase transition. Option C violates fundamental Salesforce deployment practice. Production should not function as an uncontrolled development or testing environment.

Therefore, establishing the environment architecture and deployment tooling provides the governance required for a repeatable and successful build cycle.

Study Guide Reference:Implementation Readiness — Environment Strategy; deployment planning; build and release readiness.

===============