You are part of a test team that uses Microsoft Test Manager (MTM) on a project. The project uses the Microsoft Visual Studio Scrum 2013 process template.
Your test team constantly adds new test cases.
You need to create a test suite that automatically includes all test cases related to the Accounting section of the application.
What should you do?

• A. Create a requirements-based test suite that includes all requirements with an Area Path of Accounting.
• B. Create a new query for all test cases with an Area Path of Accounting, and then copy the resulting test cases into a new test suite.
• C. Create a static suite that includes all test cases, and use the Filter option to only show accounting-related test cases.
• D. Create a query-based test suite that selects all test cases with an Area Path of Accounting.

You develop a solution that is managed in Microsoft Visual Studio Team Foundation Server (TFS) source control using three branches according the following table.

The branch hierarchy is shown in the exhibit. (Click the Exhibit button.)

-----
A new project requires you to divide your team into two separate, and largely independent, teams named Feature Team 1 and Feature Team 2. Each team works on different features.
You need to recommend an effective long-term strategy that:
Allows parallel development,
Allows independent feature releases,
Minimizes conflicts,
Supports integration, and
Allows bug fixes to production code.
What should you do?

• A. Instruct both feature teams work off the DEV branch. The teams should only check in when they are ready to integrate.
• B. Create two branches off DEV named FB1 and FB2. Instruct Feature Team 1 to check-in to FB1 and Feature Team 2 to check-in to FB2. When a team is ready to integrate, FB1 or FB2 will be merged with DEV.
• C. Instruct Feature Team 1 to check in to the DEV branch and Feature Team 2 to check in to the MAIN branch. When the teams are ready to integration, the DEV branch will be merged into the MAIN branch.
• D. Create two new folders named FB1 and FB2 at the same level as the other branches. Instruct Feature Team 1 to check in to FB1 and Feature Team 2 to check in to FB2. When the teams are ready to integrate, perform baseless merges from FBI to DEV and FB2 to DEV.

Your company has a deployment of Microsoft Visual Studio Team Foundation Server (TFS), as well as a proxy server at a development site in a different country.
You need to ensure that the proxy server can communicate with the TFS at headquarters via your company WAN.
Which network port should you use?

• A. 8080
• B. 443
• C. 80
• D. 8081

Your network environment includes a Microsoft Visual Studio Team Foundation Server (TFS) 2012 server. Your development team is using the Microsoft Framework (MSF) for Agile Software Development 6.0 process template. You have a number of user stories logged in TFS
2012.
Several user stories have external dependencies on an application programming interface (API) that is being developed by a third party. The interfaces for the API have already been agreed upon.
You need to recommend how these external dependencies should be handled in your current sprint.
What should you do?

• A. Move all user stories that have dependencies on the API to the next sprint.
• B. Add a resource to represent the third party and assign all the user stories that have dependencies on the API to this new resource.
• C. Create mockups of the API using the agreed upon interfaces. Add user stories for integration testing to the backlog.
• D. Add an agreed upon amount of effort to every user story that has dependencies on the API.

A development team is attempting to use Scrum as its process framework. You join the
team as the new scrum master.
During a meeting, a developer states that his "task is done."
You need to describe to the team how the word "done" relates to Scrum.
What should you do?

• A. The word "done" indicates that code compiles and has been unit tested.
• B. The word "done" indicates that code has been approved for release to production.
• C. The word "done" must be defined, communicated, and agreed to by the team.
• D. The word "done" indicates that code has been approved through testing and quality assurance.