Your team is setting up a test lab for the test team. Hyper-V is not the company
virtualization standard. You are in a planning meeting representing the development team. The information technology (IT) group indicates that they are reluctant to purchase a Hyper-V server and have limited resources available for maintaining test environments.
You need to suggest a solution for managing pre-production environments. What should you do?

• A. Explain that Standard Environments in Lab Management is a solution, but requires physical machines.
• B. Explain that Standard Environments in Lab Management can be used, but that IT will still have to provision test VMs.
• C. Explain that Lab Management is a solution and that IT will not need to be involved since Lab Management can be used to self provision test VMs.
• D. Explain that TFS Lab Management is a solution, but requires Hyper-V.

Your company is considering adopting the family of Microsoft Visual Studio 2012 features.
You need to identify which out-of-the-box features you could use to create an end-to-end application lifecycle management (ALM) solution.
Which three features should you use? (Each correct answer presents part of the solution. Choose three.)

• A. Time tracking and budget analysis
• B. Manual testing
• C. Deployment to production
• D. Unit testing and code coverage
• E. Requirements management

You are using the Microsoft Solution Framework (MSF) for Capability Maturity Model
Integration (CMMI) Process Improvement 6.0 process template.
A stakeholder has requested a change, but the change request has not received the
attention that it requires.
You need to escalate the change request. What should you do?

• A. Create a bug work item.
  Link the new bug to the change request.
  Escalate the bug to get the change request on track.
• B. Create an issue work item.
  Link the new issue to the change request.
  Escalate the issue to get the change request on track.
• C. Create another change request work item.
  Link the new change request to the change request.
  Escalate the change request to get the change request on track.
• D. Create an impediment work item.
  Link the new impediment to the change request.
  Escalate the impediment to get the change request on track.

You are using Microsoft Test Manager (MTM). Your development team is using Team Foundation Server (TFS) 2012 to associate requirements with source code and to automate builds.
Your team has been testing against an old build. You want to assign a more recent automated build to the test plan.
You need to review the requirements that have been affected between the current build and the new build before assigning it to your test plan.
What should you do?

• A. In the Properties View of the Plan activity, click Modify the Build In Use. Select the appropriate build in the Available builds. Review the Associated work items between selected builds list.
• B. Set up a check-in policy that will force an association of a work item to the changeset.
• C. In the Queries view of the Track activity, create a custom query that lists all requirements that have the Fixed in Build field set to the new build. Run the build and review the results.
• D. In the Assign Build view of the Track tab, click Modify. In Filter for builds, select the appropriate build to preview the list of work items.