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

Questions 26–30

1. 26application · medium

   A Salesforce team of 15 developers is moving from a shared sandbox where everyone edits metadata directly. They want to adopt source control to improve collaboration and reduce overwrites. Which approach best supports their goal?

   • AUse SVN with a single trunk where all developers commit directly to the main line.
   • BUse Git but have all developers commit directly to the main branch without pull requests.
   • CUse Git with a branching strategy where each developer works in a feature branch and merges via pull requests.
   • DContinue using the shared sandbox but enable field history tracking on all custom objects.
   Reveal Solution Discussion Select an answer first
2. 27application · medium

   A Salesforce admin accidentally deployed a faulty Apex class to production. The team uses source control for all metadata. What is the most efficient way to recover?

   • AContact Salesforce support to restore the previous version of the class.
   • BRevert the faulty change in source control and redeploy the previous version from the repository.
   • CManually edit the Apex class in production to fix the bug.
   • DUse the sandbox to recreate the class from memory and deploy it.
   Reveal Solution Discussion Select an answer first
4. 28expert · hard

   A Salesforce team is currently using SVN. They are experiencing difficulties with branching and merging, especially when multiple developers work on the same files. They are considering migrating to Git. What is the primary advantage Git offers over SVN for this scenario?

   • AGit's distributed model and lightweight branching make it easier to work in parallel and merge changes.
   • BGit provides a centralized server that locks files to prevent concurrent edits.
   • CGit is the only source control tool that integrates with Salesforce DX.
   • DGit automatically resolves all merge conflicts without developer intervention.
   Reveal Solution Discussion Select an answer first
5. 29foundation · easy

   How does source control support release management in Salesforce projects?

   • ABy preventing any changes to code after a release is planned
   • BBy automatically deploying code to production when a release is approved
   • CBy providing a stable codebase and the ability to create release branches or tags
   • DBy generating a list of all changes for the release notes
   Reveal Solution Discussion Select an answer first
6. 30application · medium

   A Salesforce team is using Git for source control but is not using branches. All developers commit directly to the main branch. They are experiencing frequent conflicts and broken builds. What is the most effective way to improve their workflow?

   • ASwitch to SVN because it handles conflicts better.
   • BIntroduce a branching strategy with short-lived feature branches and pull requests for merging.
   • CHave developers communicate more frequently about their changes.
   • DRequire developers to lock files before editing to prevent conflicts.
   Reveal Solution Discussion Select an answer first