1.
Dave has committed a profile and a custom object on a user story. However, while reviewing the User Story selections grid, he can only see the profile there.
What could be the reason for this?
***He has committed the custom object as Retrieve Only since the object already exists in the destination environment.
He has clicked on Delete Git Selections in the User Story selections grid and the custom object has been deleted.
The User Story selections grid has not been refreshed. wrong
None are correct.
2.
What is an org credential?4
A connection between a specific user and a Git branch.
A Salesforce environment.
A connection to a Git repository.
A connection between a specific user and one Salesforce environment.
3.
What are some of the challenges in the development lifecycle Copado helps address?4
Limited set of quality checks.
Lack of monitoring and compliance.
The struggle of migrating data from multiple objects.
All are correct.
4.
When committing changes on a user story, where are these changes committed?3
They are committed to the source org branch.
The are committed to the promotion branch.
They are committed to the user story feature branch.
They are committed to the deployment branch.
5.
Debbie has created a new Promotion record and has added two user stories to the promotion. She is reviewing all the details,
but she cannot find the promotion branch. What could be the reason for this?
She needs to click on Submit Deployment first, and then the promotion branch will be created. wrong
*****She needs to click on Create Deployment first, and the promotion branch will then be created and will be visible in the Git Promotion step of the Deployment record.
The user stories have not been added correctly to the promotion.
She needs to click on Deploy All first, and then the promotion branch will be created.
6.
Which is NOT TRUE about Copado branching strategy?
If any conflicts are found during the merge, Copado can auto-resolve them following different strategies.
It automates the creation of the feature and promotion branches. wrong
If you want to remove user stories from a release, you will need to manually pick the commits from the promotion branch.******
It follows a naming convention for branches so that you can easily locate them in your repository.
7.
You have deployed a user story from dev1 to UAT to delete a layout. This layout was never back promoted to dev2, so you don't want this user story
to show up in the User Stories Behind count. How can you achieve this without losing information?3
Flag the Exclude from CBM checkbox in the Promoted User Story record.
Delete the user story.
Flag the Exclude from CBM checkbox in the user story record.
Link the user story to a project that does not have a pipeline associated.
8.
How can you promote a bunch of user stories all at once?1
You can flag the Ready to Promote checkbox on the user stories, create a Promotion record, add the user stories and deploy the promotion.
You can flag the Ready to Promote checkbox on the user stories, create a Deployment record, add the user stories and submit the deployment.
You can flag the Promote and Deploy checkbox on the user stories, create a Deployment record, add the user stories and submit the deployment.
You can flag the Promote and Deploy checkbox on the user stories, create a Promotion record, add the user stories and deploy the promotion.
9.
Ana is changing the existing ExternalId__c field. After completing the task in dev2 and committing the changes,
she realizes that she has forgotten to give the relevant profile access to this field. What should Ana do after granting the proper access?2
Nothing. Copado will handle the recommit process once access has been granted in dev2, so there is no need to recommit any changes.
Just recommit the required components. There is no need to refresh the metadata index because the field was already indexed in a previous task.
Open the commit changes page, refresh the metadata index, as there were new changes in the ExternalId custom field, and then, recommit the required components. wrong
10.
What is the correct definition of promotion branch?3
It is an isolated branch that is created out of the source org's branch.
It is an isolated branch that is created from the release branch.
It is an isolated branch that is created from the destination branch.
It is an isolated branch that is created from the feature branch.
11.
You have just committed the cases page layout on a user story, but there has been a last-minute change in the layout.
What is the easiest way to ensure you are deploying the layout with the latest changes?2
Perform destructive changes on the user story to remove the first version of the layout and commit the layout again.
Commit again the layout on the same user story.
In Git, modify the layout in the feature branch.
Commit the layout on a new user story.
12.
What Copado feature can you use to define criteria for automated deployments and quality checks?3
Selenium Automated Testing.
Mass Back Promotion.
Copado Continuous Delivery.
13.
Debbie has been working on a new feature. She hasn't been able to finish the task on time, so she will continue working on it tomorrow.
A daily back promotion process is scheduled at 8 pm. What risks should Debbie consider before the daily back promotion?1
Uncommitted changes in the destination org could be overwritten, so she should commit the work in progress.
Uncommitted changes in the destination branch are always overwritten, so she will need to commit the work in progress.
There are no risks when back promoting, she can continue working tomorrow.
14.
What is the quickest way to mass back-promote user stories with Copado?1
From the Pipeline page, click on Mass Back-Promote and then click on Back Promote & Deploy.
From the Pipeline page, click on the back arrow on each of the environments where there are user stories available to be back-promoted and then click on Back Promote.
From the Pipeline page, click on Mass Back-Promote and then click on Deploy. wrong
From the Pipeline page, click on the back arrow on each of the environments where there are user stories available to be back-promoted and then click on Back Promote & Deploy.
15.
A user is preparing a deployment to production. In order to save some time when deploying,
they would like to validate the deployment on Friday and make a quick deploy during the weekend. How can a quick deployment be made with Copado?3
By adding the @QuickDeploy parameter in the deployment name.
By validating the deployment and then navigating to the Deployment Status section in the destination org and performing a quick deploy from there.
By validating the deployment and deploying again from Copado after deactivating the CheckOnly checkbox.
All are correct.
16.
Your organization has started having scalability issues because the development team is not always following best practices when writting Apex classes.
Which tool would you use in order to detect this type of errors before they get into production?1
Static Code Analysis.
Compliance Hub.
Org Differences.
Selenium Automated Testing.
17.
When you create a pull request from a user story, which two branches are compared in the pull request?2
Always the feature branch and the master branch since the latter contains the production-ready version of your code.
The feature branch and the branch of the destination org.
The feature branch and the promotion branch.
The feature branch and the release branch.
18.
How can you perform a mass back promotion?3
From the Pipeline page, click on Back Promote & Deploy. Then, click on Deploy All.
From a Promotion record, flag the Mass Back-Promote checkbox. Then, select a source org and select the destination orgs. Finally, click on Create Deployment and Submit.
From the Pipeline page, click on Mass Back-Promote. Then, select a source org and a project. Finally, select the relevant user stories and click on Back Promote or Back Promote & Deploy.
On the Pipeline page, open the environment box. Then, click on Mass Back-Promote and select a project. Finally, select the relevant user stories and click on Back Promote or Back Promote & Deploy.
19.1
In the Copado model, each Salesforce environment is tied to a branch in the repository.
True
False
20.
What could be the reason why a commit would display a No changes status?
The latest commit has no differences compared to the source branch.wrong
The latest commit has no differences compared to the feature branch. correct
The latest commit has no differences compared to the master branch.
The latest commit has no differences compared to the destination branch.
21.
Which of the following statements is TRUE about the Ready to Promote checkbox?2
User stories flagged as Ready to Promote will be automatically deployed to the next environment.
User stories flagged as Ready to Promote will be available for promotion but will need to be manually deployed.
User stories flagged as Ready to Promote will be automatically back-promoted to lower environments.
User stories flagged as Ready to Promote will be available for selection in the Deployment record.
22.
Rob is reviewing the Pipeline Manager and realizes there are user stories in the Pipeline page that need to be back promoted to different
dev environments in order to keep environments in sync and reduce merge conflicts. How can Rob accomplish this?1
Leverage the Mass Back-Promote button to update all dev environments from integration with their respective missing user stories.
Push all the user stories to production and refresh all the sandboxes in the pipeline.
Have each DevOps resource replicate their work in each dev sandbox until they match.
23.
Under which columns of the metadata grid can you define filters with conditions?1
Name, Created By and Last Modified By.
Last Committed By, Created By and Last Modified By.
Last Modified Date and Created Date.
Type, Name and Created By.
24.
During the promotion process...4
The release branch is merged into the promotion branch.
The feature branch is merged into the destination branch.
The feature branch is merged into the source branch.
The feature branch is merged into the promotion branch.
25.
Which is TRUE when using the Full Profile & Permission Sets Git operation with a Profile in Copado?2
Active system permissions and all the references to the related components in the profile are committed.
Active and disabled system permissions and all the references to the related components in the profile are committed.
If the profile already exists in the feature branch, only active permissions are committed.
26.
You would like to migrate accounts and all their related contacts in one operation. What is the simplest way to do it with Copado?2
Commit the Account and Contact objects.
Create data templates for Accounts and Contacts.
You cannot migrate both accounts and contacts in a single operation.
Create an Apex script to migrate accounts and contacts.
27.
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?4
Rob can open the user story record and click on View Results.
Rob can navigate to the promotion record from the User Story Promotions related list in the user story, and click on view the deployment errors from the Promotion Error tab.
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.
Rob can open the user story record, then navigate to the Deployment related list and review the Deployment Errors field.
28.
What happens if you commit an existing field and a permission set in two different commits on the same user story?
FLS won't be updated in the permission set since both components should have been committed in the same commit.
FLS will be updated in the permission set only if the field is committed as Selected.
FLS will be updated in the permission set as both commits were made on the same user story. wrong
FLS won't be updated in the permission set if the field is committed as Selected. ***
29.
Ana has been asked to grant sales users FLS to the Account.Purchase_Amount__c field.
The field already exists in production, and she is not interested in committing any work in progress in the field.
What steps should Ana follow to commit FLS?2
Flag both the Sales Profile and the Account.Purchase_Amount__c CustomField as Selected.
Flag the Sales Profile as Selected and the Account.Purchase_Amount__c CustomField as Retrieve Only.
Flag the Sales Profile as Retrieve Only and the Account.Purchase_Amount__c CustomField as Selected.
Flag the Sales Profile as Selected and the Account CustomObject as Retrieve Only.
30.
Debbie has been working on a new object in the dev environment.
She has created a record type and 4 fields. What is the best way for her to commit these changes?2
Mark the object as Retrieve Only and the 4 fields and the record type as Selected.
Mark the object, the 4 fields and the record type as Selected.
Select only the object. Copado will carry over all the related nested components.
Select the object and the record type since Copado will commit the fields together with the properties of the object.
Dave has committed a profile and a custom object on a user story. However, while reviewing the User Story selections grid, he can only see the profile there.
What could be the reason for this?
***He has committed the custom object as Retrieve Only since the object already exists in the destination environment.
He has clicked on Delete Git Selections in the User Story selections grid and the custom object has been deleted.
The User Story selections grid has not been refreshed. wrong
None are correct.
2.
What is an org credential?4
A connection between a specific user and a Git branch.
A Salesforce environment.
A connection to a Git repository.
A connection between a specific user and one Salesforce environment.
3.
What are some of the challenges in the development lifecycle Copado helps address?4
Limited set of quality checks.
Lack of monitoring and compliance.
The struggle of migrating data from multiple objects.
All are correct.
4.
When committing changes on a user story, where are these changes committed?3
They are committed to the source org branch.
The are committed to the promotion branch.
They are committed to the user story feature branch.
They are committed to the deployment branch.
5.
Debbie has created a new Promotion record and has added two user stories to the promotion. She is reviewing all the details,
but she cannot find the promotion branch. What could be the reason for this?
She needs to click on Submit Deployment first, and then the promotion branch will be created. wrong
*****She needs to click on Create Deployment first, and the promotion branch will then be created and will be visible in the Git Promotion step of the Deployment record.
The user stories have not been added correctly to the promotion.
She needs to click on Deploy All first, and then the promotion branch will be created.
6.
Which is NOT TRUE about Copado branching strategy?
If any conflicts are found during the merge, Copado can auto-resolve them following different strategies.
It automates the creation of the feature and promotion branches. wrong
If you want to remove user stories from a release, you will need to manually pick the commits from the promotion branch.******
It follows a naming convention for branches so that you can easily locate them in your repository.
7.
You have deployed a user story from dev1 to UAT to delete a layout. This layout was never back promoted to dev2, so you don't want this user story
to show up in the User Stories Behind count. How can you achieve this without losing information?3
Flag the Exclude from CBM checkbox in the Promoted User Story record.
Delete the user story.
Flag the Exclude from CBM checkbox in the user story record.
Link the user story to a project that does not have a pipeline associated.
8.
How can you promote a bunch of user stories all at once?1
You can flag the Ready to Promote checkbox on the user stories, create a Promotion record, add the user stories and deploy the promotion.
You can flag the Ready to Promote checkbox on the user stories, create a Deployment record, add the user stories and submit the deployment.
You can flag the Promote and Deploy checkbox on the user stories, create a Deployment record, add the user stories and submit the deployment.
You can flag the Promote and Deploy checkbox on the user stories, create a Promotion record, add the user stories and deploy the promotion.
9.
Ana is changing the existing ExternalId__c field. After completing the task in dev2 and committing the changes,
she realizes that she has forgotten to give the relevant profile access to this field. What should Ana do after granting the proper access?2
Nothing. Copado will handle the recommit process once access has been granted in dev2, so there is no need to recommit any changes.
Just recommit the required components. There is no need to refresh the metadata index because the field was already indexed in a previous task.
Open the commit changes page, refresh the metadata index, as there were new changes in the ExternalId custom field, and then, recommit the required components. wrong
10.
What is the correct definition of promotion branch?3
It is an isolated branch that is created out of the source org's branch.
It is an isolated branch that is created from the release branch.
It is an isolated branch that is created from the destination branch.
It is an isolated branch that is created from the feature branch.
11.
You have just committed the cases page layout on a user story, but there has been a last-minute change in the layout.
What is the easiest way to ensure you are deploying the layout with the latest changes?2
Perform destructive changes on the user story to remove the first version of the layout and commit the layout again.
Commit again the layout on the same user story.
In Git, modify the layout in the feature branch.
Commit the layout on a new user story.
12.
What Copado feature can you use to define criteria for automated deployments and quality checks?3
Selenium Automated Testing.
Mass Back Promotion.
Copado Continuous Delivery.
13.
Debbie has been working on a new feature. She hasn't been able to finish the task on time, so she will continue working on it tomorrow.
A daily back promotion process is scheduled at 8 pm. What risks should Debbie consider before the daily back promotion?1
Uncommitted changes in the destination org could be overwritten, so she should commit the work in progress.
Uncommitted changes in the destination branch are always overwritten, so she will need to commit the work in progress.
There are no risks when back promoting, she can continue working tomorrow.
14.
What is the quickest way to mass back-promote user stories with Copado?1
From the Pipeline page, click on Mass Back-Promote and then click on Back Promote & Deploy.
From the Pipeline page, click on the back arrow on each of the environments where there are user stories available to be back-promoted and then click on Back Promote.
From the Pipeline page, click on Mass Back-Promote and then click on Deploy. wrong
From the Pipeline page, click on the back arrow on each of the environments where there are user stories available to be back-promoted and then click on Back Promote & Deploy.
15.
A user is preparing a deployment to production. In order to save some time when deploying,
they would like to validate the deployment on Friday and make a quick deploy during the weekend. How can a quick deployment be made with Copado?3
By adding the @QuickDeploy parameter in the deployment name.
By validating the deployment and then navigating to the Deployment Status section in the destination org and performing a quick deploy from there.
By validating the deployment and deploying again from Copado after deactivating the CheckOnly checkbox.
All are correct.
16.
Your organization has started having scalability issues because the development team is not always following best practices when writting Apex classes.
Which tool would you use in order to detect this type of errors before they get into production?1
Static Code Analysis.
Compliance Hub.
Org Differences.
Selenium Automated Testing.
17.
When you create a pull request from a user story, which two branches are compared in the pull request?2
Always the feature branch and the master branch since the latter contains the production-ready version of your code.
The feature branch and the branch of the destination org.
The feature branch and the promotion branch.
The feature branch and the release branch.
18.
How can you perform a mass back promotion?3
From the Pipeline page, click on Back Promote & Deploy. Then, click on Deploy All.
From a Promotion record, flag the Mass Back-Promote checkbox. Then, select a source org and select the destination orgs. Finally, click on Create Deployment and Submit.
From the Pipeline page, click on Mass Back-Promote. Then, select a source org and a project. Finally, select the relevant user stories and click on Back Promote or Back Promote & Deploy.
On the Pipeline page, open the environment box. Then, click on Mass Back-Promote and select a project. Finally, select the relevant user stories and click on Back Promote or Back Promote & Deploy.
19.1
In the Copado model, each Salesforce environment is tied to a branch in the repository.
True
False
20.
What could be the reason why a commit would display a No changes status?
The latest commit has no differences compared to the source branch.wrong
The latest commit has no differences compared to the feature branch. correct
The latest commit has no differences compared to the master branch.
The latest commit has no differences compared to the destination branch.
21.
Which of the following statements is TRUE about the Ready to Promote checkbox?2
User stories flagged as Ready to Promote will be automatically deployed to the next environment.
User stories flagged as Ready to Promote will be available for promotion but will need to be manually deployed.
User stories flagged as Ready to Promote will be automatically back-promoted to lower environments.
User stories flagged as Ready to Promote will be available for selection in the Deployment record.
22.
Rob is reviewing the Pipeline Manager and realizes there are user stories in the Pipeline page that need to be back promoted to different
dev environments in order to keep environments in sync and reduce merge conflicts. How can Rob accomplish this?1
Leverage the Mass Back-Promote button to update all dev environments from integration with their respective missing user stories.
Push all the user stories to production and refresh all the sandboxes in the pipeline.
Have each DevOps resource replicate their work in each dev sandbox until they match.
23.
Under which columns of the metadata grid can you define filters with conditions?1
Name, Created By and Last Modified By.
Last Committed By, Created By and Last Modified By.
Last Modified Date and Created Date.
Type, Name and Created By.
24.
During the promotion process...4
The release branch is merged into the promotion branch.
The feature branch is merged into the destination branch.
The feature branch is merged into the source branch.
The feature branch is merged into the promotion branch.
25.
Which is TRUE when using the Full Profile & Permission Sets Git operation with a Profile in Copado?2
Active system permissions and all the references to the related components in the profile are committed.
Active and disabled system permissions and all the references to the related components in the profile are committed.
If the profile already exists in the feature branch, only active permissions are committed.
26.
You would like to migrate accounts and all their related contacts in one operation. What is the simplest way to do it with Copado?2
Commit the Account and Contact objects.
Create data templates for Accounts and Contacts.
You cannot migrate both accounts and contacts in a single operation.
Create an Apex script to migrate accounts and contacts.
27.
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?4
Rob can open the user story record and click on View Results.
Rob can navigate to the promotion record from the User Story Promotions related list in the user story, and click on view the deployment errors from the Promotion Error tab.
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.
Rob can open the user story record, then navigate to the Deployment related list and review the Deployment Errors field.
28.
What happens if you commit an existing field and a permission set in two different commits on the same user story?
FLS won't be updated in the permission set since both components should have been committed in the same commit.
FLS will be updated in the permission set only if the field is committed as Selected.
FLS will be updated in the permission set as both commits were made on the same user story. wrong
FLS won't be updated in the permission set if the field is committed as Selected. ***
29.
Ana has been asked to grant sales users FLS to the Account.Purchase_Amount__c field.
The field already exists in production, and she is not interested in committing any work in progress in the field.
What steps should Ana follow to commit FLS?2
Flag both the Sales Profile and the Account.Purchase_Amount__c CustomField as Selected.
Flag the Sales Profile as Selected and the Account.Purchase_Amount__c CustomField as Retrieve Only.
Flag the Sales Profile as Retrieve Only and the Account.Purchase_Amount__c CustomField as Selected.
Flag the Sales Profile as Selected and the Account CustomObject as Retrieve Only.
30.
Debbie has been working on a new object in the dev environment.
She has created a record type and 4 fields. What is the best way for her to commit these changes?2
Mark the object as Retrieve Only and the 4 fields and the record type as Selected.
Mark the object, the 4 fields and the record type as Selected.
Select only the object. Copado will carry over all the related nested components.
Select the object and the record type since Copado will commit the fields together with the properties of the object.
Comments
Post a Comment