What should you do when you're starting to organize your metadata into packages?

What should you do when you're starting to organize your metadata into packages?

• A. Put all your metadata into one unlocked package.
• B. Identify a set of related metadata that represents a functional unit.
• C. Convert your source to Salesforce DX format using force:source:convert.
• D. Create a package with a namespace to make sure API names don't change.

Answer: (B)

When starting to organize metadata into packages, the best move is to identify a set of related metadata that represents a functional unit. Grouping components by a specific business capability creates cohesive packages that can be developed, tested, and deployed independently. This modular approach lets you version and release changes for one feature without affecting others, and it makes managing dependencies between packages clearer. It also improves governance and reduces the risk of widespread impact from changes. Lumping everything into a single package makes deployment and maintenance harder, since updates touch the entire system and can unintentionally affect unrelated parts. Converting the source to Salesforce DX format is a necessary tooling step, not the organizational strategy. Adding a namespace helps with naming and distribution, but it doesn’t determine how you should structure packages around functional boundaries.

When starting to organize metadata into packages, the best move is to identify a set of related metadata that represents a functional unit. Grouping components by a specific business capability creates cohesive packages that can be developed, tested, and deployed independently. This modular approach lets you version and release changes for one feature without affecting others, and it makes managing dependencies between packages clearer. It also improves governance and reduces the risk of widespread impact from changes.

Lumping everything into a single package makes deployment and maintenance harder, since updates touch the entire system and can unintentionally affect unrelated parts. Converting the source to Salesforce DX format is a necessary tooling step, not the organizational strategy. Adding a namespace helps with naming and distribution, but it doesn’t determine how you should structure packages around functional boundaries.