Copado Chapter 1 Exam Questions
With 100% Correct Answers.
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.
Creating a release is not required when working in Copado, but it will help you organize
your versions and track the app's progress. The release must be linked to a project.
Pipeline
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.
Promotion
A container used to deploy one or multiple user stories from one environment to
another following a designated pipeline.
Feature Branch
An auxiliary branch that Copado creates when you commit changes to a user story.
Is created out of the Destination branch, and is merged into the original environments branch.
The original feature branch is merged with the promotion branch up the pipeline
Promotion Branch
A branch created by Copado's backend that combines the content in the feature branch with the
content in the destination environment.
Created when the Deployment record is created
Destination Branch
, A copy of the content included in the destination environment.
Validation Deployment
Used to check the results of deploying components to the destination environment. If there is a
potential conflict, you can review the errors and fix them before actually deploying the changes.
Click Validate Changes on the user story or check Validation Only on the Deployment record
Version Control with Git
Tracks changes over time in a file or a set of files stored in a specific location, known as a
repository. With version control, every modification in a file is recorded along with
information about who made the change and its reason. It lets you control the different versions
of your source.
Git Branch
Commits are organized into branches. A branch collects versions of the files and the
commit history, which references the changes in these files over time. Branches can be
created for different purposes, e.g., a new feature, a new release, a new sandbox.
Master/Main Branch
This branch contains the production-ready version of your code delivered to your users.
Pull Request
Is an approval process before merging two branches so that the changes are introduced in a
controlled way.
Git Merge
It is the way to move a change (commit) from one branch to another. You can use merges during
the release process to move your modifications from the branch you are working on up into
production.
Git Repository
The place where file versions, branches and commits are stored.
With 100% Correct Answers.
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.
Creating a release is not required when working in Copado, but it will help you organize
your versions and track the app's progress. The release must be linked to a project.
Pipeline
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.
Promotion
A container used to deploy one or multiple user stories from one environment to
another following a designated pipeline.
Feature Branch
An auxiliary branch that Copado creates when you commit changes to a user story.
Is created out of the Destination branch, and is merged into the original environments branch.
The original feature branch is merged with the promotion branch up the pipeline
Promotion Branch
A branch created by Copado's backend that combines the content in the feature branch with the
content in the destination environment.
Created when the Deployment record is created
Destination Branch
, A copy of the content included in the destination environment.
Validation Deployment
Used to check the results of deploying components to the destination environment. If there is a
potential conflict, you can review the errors and fix them before actually deploying the changes.
Click Validate Changes on the user story or check Validation Only on the Deployment record
Version Control with Git
Tracks changes over time in a file or a set of files stored in a specific location, known as a
repository. With version control, every modification in a file is recorded along with
information about who made the change and its reason. It lets you control the different versions
of your source.
Git Branch
Commits are organized into branches. A branch collects versions of the files and the
commit history, which references the changes in these files over time. Branches can be
created for different purposes, e.g., a new feature, a new release, a new sandbox.
Master/Main Branch
This branch contains the production-ready version of your code delivered to your users.
Pull Request
Is an approval process before merging two branches so that the changes are introduced in a
controlled way.
Git Merge
It is the way to move a change (commit) from one branch to another. You can use merges during
the release process to move your modifications from the branch you are working on up into
production.
Git Repository
The place where file versions, branches and commits are stored.
