To correct a deployment package after it has been transferred to a destination, which approach is recommended?

• A. Create a new package in the destination site then install the new package.
• B. Change the package at the destination site and reinstall it.
• C. Edit the package at the source site and redeploy the whole package to the destination site.
• D. Edit the package at the source site and save it in a new folder. Use the Compare feature to save the differences in a new package.

Answer: (C)

The important idea is to keep deployment artifacts under centralized control and ensure consistent, repeatable deployments by updating the source and redeploying the whole package. If you edit at the destination, you introduce drift between environments and break the version history, making it hard to audit, rollback, or reproduce deployments. The source site is the single place where changes should be tracked and versioned, then the updated, complete package should be redeployed to the destination so both environments stay in sync with the same artifact. Creating a new package at the destination or making changes there undermines this consistency, and using a “save differences” approach also complicates management. By editing the package at the source and deploying the full, updated package to the destination, you preserve integrity, traceability, and repeatability across deployments.