Free Microsoft 70-498 Exam Dumps Questions & Answers

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.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.
• B.Instruct both feature teams work off the DEV branch. The teams should only check in when they are ready to integrate.
• 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.
  -----

DRAG DROP
You are developing a new application that contains complicated validation and transformation logic on data pulled from three separate source systems.
You need to get feedback from your stakeholders to verify that your application meets their requirements before any other development tasks have been started. You also need to ensure that this application sub-system is correct before any other dependent module can be developed.
What should you do? (To answer, move the five appropriate actions from the list of actions to the answer area and arrange them in the correct order.)

Correct Answer:

You are the lead developer and architect of a development team that develops line of business (LOB) applications.
You need to define an architectural design process for the LOB applications.
Which three architectural goals and principles should you adopt? (Each correct answer presents a complete solution. Choose three.)

• A.Consider the team velocity.
• B.Model to analyze and reduce risk.
• C.Build to change, instead of building to last.
• D.Baseline the architecture to ensure consistency and minimize deviation.
• E.Use models and visualizations as a communication and collaboration tool.

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 can be used, but that IT will still have to provision test VMs.
• B.Explain that TFS Lab Management is a solution, but requires Hyper-V.
• 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 Standard Environments in Lab Management is a solution, but requires physical machines.

You manage a development team that has been assigned the task of developing a reporting application. The team holds a kickoff meeting with the stakeholders to document user requirements.
You review the draft requirements list that results from this meeting.
You need to indicate which requirements likely will require rework before you can send the requirements list to the development team.
Which three actions should you perform? (Each correct answer presents part of the solution. Choose three.)

• A.Identify requirements that depend on other requirements. These requirements likely will need to be split.
• B.Identify requirements that provide little business value. These requirements likely will need to be reconsidered.
• C.Identify requirements that do not have estimates. These requirements likely will need additional details before they can be approved.
• D.Identify requirements that cannot be tested easily. These requirements likely will need details to make them more testable.
• E.Identify requirements that are independent of other requirements. These requirements likely will need to be integrated with the other requirements.