Copado Copado-Developer 問題集

質問 1：
In a sandbox, you have made some changes in the System Admin profile. When you try to deploy the profile, you are getting the error "Unknown User Permission: ManageSandboxes." What can you do in order to move your changes forward? Select all that apply!
A. Update the .gitignore file in the uat branch to exclude the user permissions introduced in the higher API version and redeploy.
B. In the Git Promotion deployment step, use the Find and Replace feature to exclude the ManageSandboxes permission and redeploy.
C. Create a YAML file to exclude the ManageSandboxes permission, add it to the pipeline and redeploy.
D. Manually remove the ManageSandboxes permission from the destination branch and redeploy.
正解：B,C

質問 2：
Debbie and Dave were modifying the same Apex class on their individual sandboxes, Debbie deployed first without any issue, but when Dave tried to deploy, a Git conflict arose, so they teamed up and resolved it manually with Copado's online conflict resolution feature. What happens when both user stories are moved to the next environment?
A. Copado uses the conflict solution that was previously created.
B. Copado reports the conflict again and they need to fix it manually to be able to deploy.
C. The conflict is reported again but just as a warning. They are able to deploy.
D. No conflict is reported. Copado uses the auto-resolve conflict resolution feature to apply the changes from the latest deployment to the Apex class.
正解：A

質問 3：
You have created two different Account page layouts in Dev1, one for sales reps and and another one for the support team. You have committed the two page layouts on a user story and you are ready to deploy them to the next environment. However, the sales manager makes a last-minute decision for his team to continue using the standard Account page layout for now. What is the easiest way to prevent the sales reps layout from being deployed while deploying the support team layout?
A. Go to the user story and use the Destructive Changes Git operation to delete the sales reps layout. Then, use Commit Changes and just commit the layout for the support team.
B. Delete the user story, create a new one and commit just the layout for the support team.
C. Use the Recommit Files Git operation, flag the Create New Feature Branch checkbox and select only the layout for the support team.
D. Use the Recommit Files Git operation, flag the Re-Create Feature Branch checkbox and select only the layout for the support team.
正解：D

質問 4：
Debbie is deploying a user story with Apex components from UAT to production. The promotion test level on the user story is set to NoTestRun. What test level is going to be enforced in the deployment to production?
A. Run Specified Tests.
B. No Test Run.
C. Run Local Tests.
D. Run All Tests In Org
正解：C

質問 5：
Your company has multiple developers working in separate environments and sometimes your Apex classes get overwritten. What can you do to prevent this?
A. Activate the Online Conflict Resolution feature by removing Apex classes from the Exclude From Auto Resolve field in the Pipeline record
B. Activate the Online Conflict Resolution feature by including Apex classes in the Exclude From Auto Resolve field in the Pipeline record
C. Create a validation rule to prevent the same Apex component from being committed in different environments.
D. Activate Online Conflict Resolution feature by removing Apex classes from the Exclude From Auto Resolve field in the Promotion record.
正解：A

質問 6：
You have work in progress in dev1. After retrieving from the org and pushing a hotfix for your Admin profile from the Copado CLI, the validation deployment is failing. Why?
A. While pushing your changes from the CLI, Copado deploys the complete profile file which could contain references to other work in progress in dev1.
B. Copado has auto-resolved the Git conflict in the profile with changes that are not available in the feature branch.
C. The CLI push creates a deployment that includes the nested components in the profile file without including dependencies to work in progress.
D. Copado has auto-resolved the Git conflict in the profile with changes that are not available in the source environment.
正解：A

質問 7：
You have committed a custom field, but when you look at the feature branch, you don't see any updates. What do you need to check in order to troubleshoot the issue?
A. Verify if the field is excluded in the .gitignore file.
B. Verify if the field is excluded in an environment variable.
C. Verify if the field is excluded in the metadata filter of the org credential.
D. Verify if the field is excluded in a YAML.
正解：D