070-225 無料問題集「Microsoft Designing and Deploying a Messaging Infrastructure with Microsoft Exchange 2000 Server」

（A）Use two storage groups on the Exchange 2000 Server computer that provides Internet mail access.

（B）Enable SSL connections on the Exchange 2000 Server computer that provides Internet mail access.

（C）Enable IPSec on the Exchange 2000 Server computer that provides Internet mail access.

（D）Place two front-end Exchange 2000 Server computers in a perimeter network. (DMZ).

（A）Move the DNS from the UNIX-based servers to Windows 2000. Continue to use the UNIX- based BIND DNS servers in the Chicago and Denver offices. Use Active Directory integrated zones for all zones. Create an MX record for each domain that will be represented on the Fabrikam Inc. internet mail servers.

（B）Continue to use the UNIX-based BIND DNS servers in the Chicago and Denver offices. Add a UNIX-based BIND DNS server at each office that does not currently have one. Configure all primary DNS zones on the DNS server in the Chicago office, and configure the secondary DNS zones on the DNS servers in the other offices. Create an MX record for each domain that will be represented on the Fabrikam Inc. Internet Mail Servers.

（C）Move the DNS from the UNIX-based servers to Windows 2000. Add a Windows 2000-based DNS server at each office that does not currently have one. Use Active Directory integrated zones for all zones. Create an MX record for fabrikam.com .

（D）Continue to use the UNIX-based BIND DNS servers in the Chicago and Denver offices.
Configure all primary DNS zones on the DNS server in the Chicago office, and configure the secondary DNS zones on the DNS server in the Denver office. Create an MX record for fabrikam.com

（A）Implement the DNS server service at each office that does not currently have it. At each of the
14 Fabrikam Inc. offices, place the domain controllers and the Exchange 2000 Server computers on the internal network. Place a front-end server for HTTP,SMTP, IMAP, and POP3 on the perimeter network. To support VPN connections, enable Routing and Remote access on a server on the perimeter network.

（B）Continue to use the DNS server service at the Chicago and Denver office.
At each of the 14 Fabrikam Inc. offices, place the domain controllers and the Exchange 2000 Server computers on the internal network.
Place a front-end server for HTTP, SMTP, IMAP, and POP3 on the perimeter network. To support VPN connections, enable Routing and Remote access on a server on the perimeter network.

（C）Continue to use the DNS server service at the Chicago and Denver office. At each of the 14 Fabrikam Inc. offices, place the domain controllers and the Exchange 2000 Server computers on the internal network. Place a front-end server for HTTP, SMTP, IMAP, and POP3 on the external network, outside both firewalls. To support VPN connections, enable Routing and Remote access on a server on the perimeter network and one connection on the internal network.

（D）Implement the DNS server service at each office that does not currently have it. At each of the
14 Fabrikam Inc. offices, place the domain controllers and the Exchange 2000 Server computers on the internal network. Place a front-end server for HTTP, SMTP, IMAP, and POP3 on the external network, outside both firewalls. To support VPN connections, enable Routing and Remote access on a server on the perimeter network and one connection on the internal network.

（A）Configure the LDAP server to have two separate ports: one for each protocol Server.

（B）Install two Windows 2000 Server computers that run Routing and Remote Access. Connect modems to each of these servers.

（C）Place the LDAP on the Internet.

（D）Use two storage groups on each Exchange 2000 Server computer. Use one storage group to support users who access e-mail from home, and the other storage groups to support users who access e-mail in the office.

（E）Place two front-end protocol servers on the Internet. Configure these two servers to use Network Local Balancing (NLB).

（A）Run setup.exe /domainprep

（B）Install the Windows 2000 Server Active Directory Connector (ADC).

（C）Install the Exchange 2000 Server Active Directory Connector (ADC).

（D）Install the Active Directory Migration tool (ADMT).

（E）Run setup.exe /forestprep

（A）Use Exchange 2000 indexing on all public folders.

（B）Use Exchange 2000 to replicate all public folders to another Server.

（C）Replicate all public folders to an Exchange 2000 Server computer in each location.

（D）Distribute all public folders across multiple public folder trees.

（E）Use the Windows 2000 indexing service on drive M.

（A）Replace the five mailbox servers at headquarters with two new Pentium III-based computers.
Use the old mailbox servers as X.400 bridgehead servers that connect to the plants.

（B）Replace the five mailbox servers at headquarters with two new Pentium III-based computers.
Move the public folders to the new mailbox servers.
Use the old public folder server as a bridgehead server.

（C）Replace the five mailbox servers at headquarters with one new Pentium III-based computer.
Use the old mailbox severs as front-end servers a headquarters.
Add memory to the bridgehead server.

（D）Replace the mailbox servers at each location with one new Pentium III-based computer for each location.
Move the public folders to the new mailbox servers.
Use the old public folder server as a bridgehead server.

（A）Enable circular logging on all of the servers.
Stop the virus-scanning software services prior to upgrading to Exchange 2000 Server.
After the upgrade, restart the virus-scanning software services.

（B）Disable circular logging on all of the servers.
Stop the virus-scanning software services prior to upgrading to Exchange 2000 Server.
After the upgrade, restart the virus-scanning software services.

（C）Enable circular logging on all of the servers.
Uninstall the virus-scanning software services prior to upgrading to Exchange 2000 Server.

（D）Disable circular logging on all of the servers.
Uninstall the virus-scanning software services prior to upgrading to Exchange 2000 Server.

（A）Customers who do not currently use Windows client computers.

（B）Customers that have 768Kbps DSL connections and who want to post to newsgroups or send via e-mail documents that are associated with more than one application.

（C）Customers who have 128-Kbps two-channel ISDN connections and who usually access their e-mail by using HTTP.

（D）Customers who have connections of 56-Kbps or slower and who frequently want to post to newsgroups or send via e-mail documents that are larger than 2MB.

（E）Customers who currently use network address translation to gain access to the Internet.