Home » Microsoft » 70-498 » Which three actions should you perform?
You are a technical team lead. Your company network includes a Microsoft Visual Studio Team Foundation Server (TFS) 2012 server.
You are assigned to work on a project with an internal development team and an off-site vendor who is new to working with your company.
You need to ensure that the code delivered by the off-site vendor is of an acceptable quality, conforms to standards, and does not affect production support.
Which three actions should you perform? (Each correct answer presents a complete solution. Choose three.)
A. Implement custom and standard check-in policies to force compliance to standards, passing of unit tests, and running static code analysis.
B. Implement a branching and permissions strategy that isolates vendor changes.
C. Implement an email alert that is triggered when the off-site vendor’s developers check in code.
D. Implement a gated check-in build.
E. Implement a policy requiring developers to shelve their changes at the end of each day.
Correct Answer: ABD
Explanation/Reference:
A: Administrators of Team Foundation version control can add check-in policy requirements. These check-in policies require the user to take actions when they conduct a check-in to source control, for example a user can be required to associate a work item with a changeset.
B: The following are examples of scenarios where you might need to create branches and perform merges:
* If you are having regular problems with broken builds, you should create a development branch to isolate parallel development efforts.
* If you have features that are causing stability issues, or teams causing stability issues among each other, create separate feature or team branches beneath a development container folder in source control.
D: When a developer checks in changes that break the build, the result can be a significant hassle for small teams. The cost to larger teams can be even more expensive when measured by lost productivity and schedule delays. You can guard some or all of your code base against these problems by creating a gated check-in build definition.
Reference: Visual Studio 2013, Use a gated check-in build process to validate changes; Add Check-In Policies
