The correct selection is B, D. Salesforce CPQ stores important configuration as records rather than ordinary deployable metadata. A source-controlled SFDX-compatible data migration approach or a specialized third-party DevOps product can preserve relationships and automate promotion; manually maintained CSV loading or custom Apex deployment frameworks create unnecessary operational risk. From a deployment perspective, the same release should be reproducible across environments, with dependencies, metadata/data differences, API behavior, and target-org constraints identified before production. Automation is valuable because it turns deployment knowledge into a controlled process rather than relying on memory or manual reconstruction. The rejected alternatives do not meet the deployment requirement because they introduce drift, ignore target-org compatibility, or substitute a convenience tool for a reproducible release artifact. For this scenario, the decisive point is therefore the platform behavior represented by the selected options (B. Use an open source SFDX plugin and version control.; D. Use a third-party product.). Applying that rule consistently keeps the implementation aligned with Salesforce-supported lifecycle practices and makes the resulting change easier to review, validate, and operate across environments.

Study Guide reference: Deploying — Metadata API and Tooling API; deployment validation; package/change-set deployment; data migration; dependency management.