Copado - Fundamentals - 1 Exam Questions and Answers Already Passed
1 What Is Copado? - Answers
2 Standard Salesforce Development Lifecycle* - Answers
3 What is Devops? - Answers DevOps is a combination of practices that automate and enable greater
effectiveness 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 What are the main Challenges in Salesforce Development Lifecycle? - Answers The first thing you
encounter is that there's not a clear overview of the whole process. You may have these questions
Where do changes happen?
Should I start in dev1, or can I implement my changes directly in production?
Which environment do I need to deploy first?
Is it UAT or Integration?
Who is going to approve my changes?
5 what are the limitations of the change sets? - Answers Change Sets Limitations - Companies spend a
lot of time building change sets. Here are some of the limitations of change sets that you should know:
1.Change sets do not offer the capability to search components by name or type. As a developer, you
are forced to browse through multiple pages to find the metadata items you want to select.
2.If you accidentally add a component, you cannot filter 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 modification
is based on which request
5. Change sets do not enable continuous delivery, and automation of deployments is not an easy task
6 What are the difficulties Keeping Environments in Sync? - Answers Release teams struggle with
sandbox syncing after deploying to higher environments. For example, if a company uses a hotfix
sandbox to develop and push fixes to production, lower environments will show discrepancies regarding
the production environment. These differences can lead to deployment errors and a blocked pipeline.
Even having multiple developer environments requires users to keep those environments in sync.
7 What are the Problems arise if we refresh the sandboxes.? - Answers 1. Metadata loss. All the work in
progress in a sandbox will be overwritten after the refresh.
,2. Full sandboxes can only be refreshed once per month, therefore they can't easily receive changes that
were sent from a hotfix environment to production.
3. Scrambled emails. Whenever a sandbox is refreshed, user email addresses are modified 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 What happens If multiple Developers working on the same components? - Answers "There is a major
issue when multiple developers work in the same environment and perform changes in the same
components. As mentioned in the Change Sets Limitations section, when you work with change sets, you
have no visibility on who has made what changes, and there are no tools for you to foresee if your
changes will be overwritten.
9 Why salesforce Deployment is Difficulty for the teams to collaborate? - Answers Salesforce makes it
amazingly easy for individuals to build changes but it was not made with collaborations of large teams in
mind. As your team grows, you may find it challenging to collaborate. Synchronizing environments,
tracking the history, and being unable to merge changes on a line-by-line basis is difficult, so you are
reducing your team's possibilities to collaborate and work together.
10 Is there any Standard tool provided by Salesforce for the deployment Process? - Answers Salesforce
does not provide a definitive recommendation on how to manage the release process and doesn't
include native Agile tools and metrics.
11 Salesforce provide Quality Checks on Changes? - Answers Salesforce provide only limited set of
Quality Checks.
12 what is the built in Salesforce Quality Check ? - Answers Apex tests are the only built-in Salesforce
capability that ensures the quality of your customizations. Apex tests can identify specific errors, but
they are not meant to identify code inefficiencies and bad habits before they become a problem.
13 How the company Make sure the quality of code? - Answers "There are also many other types of
tests that go beyond what Apex alone offers and can help ensure the quality of your team's work. To
keep their code optimized, companies have to make further efforts in defining and implementing a code
inspection process.
14 What are the Main Challenges in the Salesforce Development Lifecycle? - Answers 1. No Clear
Overview of the Whole Process .2. Change Sets Limitations 3. Difficulty Keeping Environments in Sync
4.Lack of History Tracking 5. Difficulty for Teams to Collaborate 6.No Standard Tool or Process for
Managing Salesforce Changes 7.Limited Set of Quality Checks on Changes 8.Lack of Monitoring and
Compliance 9.The Struggle of Migrating Data from Multiple Objects 10.Difficulty to Identify and Unblock
Bottlenecks 11.Insufficient Quality and Frequency of Releases
15 - Answers
, 16 What is Copado? - Answers Copado is a scalable Salesforce-native application that you can download
and 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 What are the exciting features of Copado? - Answers Here are some of the exciting features:
1.Agile Implementation: Copado helps you leverage Agile methodologies to compose 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 effortless integration with Git.
4. Easily Customizable: You can customize Copado effortlessly as it is a native Salesforce app. Here are
some of the actions you can perform on Copado to personalize it for your specific requirements
5. Add custom fields. Add validation rules. Implement approval processes. Modify fields and sections to
customize the page layouts to enhance the user experience.
18 How Copado Addresses the Development Lifecycle Challenges - Answers thorugh Pipelines -With
pipelines, Copado comes to set order out of the chaos. A pipeline is a simple, graphical representation of
the path that changes will follow through the release process.
19 What s An User Story? How an User Story is Managed in Copado? - Answers Copado uses a user story
centric model. A user story is an element used in agile software development that contains the
description of a requirement from an end-user perspective and relevant information about the changes
to be implemented by developers. In Copado, it also holds the metadata related to those changes.
20 How Piplines are useful to an User story? - Answers User stories will typically start in the lowest
environments and get promoted to the next environments all the way to production, following the path
described in the pipeline. The pipeline enables you to orchestrate your user story deployments and
verify that your quality standards are met.
21 How To build your continuous delivery pipeline? - Answers To build your continuous delivery
pipeline, you need to create pipeline connections and connect to your Salesforce environments Copado
will provide a set of templates to help you choose a starting point for your pipeline. If none of the
templates provided works for you, you can build your own template to suit your requirements as
pipelines are completely flexible..
22 What is the Use of Defining a Piplines? - Answers Defining a pipeline will help you later enforce best
practices through the release process. All the changes in your pipeline will go through each stage,
guaranteeing that they are properly integrated and tested so that no environment is skipped.
23 How Copado is integrated with Version Control? - Answers "1. After they have configured the
components in a dev environment, they will just need to access the User Story record and through a
user-friendly interface, select the components to commit. For ease of use, they can filter within the list
1 What Is Copado? - Answers
2 Standard Salesforce Development Lifecycle* - Answers
3 What is Devops? - Answers DevOps is a combination of practices that automate and enable greater
effectiveness 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 What are the main Challenges in Salesforce Development Lifecycle? - Answers The first thing you
encounter is that there's not a clear overview of the whole process. You may have these questions
Where do changes happen?
Should I start in dev1, or can I implement my changes directly in production?
Which environment do I need to deploy first?
Is it UAT or Integration?
Who is going to approve my changes?
5 what are the limitations of the change sets? - Answers Change Sets Limitations - Companies spend a
lot of time building change sets. Here are some of the limitations of change sets that you should know:
1.Change sets do not offer the capability to search components by name or type. As a developer, you
are forced to browse through multiple pages to find the metadata items you want to select.
2.If you accidentally add a component, you cannot filter 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 modification
is based on which request
5. Change sets do not enable continuous delivery, and automation of deployments is not an easy task
6 What are the difficulties Keeping Environments in Sync? - Answers Release teams struggle with
sandbox syncing after deploying to higher environments. For example, if a company uses a hotfix
sandbox to develop and push fixes to production, lower environments will show discrepancies regarding
the production environment. These differences can lead to deployment errors and a blocked pipeline.
Even having multiple developer environments requires users to keep those environments in sync.
7 What are the Problems arise if we refresh the sandboxes.? - Answers 1. Metadata loss. All the work in
progress in a sandbox will be overwritten after the refresh.
,2. Full sandboxes can only be refreshed once per month, therefore they can't easily receive changes that
were sent from a hotfix environment to production.
3. Scrambled emails. Whenever a sandbox is refreshed, user email addresses are modified 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 What happens If multiple Developers working on the same components? - Answers "There is a major
issue when multiple developers work in the same environment and perform changes in the same
components. As mentioned in the Change Sets Limitations section, when you work with change sets, you
have no visibility on who has made what changes, and there are no tools for you to foresee if your
changes will be overwritten.
9 Why salesforce Deployment is Difficulty for the teams to collaborate? - Answers Salesforce makes it
amazingly easy for individuals to build changes but it was not made with collaborations of large teams in
mind. As your team grows, you may find it challenging to collaborate. Synchronizing environments,
tracking the history, and being unable to merge changes on a line-by-line basis is difficult, so you are
reducing your team's possibilities to collaborate and work together.
10 Is there any Standard tool provided by Salesforce for the deployment Process? - Answers Salesforce
does not provide a definitive recommendation on how to manage the release process and doesn't
include native Agile tools and metrics.
11 Salesforce provide Quality Checks on Changes? - Answers Salesforce provide only limited set of
Quality Checks.
12 what is the built in Salesforce Quality Check ? - Answers Apex tests are the only built-in Salesforce
capability that ensures the quality of your customizations. Apex tests can identify specific errors, but
they are not meant to identify code inefficiencies and bad habits before they become a problem.
13 How the company Make sure the quality of code? - Answers "There are also many other types of
tests that go beyond what Apex alone offers and can help ensure the quality of your team's work. To
keep their code optimized, companies have to make further efforts in defining and implementing a code
inspection process.
14 What are the Main Challenges in the Salesforce Development Lifecycle? - Answers 1. No Clear
Overview of the Whole Process .2. Change Sets Limitations 3. Difficulty Keeping Environments in Sync
4.Lack of History Tracking 5. Difficulty for Teams to Collaborate 6.No Standard Tool or Process for
Managing Salesforce Changes 7.Limited Set of Quality Checks on Changes 8.Lack of Monitoring and
Compliance 9.The Struggle of Migrating Data from Multiple Objects 10.Difficulty to Identify and Unblock
Bottlenecks 11.Insufficient Quality and Frequency of Releases
15 - Answers
, 16 What is Copado? - Answers Copado is a scalable Salesforce-native application that you can download
and 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 What are the exciting features of Copado? - Answers Here are some of the exciting features:
1.Agile Implementation: Copado helps you leverage Agile methodologies to compose 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 effortless integration with Git.
4. Easily Customizable: You can customize Copado effortlessly as it is a native Salesforce app. Here are
some of the actions you can perform on Copado to personalize it for your specific requirements
5. Add custom fields. Add validation rules. Implement approval processes. Modify fields and sections to
customize the page layouts to enhance the user experience.
18 How Copado Addresses the Development Lifecycle Challenges - Answers thorugh Pipelines -With
pipelines, Copado comes to set order out of the chaos. A pipeline is a simple, graphical representation of
the path that changes will follow through the release process.
19 What s An User Story? How an User Story is Managed in Copado? - Answers Copado uses a user story
centric model. A user story is an element used in agile software development that contains the
description of a requirement from an end-user perspective and relevant information about the changes
to be implemented by developers. In Copado, it also holds the metadata related to those changes.
20 How Piplines are useful to an User story? - Answers User stories will typically start in the lowest
environments and get promoted to the next environments all the way to production, following the path
described in the pipeline. The pipeline enables you to orchestrate your user story deployments and
verify that your quality standards are met.
21 How To build your continuous delivery pipeline? - Answers To build your continuous delivery
pipeline, you need to create pipeline connections and connect to your Salesforce environments Copado
will provide a set of templates to help you choose a starting point for your pipeline. If none of the
templates provided works for you, you can build your own template to suit your requirements as
pipelines are completely flexible..
22 What is the Use of Defining a Piplines? - Answers Defining a pipeline will help you later enforce best
practices through the release process. All the changes in your pipeline will go through each stage,
guaranteeing that they are properly integrated and tested so that no environment is skipped.
23 How Copado is integrated with Version Control? - Answers "1. After they have configured the
components in a dev environment, they will just need to access the User Story record and through a
user-friendly interface, select the components to commit. For ease of use, they can filter within the list
