Which statement is true about unlocked packages?

Which statement is true about unlocked packages?

• A. They can be changed directly in production
• B. They are developer-controlled
• C. Installing new version overwrites what has been done in production
• D. They can contain any type of Salesforce metadata

Answer: (B)

Unlocked packages are designed for source-driven development with Salesforce DX, where the package contents, versioning, and release process are owned by the development team. This makes them developer-controlled: the team decides exactly what metadata goes into each package, when changes are made, and how those changes are distributed across environments through upgrades. This model emphasizes control and traceability—you manage the package in source control, create new versions for each release, and install or upgrade in sandboxes, scratch orgs, or production as needed. It also contrasts with the idea of editing things directly in production; you typically make changes in your development environment and push a new package version rather than editing in production. Notes on the other statements: while unlocked packages can be upgraded, the behavior of upgrades can vary by metadata type and change set, so it’s not a blanket rule that an upgrade simply overwrites all production work. Also, unlocked packages cover many metadata types, but not literally every possible type, as some types may have limitations or special handling requirements.

Unlocked packages are designed for source-driven development with Salesforce DX, where the package contents, versioning, and release process are owned by the development team. This makes them developer-controlled: the team decides exactly what metadata goes into each package, when changes are made, and how those changes are distributed across environments through upgrades.

This model emphasizes control and traceability—you manage the package in source control, create new versions for each release, and install or upgrade in sandboxes, scratch orgs, or production as needed. It also contrasts with the idea of editing things directly in production; you typically make changes in your development environment and push a new package version rather than editing in production.

Notes on the other statements: while unlocked packages can be upgraded, the behavior of upgrades can vary by metadata type and change set, so it’s not a blanket rule that an upgrade simply overwrites all production work. Also, unlocked packages cover many metadata types, but not literally every possible type, as some types may have limitations or special handling requirements.