While working in Dev1 Debbie has committed a new custom field "Amount" and a validation rule
"Mandatory Amount" in the same user story. Later, during the sprint, the business analyst decided that the validation rule should not be included in this sprint but rather moved to the next sprint.
Nonetheless, the custom field must remain and be delivered in the current sprint. How can Debbie accomplish this?

• A.On the same user story, use the Destructive Changes Git operation to delete the validation rule.
• B.On the same user story, use the Recommit Files Git operation, check the Re-Create Feature Branch checkbox, deselect the validation rule and recommit.
• C.Delete the user story, create a new one and commit only the custom field as retrieve only this time.
• D.On the same user story, use the Recommit Files Git operation and deselect the validation rule.

Comment: *

Name: *

Email: *

Verification: *

You have been assigned the task of deleting a custom field. After deleting the custom field in a sandbox, you have created a user story to delete the field in Git and in upper environments, but you refreshed the medata grid before selecting the custom field. What can you do now in order to perform a destructive changes commit of the field? Select all that apply!

• A.Use the Org Credential lookup field on the Commit Changes page and find the component in another org.
• B.Change the Org Credential lookup field on the user story and find the component in another org.
• C.Use the Add Row button on the Commit Changes page and add the API name of the component.
• D.Change the base branch on the user story to locate the field in another branch

Comment: *

Name: *

Email: *

Verification: *

Where can you set the Maximum Static Code Analysis Score?

• A.In the User Story record.
• B.In the Environment record.
• C.In the Org Credential record.
• D.In the Pipeline record.

Comment: *

Name: *

Email: *

Verification: *

You would like to create a scratch org that has a duration of 15 days. Where can you set this value?

• A.In the user story.
• B.In the scratch org definition.
• C.In the extensions.
• D.In the project template

Comment: *

Name: *

Email: *

Verification: *

Dave would like to change the base branch on a user story from master to uat, but he can't see the Advanced button. As a Copado admin, what is the best way to fix this?

• A.Assigning Dave the Copado User managed permission set.
• B.Assigning Dave the System Admin profile.
• C.Assigning Dave the Edit User Story Commit Base Branch custom permission.
• D.Adding the Advanced button to the Commit Changes page layout.

Comment: *

Name: *

Email: *

Verification: *