Copado Copado-Developer 問題集

質問 1：
After pushing changes using the Copado CLI, you notice that the feature branch is being merged to a different environment branch in your remote repository. What could be the reason behind this?
A. The Copado CLI push command doesn't trigger the merge of the feature branch with the promotion branch.
B. The Copado CLI push command doesn't trigger the merge of the feature branch with the environment branch.
C. Copado doesn't merge the feature branch with the environment source branch.
D. The environment and org credential of the related user story were accidentally changed to a different one.(Not Sure)
正解：D

質問 2：
The development team is complaining that when they try to select a metadata source in the scratch org wizard, they can only see Branches. Developers should be able to select any metadata source.
How you can fix this?
A. Set the Copado DX Mode picklist field in the Pipeline record to 'All Metadata Sources'.
B. Set the Copado DX Mode picklist field in the Pipeline record to 'None'.
C. Give the developer profile the correct object level permissions to all metadata sources.
D. Set the Copado DX Mode picklist field to 'Branches' in all the environments.
正解：B

質問 3：
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
正解：C,D

質問 4：
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

質問 5：
Why the commits on a user story could display the status Commit not in branch?
A. Someone has used the Re-Create Feature Branch on the user story
B. The committed component had no changes compared to the master branch.
C. The commit process failed.
D. Someone has deleted the commits directly in the feature branch.
正解：A

質問 6：
Which of the following examples could potentially create a Git conflict?
A. B and C.
B. Merge the feature branch into the source org's branch.
C. Merge the feature branch into the promotion branch.
D. Merge the release branch into the destination branch.
正解：A

質問 7：
In Dev1, Debbie has added a new method to an Apex class. She has committed the user story and deployed the user story to UAT. In Dev2, Dave has added a method to the same class and has deployed the changes to UAT. This has reported a conflict, so Dave has teamed up with Debbie and resolved it manually. What happens when the user stories are moved to the next environment?
A. There is no Git conflict since Copado has already stored the solution to the conflict.
B. The conflict is reported again and they need to fix it manually in order to be able to deploy.
C. The conflict is reported again but just as a warning. They can 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.
正解：D