During continuous delivery, which activity is performed?

During continuous delivery, which activity is performed?

• A. Build & install (staging, UAT)
• B. Code development in a scratch org
• C. Check-in and unit tests
• D. Install training and production

Answer: (A)

In continuous delivery, the goal is to keep code in a releasable state by automatically building and validating it through environments that resemble production. The activity that best fits this is building the artifact and installing it into staging or UAT. This step produces a deployable version and allows verification by QA and stakeholders in a pre-production environment, confirming that the system behaves as expected before actual production deployment. Development in a scratch org happens earlier in the cycle, while check-in and unit tests are typically part of the integration/CI phase, not the deployment to pre-production. Installing training and production isn’t a standard CD step, since training is usually separate and production deployment is the release activity, not the constant CD validation step.

In continuous delivery, the goal is to keep code in a releasable state by automatically building and validating it through environments that resemble production. The activity that best fits this is building the artifact and installing it into staging or UAT. This step produces a deployable version and allows verification by QA and stakeholders in a pre-production environment, confirming that the system behaves as expected before actual production deployment. Development in a scratch org happens earlier in the cycle, while check-in and unit tests are typically part of the integration/CI phase, not the deployment to pre-production. Installing training and production isn’t a standard CD step, since training is usually separate and production deployment is the release activity, not the constant CD validation step.