Certified Development Lifecycle and Deployment Architect

Partial Copy sandboxes have a 5-day refresh interval, so they cannot be reset by refreshing every night. A Developer sandbox provides only 200 MB of data storage, which is insufficient for approximately 1 GB of test data. A batch job can efficiently delete the records created that day and restore the existing sandbox for the next day’s tests.

A common release calendar gives every team visibility into release windows, dependencies, and potential conflicts across all release types. Training teams on a shared release process aligns their planning and execution, including preparation for Salesforce’s predictable seasonal releases. Salesforce guidance identifies the release calendar as a tool for coordinating schedules and avoiding conflicts, while Salesforce seasonal releases occur on a predictable cycle.

A technical architect evaluates whether a proposed change is technically viable, appropriately designed, and compatible with the existing technical environment. The relevant advice is that the solution is technically sound.

A .zip release artifact is deployed in Metadata API format, so both validation and the subsequent full deployment use sfdx:mdapi:deploy. Validation is a check-only Metadata API deployment; when quick deployment is not used, a separate Metadata API deployment must run after successful validation. Salesforce documentation identifies force:mdapi:deploy as the CLI command for Metadata API deployments and notes that it supports the --checkonly validation parameter.

Redeploying an earlier metadata version updates or restores included components but does not remove components added by the failed release. A reliable metadata rollback retains a pre-deployment baseline, deletes release-added components through a destructive-changes manifest, and redeploys the baseline. Salesforce supports destructive manifests specifically for deleting metadata components during deployment.