Comprehensive and Detailed Explanation From Exact Extract:
The Transaction Line Editor (TLE) supports:
* Column filtering and sorting.
* Inline editing and recalculation.
* Manual save actions.
There is no "drag to sort" capability (A). Changes are not auto-saved (C); users must explicitly save.
References:
Revenue Lifecycle Management Implementation Guide - Transaction Line Editor Features

Comprehensive and Detailed Explanation From Exact Extract:
In Revenue Cloud Product Catalog Management, Browse Catalog product visibility is controlled using Qualification Rules and Product Qualification decision tables. The standard ("out-of-the-box") decision table and related qualification rule procedures are designed exactly for use cases like:
* Hiding or showing products based on contextual criteria such as region, industry, customer segment, etc.
* Evaluating product visibility during Product Discovery / Browse Catalog.
The documented approach is to configure ProductQualification and Qualification Rule Procedures so that they reference customer region (for example, via Account or Quote fields) and drive visibility accordingly. This leverages standard Revenue Cloud capabilities instead of creating custom frameworks.
Option A (custom decision table) is possible but not the recommended Revenue Cloud-specific capability when there is already an out-of-the-box decision table built for product qualification.
Option B (separate price books per region) controls pricing, not visibility, and quickly becomes hard to maintain.
References:
Salesforce Revenue Lifecycle Management Implementation Guide - Product Qualification, Qualification Rule Procedures, and catalog visibility Product Catalog Management Documentation - Using Qualification Rules with Browse Catalog

In Salesforce Revenue Cloud's Contract Lifecycle Management (CLM) module, Obligations are used to track post-signature responsibilities and ensure compliance with contractual commitments. An obligation represents an actionable item tied to a contract clause, such as delivering a report, making a payment, or completing a follow-up.
One of the primary benefits of creating obligations is the ability to:
* Assign Owners (users or roles)
* Attach Tasks
* Set due dates, statuses, and related metadata
This allows organizations to track performance on obligations over the lifecycle of the agreement and maintain accountability.
* Option A is correct, as assigning owners and tasks is core to the obligation management model.
* Option B is partially correct but too narrow; the Fulfilled status is only one aspect of the obligation lifecycle.
* Option C is incorrect - price discounts are managed through pricing rules, not obligations.
Exact Extracts from Salesforce Revenue Cloud Documents:
* CLM Implementation Guide - "Obligation Management":"Obligations allow contract owners to assign responsibilities to individuals and track their completion using tasks, due dates, and fulfillment status."
* Revenue Cloud CLM Overview - "Post-Signature Lifecycle Features":"Use obligations to monitor compliance with agreed-upon clauses by assigning tasks to the appropriate business users." References:
Salesforce CLM Implementation Guide
Salesforce Revenue Cloud CLM Functional Overview
CLM Admin and Template Designer Documentation

Exact Extracts from Salesforce Billing Implementation Guide:
* "When generating invoices, Salesforce Billing uses the billing account attached to the order as the billing entity."
* "If a billing account is specified on the order, its details (including Billing Address) take precedence over the order or account-level billing information."
* "If no billing account is provided, the system falls back to the order's billing fields, and then to the account's default billing profile." Step-by-Step Reasoning:
* Hierarchy for billing address resolution:Billing Account (highest) # Order Billing Address # Account Billing Profile (lowest).
* In this case:
* Billing Account (Chicago) exists and overrides all others.
* Why B is Correct:The billing process will use Chicago, because the billing account attached to the order dictates the billing details.
References :
* Salesforce Billing Implementation Guide - Billing Account Hierarchy and Invoice Address Resolution
* Salesforce Subscription Management Implementation Guide - Order Billing Account Logic

Comprehensive and Detailed Explanation From Exact Extract:
Revenue Cloud CLM supports Import Contract to:
* Take a customer-provided .docx document.
* Bring it into the CLM system as a contract version.
* Allow further negotiation and clause management.
"Generate from a Template" (B) creates documents based on Salesforce templates, not external files. "Modify in Microsoft 365 editor" (C) assumes the contract was already generated from CLM; it doesn't start from a customer's own document.
References:
CLM / Contract Authoring Documentation - Import Contract Functionality