Free Microsoft 70-496 Exam Practice Questions & Explanations
Prepared & Reviewed by the ValidExamDumps Editorial Team
At ValidExamDumps, we consistently monitor updates to the Microsoft 70-496 exam questions by Microsoft. Whenever our team identifies changes in the exam questions, objectives, focus areas or requirements, We immediately update our exam questions for both PDF and online practice exams. This commitment ensures our customers always have access to the most current and accurate questions. By preparing with these up to date and 100% exam domain coverage questions, our customers can successfully pass the Microsoft Administering Visual Studio Team Foundation Server 2012 exam on their first attempt without needing additional materials or study guides.
Other certification materials providers often include outdated or removed questions by Microsoft in their 70-496 exam. These outdated questions lead to customers failing their Microsoft Administering Visual Studio Team Foundation Server 2012 exam. In contrast, we ensure our questions bank includes only precise and up-to-date questions. Our main priority is your success in the Microsoft 70-496 exam, not profiting from selling obsolete exam questions in PDF or Online Practice Test.
Your TFS 2012 administrator plans a disaster recovery strategy. She configures the SQL Server databases (configuration, collection, warehouse, and Analysis Services) for backup using the Create Backup Schedule wizard in the TFS Administration Console, and relies on that alone to be able to restore a working deployment to new hardware.
Statement: Before the Create Backup Schedule wizard can be used, a network share must be available and the account running the backups must have permissions on both the share and the SQL Server instance, and the wizard will also create marked transactions across the TFS databases to keep them synchronized.
True. The Create Backup Schedule wizard (part of the TFS 2012 Administration Console Scheduled Backups node) requires a network share for the backup files, and the account used must have read/write access to that share as well as the required SQL Server privileges. A key benefit of the wizard is that it uses marked transactions written across all TFS databases so that full, differential, and transaction log backups can be restored to a consistent point in time, keeping the configuration and collection databases synchronized.
Developers report that when they check in code that fails a check-in policy, they are able to override the policy and complete the check-in. Management wants developers to be prevented from overriding check-in policies in the ProjectAlpha team project, while the build service account must retain full flexibility.
What should you do?
Version control policy override is governed by the item-level permission "Override check-in policy validation by check-in" (internally CHECKIN_OTHER / policy exempt). Denying it on the ProjectAlpha source control path for the Contributors group stops developers from bypassing failing policies, while the build service account (not in that group) keeps its permissions.
There is no "Bypass validation gates" permission in TFS 2012 version control, and no "Block check-ins" option in the check-in policy settings. Moving developers to Readers would remove their ability to check in code at all.
Your TFS 2012 deployment has a single team project collection named DefaultCollection that has grown very large. The Finance department's team projects within that collection must be moved to a separate SQL Server instance so they can be backed up and secured independently.
Which sequence of actions should you perform?
TFS 2012 has no supported way to move an individual team project out of a collection. The supported "split collection" technique is to detach the collection, take a SQL backup of the collection database and restore it to the target SQL Server instance under a new database name, attach that copy as a new collection, and then delete the unwanted team projects from each of the two collections.
There is no Split Collection command in the Administration Console and no collection /move switch that moves individual projects. TFS Integration Tools can copy data but loses fidelity (history, IDs) and is not the recommended approach for splitting a collection.
A development team uses the Microsoft Visual Studio Scrum 2.2 process template. The team wants a new field named "Customer Impact" to appear on the Product Backlog Item form, and they want that field to be usable in queries and to show up as a filterable dimension in the Analysis Services cube.
What must you do?
Fields are added to a work item type definition (WITD) with a unique reference name. To surface a field in the Analysis Services cube as something you can filter or group by, the field must be marked reportable="dimension". After importing the modified WITD, the warehouse and cube must be processed for the new dimension to appear.
reportable="detail" makes the field available only in the relational warehouse for Reporting Services detail reports, not as a cube dimension. measure is reserved for numeric aggregated values such as sums. Global lists only supply allowed values, they do not create fields.
You are installing Team Foundation Server 2012 for a company with 800 users. Management requires that build definitions, work item tracking, and reporting all be available, and that SQL Server Reporting Services and SQL Server Analysis Services run on a dedicated server separate from the TFS application tier.
You need to choose the correct installation path in the TFS 2012 setup wizard.
What should you do?
The Advanced configuration wizard is the only option that lets you configure reporting (SQL Server Reporting Services and Analysis Services) on separate machines from the application tier, along with remote SQL Server database instances. It is the appropriate choice for larger, distributed deployments.
Basic configuration installs a minimal deployment without reporting or SharePoint, so reporting would have to be added later - possible, but not the correct installation choice for this requirement in the wizard. Upgrade is only used when moving an existing earlier TFS deployment forward. TFS Express is limited to small teams (max 5 users) and does not support reporting at all.