70-498 Exam
What tells you about 70-498 syllabus
Want to know Ucertify 70-498 Exam practice test features? Want to lear more about Microsoft Delivering Continuous Value with Visual Studio 2012 Application Lifecycle Management certification experience? Study Highest Quality Microsoft 70-498 answers to Down to date 70-498 questions at Ucertify. Gat a success with an absolute guarantee to pass Microsoft 70-498 (Delivering Continuous Value with Visual Studio 2012 Application Lifecycle Management) test on your first attempt.
2021 Sep testking 70-498:
Q1. You have a web application that should be automatically deployed to a standard environment, including two staging web servers. You USE the LabDefaultTemplate.11.xaml build process template for your build definition.
You plan to run automated tests on the application as part of the build process. You need to configure the build definition to deploy the application.
What should you do?
A. Create deployment scripts to perform the deployment. In the Deploy section of the build process template, select Deploy the build and specify the computer names and the scripts to be executed.
B. In the build definition, specify the MS Build arguments as /p:DeployOnBuild=true;DeployTargetPackage.
C. Define separate drop folders for each web server.
D. In the build definition, specify Private Drop Location. Indicate the scripts to be executed after a successful build.
Answer: A
Q2. You manage a software development project that includes multiple feature teams. The teams integrate their code into a shared code repository as frequently as possible.
You plan to configure a build definition by using the default build process template (DefaultTemplate.xaml).
You need to know when a check-in from a feature team has broken the build or caused a test to fail, without impacting the feature team.
What should you do?
A. Set the Analyze Test Impact parameter to True in the build process template.
B. Set the build trigger to Continuous Integration and enable automated testing.
C. Add the Builds check-in policy to your team project.
D. Create a shelveset command for pending changes. Queue a build using the latest source with the shelveset parameter.
Answer: B
Q3. You are a scrum master.
You need to lead the daily scrum meeting.
Which three questions should you ask? (Each correct answer presents part of the solution. Choose three.)
A. What will be done before the next meeting?
B. What went well?
C. What has been accomplished since the last meeting?
D. Are there any potential improvements?
E. What obstacles are in the way?
F. Is the burndown up to date?
Answer: ACE
Explanation: The most popular technique that Development Teams use during the Daily Scrum is to stand in a circle facing each other. Each developer, in turn, answers the following three questions:
1. What have I done since the last Scrum?
2. What will I do between now and the next Scrum?
3. What impediments are in my way?
Professional Scrum Development with Microsoft Visual Studio 2012 p.21
Q4. DRAG DROP
You have a list of tasks entered into Microsoft Visual Studio Team Foundation Server (TFS) 2012. Each task has an estimated effort and assigned to a team member.
You have limited resources available. Due to external requirements, the start date and end date of the current iteration are fixed. Several of the tasks have dependencies on one another.
You need to identify a critical path.
What should you do? (To answer, move the three appropriate actions from the list of actions to the answer area and arrange them in the correct order.)
Answer:
Q5. You manage several developers who are working on multiple applications.
A business analyst requests an audit trail of work item changes for all prospective releases.
You need to implement a strategy to provide the audit trail.
Which two actions should you perform? (Each correct answer presents part of the solution. Choose two.)
A. Enable a check-in policy that requires a successful build prior to check-in.
B. Enable a check-in policy that requires a work item be associated with the check-in.
C. Enable static code analysis during the automated build.
D. Require developers to update the comments field of their tasks with details of any code changes for their tasks.
E. Request that developers enter the work item ID in the check-in comments for any code changes they make.
F. Enable the automated build option to associate work items with the build.
Answer: BF
Most up-to-date 70-498 questions:
Q6. Your development team uses the Microsoft Visual Studio Scrum 2.0 process template. You are the product owner.
Your product backlog includes a number of items that appear to have equal priority. However, the items have differing business value, complexity, and risk.
You need to order the backlog based on risk, complexity, and business value.
What should you do?
A. Work on items with the highest ratio of business value to effort first.
B. Work on items that have the highest effort first.
C. Work on items that have the lowest effort first.
D. Assign a risk factor to each product backlog item and work on items with the highest risk factor first.
E. Work on items that have the highest business value first.
Answer: A
Explanation: The Product Backlog should be ordered by the Product Owner to maximize the value of the software being developed. He or she will know what features and bug fixes need to be developed before others. Release planning depends on the backlog being correctly ordered. The order can be based on many factors: business value, risk, priority, technical value, learning value, or necessity. Items at a higher order are clearer and more detailed than lower-ordered ones. Effort estimates are more accurate on these items as well. In fact, the higher the order, the more a PBI or bug has been considered, and the consensus is greater regarding it, its value, and its cost.
Professional Scrum Development with Microsoft Visual Studio 2012 p.156
Q7. 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. Add a resource to represent the third party and assign all the user stories that have dependencies on the API to this new resource.
B. Add an agreed upon amount of effort to every user story that has dependencies on the API.
C. Move all user stories that have dependencies on the API to the next sprint.
D. Create mockups of the API using the agreed upon interfaces. Add user stories for integration testing to the backlog.
Answer: D
Q8. You are using the Microsoft Framework (MSF) for Capability Maturity Model Integration (CMMI) Process Improvement 6.0 process template.
You are the scrum master.
You need to assign product requirements to an iteration.
Which three actions should you perform? (Each correct answer presents part of the solution. Choose three.)
A. Create a test harness to confirm that the business requirements are understood.
B. Find the dependencies among the product requirements.
C. Prioritize each of the requirements.
D. Create a prototype to validate whether or not the requirement can be accomplished.
E. Estimate the cost of each of the requirements.
Answer: BCE
Q9. You manage a development team by using Microsoft Team Foundation Server (TFS) 2012. The development team is made up of developers with specific skills.
The project you are developing has the following characteristics:
Several external dependencies exist.
Requirements are well defined and will not change.
If an external dependency on the critical path does not meet a committed to deadline, the project will be impacted.
The impact should be identified and measured.
You need to select the appropriate tool(s) for managing the project.
What should you do?
A. Use Microsoft Project to manage dependencies and integrate with TFS where needed.
B. Use TFS with the Microsoft Visual Studio Scrum 2.0 project template.
C. Use TFS with the Microsoft Solution Framework (MSF) for Capability Maturity Model Integration (CMMI) Process Improvement 6.0 project template and the Affects link type for managing dependencies.
D. Use TFS with the MSF for Agile Software Development 6.0 process template and the web access task board.
Answer: A
Q10. A development team in your company has been unsuccessful delivering software by its deadline. You join the team as its new scrum master.
The previous scrum master did not understand the importance of the length of a sprint.
You need to define how long the sprints should be.
Which two factors should you consider to determine sprint length? (Each correct answer presents part of the solution. Choose two.)
A. The iteration length should be long enough to ensure than no more than 20 percent of the total effort is spent performing deployment and administrative tasks.
B. The iteration length should be consistent.
C. The iteration length should be flexible.
D. The sprint length should be long enough to create a usable and potentially releasable product.
E. The iteration length should be longer than one month.
Answer: BD
Explanation: Sprint length I asked Ken Schwaber once how long a Sprint should be. His answer was, “As short as possible and no shorter.” Sprints of longer than four weeks (one month) have a smell—the smell of water falling. When a Sprint’s length is longer than a month, the definition of what is being built may change or complexity and risk may increase. By limiting the maximum length of a Sprint, at most one month of development effort would be wasted, rather than several months in a classic waterfall project. Conversely, Sprints with a length of less than one week are possible, but should be executed only by a high-performance Scrum Team. Even with very short Sprints, the overhead of the inner events must be factored in, leaving even less time for actual software development. Teams working in ”micro sprints” like these need to be on their A-game every day. Ideally, the length of the Sprint does not change. If it must, it can only change in between Sprints, as a result of a decision made collaboratively during the prior Sprint’s retrospective meeting. Any change to the length of a Sprint will cause disruption to the Development Team’s cadence. This will correct over time, as will its Velocity.
Professional Scrum Development with Microsoft Visual Studio 2012 p.15