Universal Containers (UC) has multiple teams working on different projects.

The correct selection is D. Static code analysis can automatically and consistently enforce naming, maintainability, security, and other coding standards across teams and repositories. It scales better than relying only on human review and can be integrated as a CI quality gate before code is merged. 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 remaining options are weaker because they address symptoms after code is written instead of improving the build process through automation, modularity, and explicit development standards. For this scenario, the decisive point is therefore the platform behavior represented by the selected option (D. Use static code analysis to enforce coding standards.). 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.