Describe the Common Tools, Benefits, and Rationale for Using Source Control and Continuous Integration for Release Management. TECHNICAL-ARCHITECT Practice Questions (Page 3)

Questions 11–15

1. 11application · medium

   A Salesforce team is experiencing frequent production issues due to untested code and inconsistent builds. They want to adopt practices that improve quality and release predictability. Which combination of practices best addresses their concerns?

   • AAdopt source control for versioning and auditability, and implement CI to automate testing on every commit.
   • BImplement CI but do not use source control, relying on the CI tool to store code versions.
   • CUse source control only for documentation and rely on manual testing before each release.
   • DUse a single shared sandbox for all development and deploy directly to production after a quick smoke test.
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   What is the role of continuous integration in the release management process for Salesforce?

   • AIt automates the final deployment to production, eliminating the need for manual approval
   • BIt manages the version number of the Salesforce org
   • CIt validates that the code is ready for release by running automated tests and builds
   • DIt creates the release notes and documentation for the release
   Reveal Solution Discussion Select an answer first
4. 13expert · hard

   A Salesforce team is planning a release that includes a new custom object, a change to an existing Apex trigger, and a modification to a permission set. They use source control and CI. The release must be deployed to production with minimal risk. Which approach best ensures a predictable release?

   • ACreate a release branch from the main branch, run the full CI pipeline including all Apex tests, and deploy the release branch to production after approval.
   • BRun only the tests related to the changed components in CI, and deploy directly to production without a release branch.
   • CDeploy each metadata component individually to production as soon as it is merged to main, without waiting for a release branch.
   • DUse a change set to deploy the components directly from the sandbox to production, bypassing source control and CI.
   Reveal Solution Discussion Select an answer first
5. 14foundation · easy

   How does continuous integration provide faster feedback loops to Salesforce developers?

   • ABy sending automated email notifications after every production deployment
   • BBy scheduling daily builds and test runs
   • CBy requiring developers to manually run tests before committing
   • DBy running tests and reporting results shortly after code is committed
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   A Salesforce team wants to reduce the time between writing code and discovering defects. They plan to implement CI. Which CI practice directly supports faster feedback loops?

   • ARunning a full regression test suite on every commit and notifying the developer of failures.
   • BRunning tests only when a release candidate is created.
   • CRequiring developers to run tests manually before each commit.
   • DSending test results via email once a week.
   Reveal Solution Discussion Select an answer first