Question No: 11

Server (TFS) 2012) server installed at its main office. Branch offices have limited bandwidth connecting to the main office.

Client team members at one of the branch offices report that it is taking too long to retrieve files from source control.

You need to speed up the source control access for their most commonly accessed files. What should you do?

A.

Install a SQL server at the remote office and configure replication of the source control database from the main office to the SQL server at the remote office.

Install and configure a TFS proxy server at the remote office to use the replicated database.

Configure all the clients at the remote office to use the new proxy server

B.

Install a new TFS instance at the remote office and configure it to sync with the main office.

Configure all the clients at the remote office to connect to the new TFS instance.

C.

Install and configure a TFS proxy server at the remote office.

Configure all the clients at the remote office to use the new proxy server.

D.

Install and configure a TFS proxy server at the remote office.

Run the TFSConfig.exe command to redirect remote users to the TFS proxy server based on IP address.

Install and configure a TFS proxy server at the remote office.

Run the TFS Admin Console command to redirect remote users to the TFS proxy server based on IP address.

Answer: C

Question No: 12

Your network environment includes a Microsoft Visual Studio Team Foundation Server (TFS) 2012 server. Your TFS environment currently consists of a single team project collection (TPC) named DevTPC, one build controller named BC-1, and one build agent named BA-1.

Question No: 14

The Windows Server 2008 R2 SP1 server has a SQL Server 2008 R2 environment, as well as a Microsoft Office SharePoint Foundation 2010 environment. Your organization wants to perform an in-place upgrade to the 2013 version of TFS.

You need to prepare the environment to meet the minimum requirements for the upgrade. What should you do?

You release new versions quarterly and provide support for the four most recent versions. When issues are logged with previous versions it is time-consuming for your developers to locate and associate the correct version of debugging symbols and source code.

You need to streamline the process for debugging prior versions of your library. What should you do?

When it is time to deploy each quarterly update, copy the release binaries into version control.

Within the build definition, set the Index Sources property to True and provide a path for the symbols. Add this path to the list of symbol file locations in Visual Studio when debugging that particular version.

When it is time to deploy each quarterly update, label the source code with the version number being released.

Enable IntelliTrace within Visual Studio. Within the build definition, set the IntelliTrace option to True.