Learn About Upgrading Your MCSE to Windows Server 2008
By Certification Magazine —
1 | 2 | 3 |
These questions are based on 70-649: TS: Upgrading Your MCSE on Windows Server 2003 to Windows Server 2008, Technology Specialist
Microsoft
Self Test Software Practice Test
Objective: Configure network access.
Sub-objective: Configure IPv4 and IPv6 addressing.
Single answer, multiple-choice
You are the network administrator for your company. The company network consists of Windows Server 2008 server computers and Windows Vista client computers. You have the following eight Internet Protocol version 6 (IPv6) subnetted address prefixes:
- 3FFE:FFFF:0:C000::/54
- 3FFE:FFFF:0:C400::/54
- 3FFE:FFFF:0:C800::/54
- 3FFE:FFFF:0:CC00::/54
- 3FFE:FFFF:0:D000::/54
- 3FFE:FFFF:0:D400::/54
- 3FFE:FFFF:0:D800::/54
- 3FFE:FFFF:0:DC00::/54
What would be the original prefix length for the global address prefix 3FFE:FFFF:0:C000::?
A. 51
B. 52
C. 53
D. 54
Answer:
A. 51
Tutorial:
The original prefix length for the global address prefix 3FFE:FFFF:0:C000:: is 51. The eight IPv6 subnetted address prefixes are the result of 3-bit subnetting of the global address prefix 3FFE:FFFF:0:C000::/51. To perform 3-bit subnetting of the global address prefix 3FFE:FFFF:0:C000::/51, you must use the following calculations:
Hexadecimal value of the subnet ID being subnetted, F = 0xC000
Subnetting bits, s = 3
Network bits, m = 51
Number of bits within the subnet ID that are already fixed, f = 51 - 48 = 3
Number of prefixes, n = 2^3 = 8
Incremental value between each successive subnet ID expressed in hexadecimal, i = 2^16-(f+s)
i = 2^16-(3+3) = 1024 = 0x400
New prefix length, P = 51+ 3 = 54
All other options are incorrect.
References:
TechNet Home > Networking > Introduction to IP Version 6
Objective: Configure terminal services.
Sub-objective: Configure Terminal Services server options.
Single answer, multiple-choice
You install Terminal Services on a Windows Server 2008 computer named TS1. You install several business applications on TS1. You want to enable all users on the network to access these application remotely. To achieve this, you add all applications to the RemoteApps list.
You also want to ensure malicious users are unable to access any program not listed in the RemoteApps list. What should you do?
A. Remove the business applications from the RemoteApps list.
B. Select the “Block remote users from starting unlisted programs. Remote users will only be able to start RemoteApps that you list. (Recommended)” option on the Terminal Server tab in the RemoteApp Deployment Settings dialogue box.
C. Select the “Allow users to start both listed and unlisted programs” option on the Terminal Server tab in the RemoteApp Deployment Settings dialogue box.
D. Clear the “Make a remote desktop connection to this terminal server available in TS Web Access” option on the Terminal Server tab in the RemoteApp Deployment Settings dialogue box.
Answer:
B. Select the “Block remote users from starting unlisted programs. Remote users will only be able to start RemoteApps that you list. (Recommended)” option on the Terminal Server tab in the RemoteApp Deployment Settings dialog box.
Tutorial:
You should select the “Block remote users from starting unlisted programs. Remote users will only be able to start RemoteApps that you list. (Recommended)” option on the Terminal Server tab in the RemoteApp Deployment Settings dialogue box. RemoteApp programs are programs that are accessed remotely through Terminal Services so they appear to be running on the local computer of the end user.
You can use several methods to deploy RemoteApp programs, such as creating a Remote Desktop Protocol (.rdp) file or linking to the program on a Web site using TS Web Access. The .rdp package contains settings that are required to run RemoteApp programs. You can configure Terminal Server deployment settings to define how users will connect to the Terminal Server to access RemoteApp programs.
You can configure the Terminal Server tab in the RemoteApp Deployment Settings dialogue box to specify the connection settings, desktop access and access to unlisted programs. When you want to prevent malicious users from accessing programs other than specific end-user applications, you should select the “Block remote users from starting unlisted programs. Remote users will only be able to start RemoteApps that you list. (Recommended)” option.
You should not remove the business applications from the RemoteApps list. In this scenario, you want to enable all users on the network to access applications installed on TS1. Removing the programs from the RemoteApps list would prevent users from accessing programs installed on TS1.
You should not select “Allow users to start both listed and unlisted programs” option on the Terminal Server tab in the RemoteApp Deployment Settings dialogue box. Selecting this option would allow users to start any program remotely from an .rdp file on initial connection, in addition to those programs listed in the RemoteApps list. Selecting the “Allow users to start both listed and unlisted programs” option will not ensure malicious users are unable to access the programs not listed in the RemoteApps list.
You should not clear the “Make a remote desktop connection to this terminal server available in TS Web Access” option on the Terminal Server tab in the RemoteApp Deployment Settings dialogue box. This option provides a link to the full Terminal Server desktop through TS Web Access. Clearing the “Make a remote desktop connection to this terminal server available in TS Web Access” option will not ensure malicious users are unable to access the programs not listed in the RemoteApps list.
