Recommit Files A git operation that enables you re recommit components, remove com-ponents from
User Story Selections, and re-create the user story feature branch Questions with Correct Answers
Question 1:
Re-Create Feature Branch
Answer:
checkbox that appears when Recom-mit files is selected as the git oper-ation. Used in cases where
metada-ta was committed by mistake or is no longer needed in the user sto-ry. When checked, existing
commits won't be present in the new feature branch and previous commit status will be 'Commit Not in
Branch'
Question 2:
**Ability to remove permissions to re-create feature branch via custom settings in setup. Custom
settings-’personal settings’manage’disable RCFB in US**
Recommit Files Flow: Re-Create Feature = FALSE
Recommit Files Flow: Re-Create Feature = TRUE
Commit the selected metadata components in the existing feature branch.
Answer:
Recommit Files Flow: Re-Create Feature = FALSE
Question 3:
If the feature branch is not found because it was deleted manually in the Git Repository, Copado will
auto-matically create a feature branch and commit the selected metadata.
Destructive Changes in Salesforce (w/o Copa-do)
Deleting and Components in a Deployment (w/o Copado)
Delete the existing feature branch in the Git repository.
Create a new feature branch.
Commit the selected metadata components.
To delete SF components, a
Answer:
Deleting and Components in a Deployment (w/o Copado)
Question 4:
delete manifest file named destruc-tiveChanges.xml must be included that contains all components to
be deleted. Also have to add an empty package.xml file that includes the API version in the same
directory as the manifest.
Salesforce will return an error when a component is deleted that is being referenced somewhere else.
Answer:
The best answer is the response that directly addresses the question stem.
Question 5:
-By default, deletions are processed before additions or updates.
-If there are any dependencies be-tween components, Salesforce al-lows you to perform both
operations in a single deployment and define its order of execution by using the
destructiveChangesPre.xml and de-structiveChangesPost.xml.
,Answer:
its order of execution by using the destructiveChangesPre.xml and de-structiveChangesPost.xml is the
key concept or process described in the course material.
Question 6:
Destructive Changes
Answer:
One of the Git Operations that you can choose from the Commit
Question 7:
Changes page that allows you to de-ploy component deletions
Answer:
Changes page that allows you to de-ploy component deletions
Question 8:
Destructive Changes Flow
Answer:
(1) Copado will create a feature branch. The selected component will be deleted in the feature branch
and then merged into the org's branch.
Question 9:
Copado will delete the entire file of the selected metadata in the org's branch if there is one.
If the selected components are referenced in other components, these references will also be delet-ed.
Answer:
The best answer is the response that directly addresses the question stem.
Question 10:
Deleted components flagged as Git Deletions in the User Story Selec-tions and any other updated
compo-nent if it was referencing the deleted component, flagged as Git Upserts.
Destructive Changes Flow: Component Exists in Master Branch
Answer:
The best answer is the response that directly addresses the question stem.
Question 11:
Destructive Changes Flow: Component DOES NOT Exists in Master Branch
A Git commit will be Completed successfully.
Answer:
The best answer is the response that directly addresses the question stem.
Question 12:
A feature branch carrying the dele-tion will be pushed to your repository.
A No Changes Git commit record will be created to the user story.
,Answer:
The best answer is the response that directly addresses the question stem.
Question 13:
No feature branch will be pushed to the repository.
NOTE: Copado allows you to enter
Answer:
The best answer is the response that directly addresses the question stem.
Question 14:
a ditterent base branch name to be used to generate the feature branch.
Answer:
a ditterent base branch name to be used to generate the feature branch.
Question 15:
Destructive Changes: Base Branch
Answer:
Decides where the feature branch is
Question 16:
created from
Answer:
created from
Question 17:
Destructive Changes: Credentials Lookup
Answer:
Field displayed after destructive
Question 18:
changes is selected. If a ditterent cre-dential is selected in the lookup field, the metadata grid will
display meta-data indexed from the selected cre-dential
Answer:
The best answer is the response that directly addresses the question stem.
Question 19:
Destructive Changes: Add Row Button
Answer:
Used to find metadata that has al-
, Question 20:
ready been deleted. User inputs API name and metadata type
Answer:
ready been deleted. User inputs API name and metadata type
Question 21:
Git Conflict (Merge Conflict)
Answer:
When merging two branches that have the same files, but one or more lines in the files have been
updated with ditterent values in each branch. Git requires your help to determine which changes
should be incorporat-ed into the final merge.
Question 22:
Copado Merge Order
Answer:
merge order of the User Stories into the Promotion branch is based on the User Story name field in
ascend-ing order. From Copado V12, you can override the default name order and define a custom
merge order, based on a ditterent user story field with asc or desc order.
Question 23:
Two Types of Conflict Resolution Processes
Answer:
Automatic and Manual
Question 24:
Automatic Conflict Resolution To save you the manual work of resolving the conflicted files, Copado
provides you with the Auto Resolve feature. De-pending on the type of file, Copa-do will apply a
ditterent auto-resolve conflict strategy.
Manual Conflict Resolution Copado allows you to manually resolve file conflicts during the User Story
pro-motion process with the Online Con-flict Resolution feature.
Answer:
The best answer is the response that directly addresses the question stem.
Question 25:
Components to Exclude from Auto Resolve
Answer:
ApexClass, ApexComponent, Apex-
Question 26:
Page, ApexTrigger and Layout
Answer:
Page, ApexTrigger and Layout
User Story Selections, and re-create the user story feature branch Questions with Correct Answers
Question 1:
Re-Create Feature Branch
Answer:
checkbox that appears when Recom-mit files is selected as the git oper-ation. Used in cases where
metada-ta was committed by mistake or is no longer needed in the user sto-ry. When checked, existing
commits won't be present in the new feature branch and previous commit status will be 'Commit Not in
Branch'
Question 2:
**Ability to remove permissions to re-create feature branch via custom settings in setup. Custom
settings-’personal settings’manage’disable RCFB in US**
Recommit Files Flow: Re-Create Feature = FALSE
Recommit Files Flow: Re-Create Feature = TRUE
Commit the selected metadata components in the existing feature branch.
Answer:
Recommit Files Flow: Re-Create Feature = FALSE
Question 3:
If the feature branch is not found because it was deleted manually in the Git Repository, Copado will
auto-matically create a feature branch and commit the selected metadata.
Destructive Changes in Salesforce (w/o Copa-do)
Deleting and Components in a Deployment (w/o Copado)
Delete the existing feature branch in the Git repository.
Create a new feature branch.
Commit the selected metadata components.
To delete SF components, a
Answer:
Deleting and Components in a Deployment (w/o Copado)
Question 4:
delete manifest file named destruc-tiveChanges.xml must be included that contains all components to
be deleted. Also have to add an empty package.xml file that includes the API version in the same
directory as the manifest.
Salesforce will return an error when a component is deleted that is being referenced somewhere else.
Answer:
The best answer is the response that directly addresses the question stem.
Question 5:
-By default, deletions are processed before additions or updates.
-If there are any dependencies be-tween components, Salesforce al-lows you to perform both
operations in a single deployment and define its order of execution by using the
destructiveChangesPre.xml and de-structiveChangesPost.xml.
,Answer:
its order of execution by using the destructiveChangesPre.xml and de-structiveChangesPost.xml is the
key concept or process described in the course material.
Question 6:
Destructive Changes
Answer:
One of the Git Operations that you can choose from the Commit
Question 7:
Changes page that allows you to de-ploy component deletions
Answer:
Changes page that allows you to de-ploy component deletions
Question 8:
Destructive Changes Flow
Answer:
(1) Copado will create a feature branch. The selected component will be deleted in the feature branch
and then merged into the org's branch.
Question 9:
Copado will delete the entire file of the selected metadata in the org's branch if there is one.
If the selected components are referenced in other components, these references will also be delet-ed.
Answer:
The best answer is the response that directly addresses the question stem.
Question 10:
Deleted components flagged as Git Deletions in the User Story Selec-tions and any other updated
compo-nent if it was referencing the deleted component, flagged as Git Upserts.
Destructive Changes Flow: Component Exists in Master Branch
Answer:
The best answer is the response that directly addresses the question stem.
Question 11:
Destructive Changes Flow: Component DOES NOT Exists in Master Branch
A Git commit will be Completed successfully.
Answer:
The best answer is the response that directly addresses the question stem.
Question 12:
A feature branch carrying the dele-tion will be pushed to your repository.
A No Changes Git commit record will be created to the user story.
,Answer:
The best answer is the response that directly addresses the question stem.
Question 13:
No feature branch will be pushed to the repository.
NOTE: Copado allows you to enter
Answer:
The best answer is the response that directly addresses the question stem.
Question 14:
a ditterent base branch name to be used to generate the feature branch.
Answer:
a ditterent base branch name to be used to generate the feature branch.
Question 15:
Destructive Changes: Base Branch
Answer:
Decides where the feature branch is
Question 16:
created from
Answer:
created from
Question 17:
Destructive Changes: Credentials Lookup
Answer:
Field displayed after destructive
Question 18:
changes is selected. If a ditterent cre-dential is selected in the lookup field, the metadata grid will
display meta-data indexed from the selected cre-dential
Answer:
The best answer is the response that directly addresses the question stem.
Question 19:
Destructive Changes: Add Row Button
Answer:
Used to find metadata that has al-
, Question 20:
ready been deleted. User inputs API name and metadata type
Answer:
ready been deleted. User inputs API name and metadata type
Question 21:
Git Conflict (Merge Conflict)
Answer:
When merging two branches that have the same files, but one or more lines in the files have been
updated with ditterent values in each branch. Git requires your help to determine which changes
should be incorporat-ed into the final merge.
Question 22:
Copado Merge Order
Answer:
merge order of the User Stories into the Promotion branch is based on the User Story name field in
ascend-ing order. From Copado V12, you can override the default name order and define a custom
merge order, based on a ditterent user story field with asc or desc order.
Question 23:
Two Types of Conflict Resolution Processes
Answer:
Automatic and Manual
Question 24:
Automatic Conflict Resolution To save you the manual work of resolving the conflicted files, Copado
provides you with the Auto Resolve feature. De-pending on the type of file, Copa-do will apply a
ditterent auto-resolve conflict strategy.
Manual Conflict Resolution Copado allows you to manually resolve file conflicts during the User Story
pro-motion process with the Online Con-flict Resolution feature.
Answer:
The best answer is the response that directly addresses the question stem.
Question 25:
Components to Exclude from Auto Resolve
Answer:
ApexClass, ApexComponent, Apex-
Question 26:
Page, ApexTrigger and Layout
Answer:
Page, ApexTrigger and Layout
