Copado Fundamentals I Certification Exam Guide

Copado Fundamentals I Certification is designed for users who don’t have a lot of knowledge about Copado. This certification introduces you to Copado and how Copado integrates with your repository, and covers basic Copado features such as commits, deployments and promotions.

1. What is Copado?

Copado is an end to end dev-ops solution built natively on Salesforce. Copado helps customer manage every part of the development lifecycle.

Copado key features:

Version Control & Backup – Identify changes in every release, schedule backups of metadata, and quickly restore previous versions
Connect Any Org – Deploy metadata between any sandbox, production, testing, or scratch org—and connect git repositories
Continuous Integration & Automation – Setup CI processes and deploy automatically on a schedule or by a webhook trigger
Team Collaboration & Sharing – Share changes with team members and ensure everyone is aligned with in-app chat and notifications

Copado supports dev-ops for:

Salesforce
Vlocity
Mulesoft
Heroku
Veeva
Ncino
Salesforce CPQ
Google Cloud
Cloudcraze
Clariti
Conga

2. About Copado Fundamentals I Certification Exam

Content: 30 multiple-choice/multiple-select questions
Time allotted to complete the exam: 60 minutes
Passing Score: 70% (21 Questions out of 30)
Prerequisites: none
Allowed Attempts: 2
Retake Registration fee: USD 250

Note: Copado’s Fundamentals I certification is an open book exam

3. Copado Fundamentals I Certification Exam Topics

Topic	Weightage
What is Copado	16%
Commit Changes	36%
Branching Strategy	13%
Promotion	20%
Back Promotion	15%

4. Important Topics for Copado Fundamentals I Certification Exam

4.1 What Is Copado – 16% (5 Questions)

Copado features
- Agile Implementation – helps leverage Agile methodologies to compose your releases and plan your sprints.
- Quality Check – use the inbuilt set of quality and compliance features to implement quality checks right from the start of the development lifecycle
- Integration with Git – implement seamless and effortless integration with Git.
- Easily Customisable – Salesforce native app

Value Stream Maps enables you to visualize your entire team as a flow and easily identify bottlenecks in your DevOps process
Static Code Analysis is a type of quality check that allows you to analyze your code to find inefficiencies and detect common errors in the code. Code analysis can be performed using PMD, CodeScan, or SonarQube.
Copado Compliance Hub – allows you to scan all the metadata changes made in your environments in order to spot and identify security breaches
Copado Data Deploy – create point-and-click data templates with no technical knowledge in order to build relational queries
Pipelines – a unidirectional flow that defines the order in which changes will be migrated, starting with the development orgs and finishing in a production org
Standard Development Lifecycle vs. Development Lifecycle with Copado

4.2 Commit Changes – 36% (11 Questions)

Credential: A credential is a connection between a user and a Salesforce environment. To work with Copado, you need to create a credential with your user in the org where Copado is installed. When creating a credential, the level of access is the same as the username used to authenticate the credential
User story: A user story is the smallest unit of work in an Agile framework. It’s an informal, general explanation of a software feature written from the perspective of the end-user or customer. In Copado, a user story is also used as a container object to develop, commit, promote, and deploy development work
Environment: An environment in Copado represents a Salesforce organization or instance of an application in other clouds such as Heroku or MuleSoft
Commit: A commit is a process used in Copado to link changes to a user story and record these changes in a Git repository. These committed changes will be later deployed to the different environments in your pipeline. Therefore, it is essential to commit just what you need
A project is a container of your user stories
A release lets you group user stories to promote them together and keep track of the version of changes that your application experiences after every deployment
A pipeline is a list of connections defining a path in which components will move through the release management process. Whenever you work with user stories under a project linked to a pipeline, Copado will know the next environment where to deploy
Commit changes
Commit incremental changes
Commit full profiles

4.3 Branching Strategy – 13% (4 Questions)

Copado branching strategy
- When a developer commits a change into their user story, Copado creates a feature branch for that user story. All the following commits in the same user story will be collected in the feature branch, which is taken out of master, so no ‘work in progress’ or other features are carried on with this feature branch
- Every time there is a user story commit, Copado merges that feature branch into the branch of the org where the developer was working, so that the org is kept in sync with the metadata in the branch
- You can monitor in the Copado Branch Management application page the differences between the current stage and the following one, and the user story feature branches get validated from both Git and Salesforce perspectives
- When you are running a promotion in Copado, Copado creates a promotion branch out of the destination branch (this is also known as ‘release branch’). This is an exact copy of the destination into which all the user stories included in the promotion will be merged. By doing this, we respect the original contents of the destination, while we add new contributions of developers to it; and we check if the user story feature branches can be merged all together
- If the merge has no conflicts or they are resolved automatically, then the deployment to destination takes place, and after a successful deployment, the promotion branch gets merged into the branch of the destination org, so user story commits finally reach the following stage

4.4 Promotion – 20% (6 Questions)

Promotion: A promotion is a container used to deploy one or multiple user stories from one environment to another following a designated pipeline
Feature branch: A feature branch is an auxiliary branch that Copado creates when you commit changes to a user story
Promotion Branch: A promotion branch is a branch created by Copado’s backend that combines the content in the feature branch with the content in the destination environment
Destination branch: A destination branch is a copy of the content included in the destination environment
Promote and deploy vs. promote
Promotion process
Promotion best practices

4.5 Back Promotion – 15% (4 Questions)

Purpose of Creating Back Promotions
- Keeps the Sandboxes in sync
- Propagates Hotfixes
Back promotion process.

Back promotion best practices
- Back promote only user stories that have been tested and approved
- Minimize the differences between sandboxes
- Keep sandboxes in sync
- Schedule a date and a time for the back promotion so that your team of developers knows when the process will be taking place