SKU rationalization is a process that involves reviewing and trimming down the product variety to focus on the most profitable SKUs1. This process is crucial in managing SKUproliferation, which refers to the creation of multiple product records for various product combinations offered, even though they are the same product, merely sold under different scenarios2.
In the context of Salesforce Revenue Cloud, SKU rationalization can be achieved through the consolidation of products in the following areas:
B). Same product names with different attribute values: Products that are essentially the same but have different attribute values can be consolidated. This reduces the complexity of the product catalog and makes it easier to manage2.
D). Same product names commonly found in the same bundle: Products that are often sold together in the same bundle can be consolidated. This not only simplifies the product catalog but also makes it easier for customers to make purchases2.
E). Same product names with different Term length: Productsthat are the same but have different term lengths can be consolidated. This can simplify the product catalog and make it easier for customers to understand the products they are purchasing2.
https://www.simplus.com/sku-rationalization-strategy/

To migrate legacy install base into Salesforce CPQ along with the contract, the Revenue Cloud Consultant needs to populate the Assets and Subscriptions objects. These objects store the information about the products and services that the customer has purchased and are associated with the contract. The Assets object tracks the physical products, such as hardware and software licenses, that have been delivered or activated for the customer. The Subscriptions object tracks the recurring products, such as software subscriptions or maintenance plans, that have a defined billing frequency and term. By populating these objects, the Revenue Cloud Consultant can preserve the history of the customer's purchases and enable the features of Salesforce CPQ, such as renewals, amendments, and co-termination. References:
* Migrate Legacy Data to Salesforce CPQ
* [Assets]
* [Subscriptions]

C) Lead with Business Requirements and Process123: This principle helps you understand the specific needs and objectives of the project, as well as the current and desired state of the business processes. It also helps you align the project scope with the business value and outcomes.
D) Think Transformation before Customization3: This principle helps you leverage the best practices and capabilities of Revenue Cloud, and avoid unnecessary or complex customizations that may increase costs, risks, and maintenance efforts. It also helps you embrace change and innovation, and optimize your revenue operations.
A) Alignment with customer on CPQ and Billing Terminology3: This principle helps you establish a common language and understanding of the key concepts and features of Revenue Cloud, such as CPQ (Configure-Price-Quote), Billing, Subscription Management, etc. It also helps you avoid

According to the Salesforce Revenue Cloud Implementation Guide, any changes to the design document during the build phase should be communicated to the project manager, who will assess the impact of the changes on the project scope, timeline, and budget. The project manager will then decide whether to accept, reject, or defer the changes, and update the project plan accordingly. This is the best practice to ensure that the project is delivered on time, on budget, and with the expected quality and functionality.
Implementing the lookup price rules immediately without consulting the project manager or the solution architect could result in errors, inconsistencies, or conflicts with the existing design or other components of the solution. It could also cause delays or rework if the changes are not aligned with the customer's expectations or requirements. Therefore, option B and option E are not appropriate.
Consulting with the solution architect first could help to expedite the updates to the design document, but it would still require the approval of the project manager and the customer before implementing the changes.
Therefore, option D is not sufficient.
Communication to the customer that ongoing adjustments can be made as long as we are in the build phase could create confusion or unrealistic expectations about the project scope and timeline. It could also undermine the credibility and authority of the project manager and the solution architect, who are responsible for managing the project and ensuring the quality of the solution. Therefore, option A is not advisable.
References:
* 1: Salesforce Revenue Cloud Implementation Guide, page 17
* 2: Lookup Price Rule query considerations with Salesforce CPQ 3