1. What is copado?
A - It's a scalable Salesforce-native platform that provides value in every stage of the Salesforce DevOps process.
B - It's a
... [Show More] new TI management methodology.
C - It's a series of online tutorials that teach you how to implement the Salesforce Dev-Ops process.
A
2. Which is NOT TRUE about Copado's integration with version control?
A - With Git, all changes are tracked.
B - It requires extensive knowleadge of Git.
C - Users with little knowledge of Git can leverage it.
B
3. Copado provides a conflict resolution engine that auto resolves Git conflicts in components.
A - True
B - False
A
4. How can Copado help you manage your releases in an agile way? (choose 2)
A - It provides you with built-in agile tools.
B - It includes a guide with agile practices.
C - It supports integration with external ALM systems.
A e C
5. What is TRUE about user stories?
A - User Stories establish a direct relationship between a change and its functional requirement.
B - They can be assigned to multiple developers.
C - Only admin users can delete user story records.
A
6. How does Copado solve the lack of compliance?
A - It includes a compliance hub tool that allows you to scan all the metadata changes made in your environments in order to find security breaches.
B - It sends users a list of all the changes so that they can review them and identify the ones that are non-compliant
A
7. What quality checking options does Copado offer out of the box?
A - Selenium testing.
B - Static Code Analysis.
C - Customization of the minimum apex coverage required.
D - All of the above
D
8. Ana the admin created a new external id field for the account object. When she tries to commit from the User Story commit page, she was unable to locate the field on the metadata grid. What should Ana do?
A - Ana should commit again from the correct User Story.
B - Ana should use the metadata filter to show only custom fields.
C - Ana should refresh the Metadata Index.
C
9. Ana added a new field to the account object in her sandbox. After refreshing the metadata index from commit changes page, the field is not showing on the grid.
A - Ana was committing from a User Story with an Org Credential different than the one for her sandbox.
B - Ana did not commit the correct field.
C - Ana did not refresh the metadata index.
A
10. Ana added a new field to the account layout in her sandbox. After committing the account layout , the User Story displayed a message indicating that the last commit had no changes.
A - The metadata Index was not refreshed.
B - Ana committed from the incorrect User Story.
C - Ana marked the account layout as "Retrieve Only " on the metadata grid.
C
11. After committing the account layout, the User Story shows a message indicating the last commit has no changes.
A - The account layout on the source org had no differences regarding the feature branch.
B - The user selected the wrong component.
C - The metadata Index was not refreshed.
A
12. Which is NOT True when using Promote and Deploy checkbox from a User Story?
A - You can only promote one User Story at a time.
B - A deployment record is automatically created and executed.
C - The promotion's status is updated while the deployment is being executed.
D - A deployment record is automatically created but the user needs to launch the Deployment.
D
13. After trying to Promote and Deploy a User Story with some changes in the Sales Profile, Rob received an email notifying him that the Promotion had failed. How can Rob review the Deployment Errors?
A - Navigate to the User Story Promotion record and from the Promotion error tab, click on view Deployment Errors
B - From the User Story record, navigate to the Deployment related list and review the Deployment errors field.
C - Open the User Story record, and Click and View Results.
D - Navigate to the User Story Promotion record, Open the related Deployment and review the results in the failed Deployment Step.
D
14. There are five new User Stories marked as Ready to Promote and ready to be promoted to the next environment. Rob has been asked to deploy all five from the dev1 environment to the UAT environment. What would be the best way to do this?
A - Create a Promotion record, select the first approved User Story and deploy the Promotion. Then repeat the same process for the remaining four User Stories.
B - Use the Promote and Deploy option and deploy the User Stories one by one.
C - Create a Promotion record, select the five approved User Stories and deploy the Promotion.
C
15. Ana has created a promotion and she's not able to find a User Story in the Available User Stories list. What should Ana check?
A - The User Story "Ready to Promote" checkbox is flagged.
B - The User Story has commits.
C - The User Story destination Org Credential is filled.
D - The User Story status has been set to "Ready to Promote".
A
16. When is the promotion branch created?
A - Once the User Story record is marked as "Ready to Promote".
B - Once the Promotion record is created and its status is set to Completed.
C - Once the Deployment record is launched.
D - Once the Deployment record is created.
D
17 - Dave has been working in the DEV 1 environment. Can you list the actions that will occur when Dave commits his changes in a User Story?
A - The Feature branch is created out of master. The Feature branch is merged into the Destination branch.
B - A Feature branch is created out of the Destination branch. The Feature branch is merged into the dev1 branch.
C - A Feature branch is created out of the master branch. The Feature branch is merged into the dev1 branch.
C
18. Rob has created a Promotion to include the team's User Stories planned for the Release. Once he has created the promotion, the Business asks him to exclude some features from the Release. What should Rob do in this case?
A - Delete the Feature branches related to those features.
B- Deselect the User Stories related to those features and submit a new Deployment.
C - Remove the commits related to those features from the Promotion branch.
B
19. Which of the following is NOT an advantage of Copado's Branching Strategy?
A - It eliminates manual work, since it automates the creation of feature branches and the merge process.
B - It's more flexible, as it allows the developed features to be isolated as long as they need to be.
C - It creates only one Release branch, so it reduces the number of branches in your repository.
D - You can link every change to a User Story so that you can document your changes with accuracy.
C
20. When Dave's User Story is deployed to Production environment, Copado reuses the same Feature branches that were created when he committed in Dev 1 environment.
A - True
B - False
TRUE [Show Less]