Welcome to Certifiable, your exam prep headquarters. Here you'll find questions about some of the tricky areas that are fair game for the certification exams. Following the questions, you'll find the correct answers and explanatory text. We change the questions weekly.
Questions (February 22, 2002)
Answers (February 22, 2002)
This week's questions cover topics for Exam 70-270: Installing, Configuring, and Administering Microsoft Windows XP Professional.
Question 1
You've configured a Windows XP Professional system as a front-end Terminal Services connector. Specifically, you set up the XP Pro computer with Microsoft Internet Information Services (IIS) 5.1 and established a home page so that your systems administration group members can quickly type a server name and administer it using Terminal Services. The XP system on which the Terminal Services front-end connection is installed has the Fully Qualified Domain Name (FQDN) bofh.oksanatech.org.au. Which of the following URLs correctly points to the page from which users can access the Remote Desktop Web connection? (Choose the best answer.)
- http://bofh.oksanatech.org.au/webmin
- http://bofh.oksanatech.org.au/tsclient
- http://bofh.oksanatech.org.au/tsweb
- http://bofh.oksanatech.org.au/terminals
- http://bofh.oksanatech.org.au/rdweb
Question 2
You want to enable access to a Windows XP system named kakafka for members of the Active Directory (AD) group PFY in your Windows 2000 domain. Which of the following steps should you take on the system to give the PFY group Remote Desktop access to it? (Select all that apply.)
- Run gpedit.msc. Click User Config, Admin Templates, Windows Components, Terminal Services. Find the "Allow Access to" key and set it to Enable. Drag the PFY group to the list of allowable users/groups.
- Run gpedit.msc. Click Computer Config, Admin Templates, Windows Components, Terminal Services. Find the "Allow Access to" key and set it to Enable. Drag the PFY group to the list of allowable users/groups.
- Right-click My Computer, and select Manage, Local Users and Groups, Groups. Open the Remote Desktop Users group, and add the PFY group.
- Right-click My Computer, and select Manage, Terminal Services, Properties. In the Allow Access dialog box, select the PFY group.
- Right-click My Computer, select Properties, and select the Remote tab. Select "Allow Users to connect to this computer remotely," click "Select Remote Users," and use AD to add the PFY group.
Question 3
Using the Group Policy edit tool, gpedit.msc, which of the following options can you configure for Remote Desktop/Terminal Services on a Windows XP Professional workstation? (Choose all that apply.)
- Set a time limit for disconnected sessions.
- Set a time limit for active sessions.
- Allow reconnections from the original client only.
- Terminate sessions when time limits expire.
- Disable Terminal Services Sound.
Answer to Question 1
The correct answer is C—http://bofh.oksanatech.org.au/tsweb. XP's Web-based Terminal Services client is a fast and easy way to access Terminal Services. Terminal Services, in turn, is an excellent tool for remote administration of Windows .NET and Win2K servers. Win2K requires an add-on to enable this functionality, but Microsoft has built it into XP.
Answer to Question 2
The correct answers are C—Right-click My Computer, and select Manage, Local Users and Groups, Groups. Open the Remote Desktop Users group, and add the PFY group; and E— Right-click My Computer, select Properties, and select the Remote tab. Select "Allow Users to connect to this computer remotely," click "Select Remote Users," and use AD to add the PFY group. Either method—defining who can access Remote Desktop or defining who can access Remote Control—will accomplish your goal. Note that this question asks about Remote Desktop, not Remote Assistance. Setting up one machine for Remote Desktop access might be useful for several reasons. You might want to use the connection to access a specific application or configure it for special services through the firewall.
Answer to Question 3
The correct answers are A—Set a time limit for disconnected sessions; B—Set a time limit for active sessions; C—Allow reconnections from the original client only; and D Terminate sessions when time limits expire. Each option is useful. If you've used Windows 2000 Server Terminal Services, for example, you know that it's a good idea to set a time limit for disconnected remote administration sessions. If you don't, the two remote administration sessions that Terminal Services permits can become tied up if they're accidentally disconnected and an administrator must log on from the console to disconnect them.
