Copado Certified illustrated solutions
1. What are some of the challenges in the development
lifecycle Copado helps address?: Limited set of quality checks.
Lack of monitoring and compliance.
The struggle of migrating data from multiple
objects. All are correct. (Correct)
2. Which of the following is an element that helps you track
changes but is not required in order to work with Copado?
Pipeline: Release
3. How can you access the feature branch in your Git repository
directly from a user story?: Using the link in the View in Git field.
4. What is the correct definition of promotion branch?: It is an
isolated branch that is created from the destination branch.
5. You can back-promote a user story that has not yet been
deployed to a higher environment.: False
6. How can you create a validation deployment of multiple
user stories?: - Create a Promotion record and add all the user
stories. Then, click on Create Deployment, flag the Validation Only
checkbox and click on Submit.
7. Dave has added a new field to the opportunity layout in the
dev3 sandbox. After committing the opportunity layout, the
user story displays a message indicating that the last commit
has no changes. What has Dave done wrong?-
: Dave has marked the opportunity layout as Retrieve Only in the
,metadata grid.
8. What is the quickest way to mass back-promote user stories
with Copa- do?: From the Pipeline page, click on Mass Back-Promote
and then click on Back Promote & Deploy.
9. Why would you flag an object as Retrieve Only when
committing changes on a user story?: You just want to update
FLS.
10.Which is TRUE when continuously using the Mass Back
Promotion fea- ture?: It reduces time by back promoting all the
user stories in bulk.
It reduces the possibility of getting a merge conflict.
It allows you to back promote the metadata changes without the
inconvenience of a sandbox refresh.
All are correct.(correct)
11.Debbie wants to check when was the last time a component
was commit- ted on the user story she is working on. Where
can she find this information? Select all that apply!: 1.)She can
navigate to the User Story selections section and check the Latest
Commit Date.
, 2.)She can navigate to the User Story Commits related list and check
the Commit Date.
12.Which of the following statements is TRUE?: The feature
branch that is created when you commit on a user story in dev is
reused by Copado when you deploy the user story to production.
13.By default, user story feature branches are merged into the
promotion branch based on:: The User Story Reference field of the
user story in ascending order.
14.Which is TRUE when using the Full Profiles & Permission
Sets Git oper- ation with a Profile in Copado: Active and disabled
system permissions and all the references to the related components
in the profile are committed.
15.Rob has tried to promote and deploy a user story with
changes in the HR profile, but he has received an email
notifying him that the promotion has failed. How can he
review the deployment errors?: Rob can navigate to the promotion
record from the User Story Promotions related list in the user story,
then open the related deployment and review the results in the failed
deployment step.
16.Turned off system permissions are retrieved when you
commit a profile using the Full Profiles & Permission Sets Git
operation.: True
17.What user stories can be back-promoted?: User stories where
1. What are some of the challenges in the development
lifecycle Copado helps address?: Limited set of quality checks.
Lack of monitoring and compliance.
The struggle of migrating data from multiple
objects. All are correct. (Correct)
2. Which of the following is an element that helps you track
changes but is not required in order to work with Copado?
Pipeline: Release
3. How can you access the feature branch in your Git repository
directly from a user story?: Using the link in the View in Git field.
4. What is the correct definition of promotion branch?: It is an
isolated branch that is created from the destination branch.
5. You can back-promote a user story that has not yet been
deployed to a higher environment.: False
6. How can you create a validation deployment of multiple
user stories?: - Create a Promotion record and add all the user
stories. Then, click on Create Deployment, flag the Validation Only
checkbox and click on Submit.
7. Dave has added a new field to the opportunity layout in the
dev3 sandbox. After committing the opportunity layout, the
user story displays a message indicating that the last commit
has no changes. What has Dave done wrong?-
: Dave has marked the opportunity layout as Retrieve Only in the
,metadata grid.
8. What is the quickest way to mass back-promote user stories
with Copa- do?: From the Pipeline page, click on Mass Back-Promote
and then click on Back Promote & Deploy.
9. Why would you flag an object as Retrieve Only when
committing changes on a user story?: You just want to update
FLS.
10.Which is TRUE when continuously using the Mass Back
Promotion fea- ture?: It reduces time by back promoting all the
user stories in bulk.
It reduces the possibility of getting a merge conflict.
It allows you to back promote the metadata changes without the
inconvenience of a sandbox refresh.
All are correct.(correct)
11.Debbie wants to check when was the last time a component
was commit- ted on the user story she is working on. Where
can she find this information? Select all that apply!: 1.)She can
navigate to the User Story selections section and check the Latest
Commit Date.
, 2.)She can navigate to the User Story Commits related list and check
the Commit Date.
12.Which of the following statements is TRUE?: The feature
branch that is created when you commit on a user story in dev is
reused by Copado when you deploy the user story to production.
13.By default, user story feature branches are merged into the
promotion branch based on:: The User Story Reference field of the
user story in ascending order.
14.Which is TRUE when using the Full Profiles & Permission
Sets Git oper- ation with a Profile in Copado: Active and disabled
system permissions and all the references to the related components
in the profile are committed.
15.Rob has tried to promote and deploy a user story with
changes in the HR profile, but he has received an email
notifying him that the promotion has failed. How can he
review the deployment errors?: Rob can navigate to the promotion
record from the User Story Promotions related list in the user story,
then open the related deployment and review the results in the failed
deployment step.
16.Turned off system permissions are retrieved when you
commit a profile using the Full Profiles & Permission Sets Git
operation.: True
17.What user stories can be back-promoted?: User stories where
