Ace Your Development-Lifecycle-and-Deployment-Architect Salesforce Developer Exam

The best strategy to delete the day’s test data in a partial copy sandbox every night is to execute a batch job that deletes all records created on the day. This way, you can automate the process of cleaning up the test data and avoid manual work. Manually deleting all records individually is time-consuming and error-prone. Creating a new developer copy sandbox every night is unnecessary and wasteful, as developer copy sandboxes have limited storage and functionality. Refreshing the sandbox every night is also not feasible, as partial copy sandboxes have a refresh interval of 5 days.

Tracking effort estimates, actuals, and remaining work can help the developer improve their estimation skills and accuracy, which can benefit the project planning and delivery.

The development model that the architect should recommend to be used by the consolidated development team is the package development model. This model allows teams to build release artifacts that can be tested and released independently from artifacts for other projects, using unlocked packages or second-generation managed packages. This model can help improve the modularity, reusability, and maintainability of the code and configuration, as well as enable source-driven development and continuous integration and delivery. The org development model is not a good choice for the consolidated development team, as it is based on working directly in an org and using change sets or metadata API tools to deploy changes. This model can lead to conflicts, dependencies, and governance issues, especially when working on multiple projects or with multiple teams. The change set development model is also not a good choice for the consolidated development team, as it is based on using change sets to deploy changes between connected orgs. This model can be slow, error-prone, and limited, as it does not support all metadata types, dependencies, or automation. The package development model does not allow packages to be created and deployed using declarative (point-and-click) development tools, without writing code. This is a wrong statement, as the package development model supports both declarative and programmatic development tools, and requires writing code to create and install packages using the Salesforce CLI or APIs. See Package Development Model for more details.

The best practice for moving classes between packages is to set them as deprecated in the source package and recreate them in the target package. This way, the existing subscribers of the source package will not be affected by the change, and the new subscribers of the target package will get the updated classes. Moving the classes directly or changing their names can cause compilation errors and dependency issues.