In Revenue Cloud / Revenue Lifecycle Management, context mappings control how values (such as attributes or fields) flow between the runtime configuration/quoting experience and underlying Salesforce objects. When defining a mapping, you specify a Mapping Intent, which determines how the data is used and whether it is stored.
The documentation describes the Persistence intent along the lines of:
Persistence
Use this intent when you want the mapped value to be written to and stored on the underlying Salesforce object so it can be used later in downstream processes (such as orders, contracts, billing, or analytics).
This exactly matches the scenario described in the question:
A sales user updates a custom attribute when selecting products for a quote.
The value must be available for downstream processes (for example, contract creation, order generation, billing, or reporting).
Therefore, the value needs to be persisted to an object/field, not just used temporarily in the UI.

In Revenue Cloud's attribute model:
From the RLM Product Catalog Guide:
"Attribute categories appear in the configurator in the order defined by the Sequence field on the Attribute Category record."
"Any attributes not assigned to a category appear in an automatically generated category called Uncategorized, displayed last." Alphabetical order is not used.
Display order is deterministic, not random.

Renewal Flow Templates are the out-of-the-box solution for creating Renewal Opportunities and Quotes/Orders in Revenue Cloud. Salesforce provides prebuilt flow templates specifically designed to automate the renewal process without requiring custom development.
According to Salesforce Help documentation on Flow Templates for Renewal Automation, Revenue Cloud includes the "Create and Update Renewal Opportunities" flow template. This template automatically creates renewal opportunities for forecasting purposes when assets are created, and keeps them synchronized when customers amend or cancel subscriptions. The flow template is triggered by platform events and uses standard Revenue Cloud invocable actions.
The renewal flow templates utilize the InitiateRenewal invocable action, which is a standard out- of- the-box Apex action provided by Salesforce. This action can create either renewal quotes or renewal orders based on specified parameters, and it properly links these transactions to renewal opportunities for accurate forecasting. The flow templates handle the complexity of tracking asset end dates, calculating renewal amounts, and maintaining synchronization between assets and renewal opportunities.

In Salesforce CPQ, Constraint Models define validation, inclusion, and compatibility rules that control product configuration behavior. When a validation or warning depends on an attribute value of a single product, the logic should be defined at the Product Level Constraint Model.
In this scenario, the "Terabyte" attribute belongs to "Product A," and the business rule requires displaying a warning message when the attribute exceeds 100. Implementing this at the Product Level Constraint Model ensures that the rule evaluates only that product's context and triggers the message directly within the configuration page when users input the attribute value.
Quote-level constraint models are used for cross-product validations across multiple quote lines, not for product-specific attribute conditions. Therefore, option C correctly uses the Product Level Constraint Model.

In Salesforce Revenue Cloud, the ability to manage product records within the product catalog is governed by specific permission sets and licenses. If a user can view but not edit product records, they likely lack the proper Permission Set License (PSL) required to perform product catalog modifications.
The correct solution is to assign the Product Catalog Management Designer permission set license, which enables users to:
Create and update product records
Manage attributes, configurations, and pricing
Work with product relationships and dependencies
According to the Salesforce CPQ Implementation Guide, this permission set is essential for users responsible for catalog operations.