Copado Fundamentals Level 1 Study Guide and
Practice 2025/2026
1. 1 What Is Copa-
do?
2. 2 Standard Sales-
force Develop-
ment Lifecycle*
3. 3 What is De- DevOps is a combination of practices that automate and enable greater e�ec-
vops? tiveness in the process of building and running software. DevOps combines the
technical practices of Continuous Delivery with the business practices of lean
management and lean product development.
4. 4 What are the The rst thing you encounter is that there's not a clear overview of the whole
main Challenges process. You may have these questions
in Salesforce De- Where do changes happen?
velopment Life- Should I start in dev1, or can I implement my changes directly in production?
cycle? Which environment do I need to deploy rst?
Is it UAT or Integration?
Who is going to approve my changes?
5. 5 what are the Change Sets Limitations - Companies spend a lot of time building change sets.
limitations of the Here are some of the limitations of change sets that you should know:
change sets? 1.Change sets do not o�er the capability to search components by name or type.
As a developer, you are forced to browse through multiple pages to nd the
metadata items you want to select.
2.If you accidentally add a component, you cannot lter within your selections to
remove the component quickly.
3.Certain components are not available to be deployed using change sets, and it's
possible to move changes only across environments that are connected.
4.With change sets, all selected components come in a single list, so you can't
scope which modi cation is based on which request
, 5. Change sets do not enable continuous delivery, and automation of deployments
is not an easy task
6. 6 What are the dif- Release teams struggle with sandbox syncing after deploying to higher environ-
�culties Keeping ments. For example, if a company uses a hot x sandbox to develop and push
Environments in xes to production, lower environments will show discrepancies regarding the
Sync? production environment. These di�erences can lead to deployment errors and a
blocked pipeline. Even having multiple developer environments requires users to
keep those environments in sync.
7. 7 What are the 1. Metadata loss. All the work in progress in a sandbox will be overwritten after
Problems arise if the refresh.
we refresh the 2. Full sandboxes can only be refreshed once per month, therefore they can't easily
sandboxes.? receive changes that were sent from a hot x environment to production.
3. Scrambled emails. Whenever a sandbox is refreshed, user email addresses
are modi ed in the sandbox so that production users don't receive automatically
generated email messages from the sandbox. Hence, users are required to
validate an email address change in order to be able to log in again into the
sandbox. 4.Data loss. Unless you're refreshing a full sandbox or a partial copy,
you will lose all data. Hence, you need to recreate the test data all over again.
8. 8 What happens "There is a major issue when multiple developers work in the same environment
If multiple Devel- and perform changes in the same components. As mentioned in the Change Sets
opers working on Limitations section, when you work with change sets, you have no visibility on who
the same compo- has made what changes, and there are no tools for you to foresee if your changes
nents? will be overwritten.
9. 9 Why salesforce Salesforce makes it amazingly easy for individuals to build changes but it was
Deployment is not made with collaborations of large teams in mind. As your team grows, you
Di culty for the may nd it challenging to collaborate. Synchronizing environments, tracking the
teams to collabo- history, and being unable to merge changes on a line-by-line basis is di cult, so
rate? you are reducing your team's possibilities to collaborate and work together.
,10. 10 Is there Salesforce does not provide a de nitive recommendation on how to manage the
any Standard release process and doesn't include native Agile tools and metrics.
tool provided by
Salesforce for
the deployment
Process?
11. 11 Salesforce Salesforce provide only limited set of Quality Checks.
provide Quali-
ty Checks on
Changes?
12. 12 what is Apex tests are the only built-in Salesforce capability that ensures the quality of your
the built in customizations. Apex tests can identify speci c errors, but they are not meant to
Salesforce Quali- identify code ine ciencies and bad habits before they become a problem.
ty Check ?
13. 13 How the com- "There are also many other types of tests that go beyond what Apex alone o�ers
pany Make sure and can help ensure the quality of your team's work. To keep their code optimized,
the quality of companies have to make further e�orts in de ning and implementing a code
code? inspection process.
14. 14 What are 1. No Clear Overview of the Whole Process .2. Change Sets Limitations 3. Di culty
the Main Chal- Keeping Environments in Sync 4.Lack of History Tracking 5. Di culty for Teams
lenges in the to Collaborate 6.No Standard Tool or Process for Managing Salesforce Changes
Salesforce Devel- 7.Limited Set of Quality Checks on Changes 8.Lack of Monitoring and Compliance
opment Lifecy- 9.The Struggle of Migrating Data from Multiple Objects 10.Di culty to Identify
cle? and Unblock Bottlenecks 11.Insu cient Quality and Frequency of Releases
15. 15
16. 16 What is Copa- Copado is a scalable Salesforce-native application that you can download and
do? install in an org. It provides you with a complete system to plan, track and carry out
, your DevOps activities. It also adds value in every stage of the Salesforce DevOps
process.
17. 17 What are the Here are some of the exciting features:
exciting features 1.Agile Implementation: Copado helps you leverage Agile methodologies to com-
of Copado? pose your releases and plan your sprints. 2.Quality Check: You can use the inbuilt
set of quality and compliance features to implement quality checks right from the
start of the development lifecycle.
3. Integration with Git: You can use Copado to implement seamless and e�ortless
integration with Git.
4. Easily Customizable: You can customize Copado e�ortlessly as it is a native
Salesforce app. Here are some of the actions you can perform on Copado to
personalize it for your speci c requirements
5. Add custom elds. Add validation rules. Implement approval processes. Modify
elds and sections to customize the page layouts to enhance the user experience.
18. 18 How Co- thorugh Pipelines -With pipelines, Copado comes to set order out of the chaos. A
pado Address- pipeline is a simple, graphical representation of the path that changes will follow
es the Devel- through the release process.
opment Lifecycle
Challenges
19. 19 What s An Copado uses a user story centric model. A user story is an element used in agile
User Story? How software development that contains the description of a requirement from an
an User Story is end-user perspective and relevant information about the changes to be imple-
Managed in Co- mented by developers. In Copado, it also holds the metadata related to those
pado? changes.
20. 20 How Piplines User stories will typically start in the lowest environments and get promoted to
are useful to an the next environments all the way to production, following the path described in
User story? the pipeline. The pipeline enables you to orchestrate your user story deployments
and verify that your quality standards are met.
Practice 2025/2026
1. 1 What Is Copa-
do?
2. 2 Standard Sales-
force Develop-
ment Lifecycle*
3. 3 What is De- DevOps is a combination of practices that automate and enable greater e�ec-
vops? tiveness in the process of building and running software. DevOps combines the
technical practices of Continuous Delivery with the business practices of lean
management and lean product development.
4. 4 What are the The rst thing you encounter is that there's not a clear overview of the whole
main Challenges process. You may have these questions
in Salesforce De- Where do changes happen?
velopment Life- Should I start in dev1, or can I implement my changes directly in production?
cycle? Which environment do I need to deploy rst?
Is it UAT or Integration?
Who is going to approve my changes?
5. 5 what are the Change Sets Limitations - Companies spend a lot of time building change sets.
limitations of the Here are some of the limitations of change sets that you should know:
change sets? 1.Change sets do not o�er the capability to search components by name or type.
As a developer, you are forced to browse through multiple pages to nd the
metadata items you want to select.
2.If you accidentally add a component, you cannot lter within your selections to
remove the component quickly.
3.Certain components are not available to be deployed using change sets, and it's
possible to move changes only across environments that are connected.
4.With change sets, all selected components come in a single list, so you can't
scope which modi cation is based on which request
, 5. Change sets do not enable continuous delivery, and automation of deployments
is not an easy task
6. 6 What are the dif- Release teams struggle with sandbox syncing after deploying to higher environ-
�culties Keeping ments. For example, if a company uses a hot x sandbox to develop and push
Environments in xes to production, lower environments will show discrepancies regarding the
Sync? production environment. These di�erences can lead to deployment errors and a
blocked pipeline. Even having multiple developer environments requires users to
keep those environments in sync.
7. 7 What are the 1. Metadata loss. All the work in progress in a sandbox will be overwritten after
Problems arise if the refresh.
we refresh the 2. Full sandboxes can only be refreshed once per month, therefore they can't easily
sandboxes.? receive changes that were sent from a hot x environment to production.
3. Scrambled emails. Whenever a sandbox is refreshed, user email addresses
are modi ed in the sandbox so that production users don't receive automatically
generated email messages from the sandbox. Hence, users are required to
validate an email address change in order to be able to log in again into the
sandbox. 4.Data loss. Unless you're refreshing a full sandbox or a partial copy,
you will lose all data. Hence, you need to recreate the test data all over again.
8. 8 What happens "There is a major issue when multiple developers work in the same environment
If multiple Devel- and perform changes in the same components. As mentioned in the Change Sets
opers working on Limitations section, when you work with change sets, you have no visibility on who
the same compo- has made what changes, and there are no tools for you to foresee if your changes
nents? will be overwritten.
9. 9 Why salesforce Salesforce makes it amazingly easy for individuals to build changes but it was
Deployment is not made with collaborations of large teams in mind. As your team grows, you
Di culty for the may nd it challenging to collaborate. Synchronizing environments, tracking the
teams to collabo- history, and being unable to merge changes on a line-by-line basis is di cult, so
rate? you are reducing your team's possibilities to collaborate and work together.
,10. 10 Is there Salesforce does not provide a de nitive recommendation on how to manage the
any Standard release process and doesn't include native Agile tools and metrics.
tool provided by
Salesforce for
the deployment
Process?
11. 11 Salesforce Salesforce provide only limited set of Quality Checks.
provide Quali-
ty Checks on
Changes?
12. 12 what is Apex tests are the only built-in Salesforce capability that ensures the quality of your
the built in customizations. Apex tests can identify speci c errors, but they are not meant to
Salesforce Quali- identify code ine ciencies and bad habits before they become a problem.
ty Check ?
13. 13 How the com- "There are also many other types of tests that go beyond what Apex alone o�ers
pany Make sure and can help ensure the quality of your team's work. To keep their code optimized,
the quality of companies have to make further e�orts in de ning and implementing a code
code? inspection process.
14. 14 What are 1. No Clear Overview of the Whole Process .2. Change Sets Limitations 3. Di culty
the Main Chal- Keeping Environments in Sync 4.Lack of History Tracking 5. Di culty for Teams
lenges in the to Collaborate 6.No Standard Tool or Process for Managing Salesforce Changes
Salesforce Devel- 7.Limited Set of Quality Checks on Changes 8.Lack of Monitoring and Compliance
opment Lifecy- 9.The Struggle of Migrating Data from Multiple Objects 10.Di culty to Identify
cle? and Unblock Bottlenecks 11.Insu cient Quality and Frequency of Releases
15. 15
16. 16 What is Copa- Copado is a scalable Salesforce-native application that you can download and
do? install in an org. It provides you with a complete system to plan, track and carry out
, your DevOps activities. It also adds value in every stage of the Salesforce DevOps
process.
17. 17 What are the Here are some of the exciting features:
exciting features 1.Agile Implementation: Copado helps you leverage Agile methodologies to com-
of Copado? pose your releases and plan your sprints. 2.Quality Check: You can use the inbuilt
set of quality and compliance features to implement quality checks right from the
start of the development lifecycle.
3. Integration with Git: You can use Copado to implement seamless and e�ortless
integration with Git.
4. Easily Customizable: You can customize Copado e�ortlessly as it is a native
Salesforce app. Here are some of the actions you can perform on Copado to
personalize it for your speci c requirements
5. Add custom elds. Add validation rules. Implement approval processes. Modify
elds and sections to customize the page layouts to enhance the user experience.
18. 18 How Co- thorugh Pipelines -With pipelines, Copado comes to set order out of the chaos. A
pado Address- pipeline is a simple, graphical representation of the path that changes will follow
es the Devel- through the release process.
opment Lifecycle
Challenges
19. 19 What s An Copado uses a user story centric model. A user story is an element used in agile
User Story? How software development that contains the description of a requirement from an
an User Story is end-user perspective and relevant information about the changes to be imple-
Managed in Co- mented by developers. In Copado, it also holds the metadata related to those
pado? changes.
20. 20 How Piplines User stories will typically start in the lowest environments and get promoted to
are useful to an the next environments all the way to production, following the path described in
User story? the pipeline. The pipeline enables you to orchestrate your user story deployments
and verify that your quality standards are met.
