What happens with a component that is added to the .gitignore file and is later committed on a user
story?
Dave comitted a new method on the AccountOperations class but, after deploying his changes from
DEV to INT, he found his changes were not there due to an auto-resolved Git conflict he was not
aware of. What could he have done to prevent this from happening just in this particular promotion?
When you use the Recommit Files operation on a user story and flag the Re-Create Feature
Branch checkbox, what happens to the status of previous commit records on the same user story?
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?
Which of the following expressions is a correct regex expression that finds the value in the required tag of a field?
What happens when you use the Recommit Files Git operation and select the Re-Create Feature Branch checkbox? Select all that apply!
You have reached the max number of allowed answers
Rob, has set up the following connection behavior in UAT:
Dave, the lead developer, has committed an Apex class in dev1 and is going to deploy it to UAT.
What will happen once the user story is successfully deployed to UAT?
Rob, would like to enforce the following quality gates when deploying to INT:
* A static code analysis for all Apex classes and triggers.
* A validation deployment for all Apex classes and triggers.
* A validation deployment for profiles.
What is the easiest way for him to address these requirements?
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?
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?
Why the commits on a user story could display the status Commit not in branch?
Rob is deploying an important release from uat to production and would like to temporarily
freeze some users to ensure they don't make any changes during the release window that could have a negative impact on the release. What would be the easiest way to do this?