The Renewal process in Salesforce Revenue Cloud begins with creating a Renewal Quote based on existing Assets (representing active subscriptions or entitlements). The Renewal Quote inherits pricing, terms, and quantities from the current assets and allows for updates such as upsells or discounts.
Once the Renewal Quote is approved, it is converted into an Order, and upon Order activation, Salesforce automatically generates new Assets (and optionally renewal Contracts if managed through Subscription Management).
Therefore, the correct renewal flow is:
Create Renewal Quote with linked Assets.
Create Order from the Renewal Quote.
Activate Order, triggering renewal assetization and lifecycle continuation.

Experience Cloud (formerly Communities) is the standard Salesforce framework for giving partners or customers self-service, license-efficient access to features like catalog browsing and quote submission, and it integrates directly with Revenue Cloud's Product Discovery and Quoting APIs to expose these capabilities in a branded external portal. Chatter Groups are for collaboration, not transactional self-service, and Mobile Publisher is about app packaging, not portal access control.

Salesforce Revenue Lifecycle Management provides a modern contract lifecycle management experience using Salesforce Contracts Connector for Word, which enables:
Contract document generation
Clause insertion and management
Redlining within Microsoft Word
Integration with e-signature providers
Tracking and syncing changes back to Salesforce
From the RLM Implementation Guide:
"Salesforce Contracts Connector for Word allows users to generate agreements, manage clauses, and perform redlining directly within Microsoft Word."
"Supports digital negotiation workflows and integrates with DocGen and e-signature."

Standard context definitions provided by Salesforce are locked and cannot be edited or deactivated.
Revenue Lifecycle Management Implementation Guide states:
"Standard context definitions cannot be modified directly."
"To customize them, admins may either extend (create a child version) or clone them." Only these two actions are supported for customizing context behavior.

"Local Cardinality defines the minimum and maximum quantities allowed for an individual product option within a bundle."
"Group Cardinality defines the quantity range allowed across all options within a product option group. It restricts the total number of items a user can select within that group."
"Use both local and group cardinalities together to control both per-option limits and total group quantity constraints." Step-by-Step Reasoning:
Requirement:
Max 3 T-shirts
Max 3 caps
Total bundle limit = 5 items combined.
Solution:
Local Cardinality: For each item (T-shirts, caps) min 1, max 3 ensures flexibility.
Group Cardinality: Across both min 1, max 5 ensures total combined limit of 5.
Why B is Correct:
It satisfies both individual and group quantity rules while maintaining configuration flexibility.