Team Foundation Server (TFS) Quiz

TFS provides a multi-layered security model that includes its own security system for project-level permissions, integration with SharePoint security for portal access, and Reporting Services security for report access. This layered approach allows fine-grained control over different aspects of the TFS environment.

TFS security operates on both individual users and groups. You can assign permissions directly to specific users or to Windows/Active Directory groups and TFS groups. This dual approach provides flexibility - use users for specific permissions and groups for role-based access control.

Lab Management integrates physical and virtual test labs into the software lifecycle, automating provisioning and configuration. Other options like test case, bug, or process management deal with test logic, defect tracking, or workflow control rather than lab infrastructure.

Team Foundation Server (TFS) architecture has server components (TFS Application Tier, SharePoint, SQL Server) and client components (Team Explorer, Team System Clients, MS Office integration). SharePoint runs on the server side to provide project portal functionality, while Team Explorer and MS Office integrations are client-side tools.

A TFS work item includes multiple components: links to related work items, audit history tracking all changes, file attachments, and the current state field. Since all options A-D are valid parts of a work item, the correct answer is 'None of the above' - meaning none of them are excluded from work items.

TFS Work Items integrate with Microsoft Excel for bulk editing and publishing work items, and with Microsoft Project for project scheduling and timeline management. The Outlook integration option exists in later TFS versions but the question asks for specific integrations, with Excel and Project being the primary historically-supported integrations.

Team-based development involves a group of individuals with different specialized roles (like developers, testers, analysts) working collaboratively toward a common, shared product or goal. Distractors fail by suggesting different purposes or identical roles.

Complex server topology in TFS uses multiple servers configured in clusters or failover arrangements to host both the data tier (databases) and application tier (TFS application servers). This provides high availability and redundancy - if one server fails, another takes over. Simple topology uses a single server, while moderate separates data and application tiers without clustering.

TFS Source Control provides offline support (you can work without server connection and sync later), folder difference tools to compare local and server versions, and distributed team support for geographically separated teams. All three are legitimate features, making 'All of the above' the correct answer.

Branching preserves the complete history of files and folders because when you create a branch, TFS maintains the entire version history up to that branch point. You can view the full historical context in the new branch. Merging combines changes but doesn't create the historical record, Annotate shows per-line history, and History is a view command.

A shelveset in TFS allows you to store your pending changes on the server without committing them to the source control repository. This is useful for: (1) saving work-in-progress to share with others for code review, (2) switching to another task, or (3) getting a clean workspace for build. Changesets are permanent commits, and check-ins finalize changes.

Gated Check-in is a TFS build option that requires a successful build before allowing changes to be committed to the repository. When you queue a gated check-in, TFS shelves your changes, builds them, and only commits them if the build passes. This prevents broken code from entering the main branch. Incremental and continuous check-in are not TFS terms.

The question asks what TFS 2010 CANNOT achieve. All options A-E (parallel development, code quality protection, work management, progress reporting, environment administration) are core capabilities of TFS 2010. Therefore, 'None of the above' is correct - there is nothing listed that TFS 2010 cannot do.

When creating a new TFS team project, the system creates four default groups: Project Administrators (full control), Project Readers (read-only access), Project Contributors (can contribute work items and code), and Project Build Services (used by build agents). Options A, B, and D incorrectly list 'Project Testers', 'Project Developers', and 'Project Writers' which are not default groups.

The TFS Administration Console (often referred to as TFS Administrator) is the administrative application used to configure, monitor, and manage Team Foundation Server settings and team project collections. By contrast, Team Explorer is a client-side interface used to connect to TFS.

TFS stands for Team Foundation Server, which is Microsoft's application lifecycle management (ALM) and collaboration platform. It provides version control, work item tracking, build automation, testing, and release management capabilities for software development teams.

The five core components of Team Foundation Server are: (1) Work Item Tracking - bugs, tasks, requirements; (2) Version Control - source code management; (3) Build Automation - automated build and CI/CD; (4) Project Portal - SharePoint-based team collaboration site; (5) Reporting - SQL Server Reporting Services reports for project metrics. Process templates are not a component but templates that configure these components.

TFS supports four out-of-box check-in policies: Code Analysis (requires code analysis rules to pass), Testing (requires associated tests to pass), Build (requires build to succeed), and Work Items (requires work items to be linked/associated). The 'work items' option completes the set - options A, B, and C incorrectly list 'Inspections', 'Process flow', and 'Review' which are not standard policies.

The Agile process template in TFS 2010 includes two key Excel workbooks: Product Backlog (for capturing and prioritizing all user stories/features for the product) and Iteration Backlog (for planning work in specific iterations). Sprint backlog is a Scrum term - TFS Agile uses 'iteration' instead of 'sprint'.