The correct selection is B, C. Unlocked-package adoption should begin by checking metadata packaging support and testing package versions in non-production environments before production installation. The Metadata Coverage Report identifies what can be packaged, while source control remains essential and a single monolithic package defeats modular package-development principles. From a build perspective, the implementation should be source-driven, reviewable, automatable, and modular. Engineering controls such as version control, package boundaries, static analysis, coding standards, and isolated development environments reduce defects early and make changes easier to understand, test, and promote. The rejected choices either rely on manual review alone, use the wrong development abstraction, or introduce custom complexity where Salesforce already provides a source-driven engineering mechanism. For this scenario, the decisive point is therefore the platform behavior represented by the selected options (B. Consult the metadata coverage report to identify features supported by packages.; C. Test developed packages in test environments before installing to production.). 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: Building — Salesforce DX; package development; coding standards; static analysis; source control; secure development.