Designing Messaging Solutions With Microsoft Exchange Server 2007
BackBy Certification Magazine — August 21, 2008
These questions are based on 70-237: Pro: Designing Messaging Solutions with Microsoft Exchange Server 2007Microsoft
Self Test Software Practice Test
Objective: Design and plan messaging services.
Sub-objective: Evaluate and plan server deployment based on best practices, budget and other business factors.
Multiple answer, multiple-choice
You are the messaging engineer for your organization and plan to deploy Exchange Server 2007 server in your organization, limiting the number of servers to as few as possible. Which Exchange Server roles should you deploy to protect your Exchange environment from unwanted message traffic such as spam and intelligently route messages within an Exchange 2007 environment? (Choose two.)
A. Client Access Server.
B. Edge Transport Server.
C. Hub Transport Server.
D. Unified Messaging.
Answer:
B. Edge Transport Server.
C. Hub Transport Server.
Tutorial:
To protect your Exchange environment from unwanted message traffic and intelligently route messages within an Exchange 2007 environment, you should deploy Edge Transport Server and Hub Transport Server roles.
The Edge Transport Server role protects your Exchange environment from unwanted message traffic such as anti-virus and spam and is deployed outside the Active Directory forest in the perimeter network. Edge Transport Server allows you to inspect inbound e-mails in the perimeter network for spam and viruses. You should ensure that anti-spam components in Exchange Server 2007 are up-to-date.
Besides using Windows Update, you can use Microsoft Exchange 2007 Standard Anti-spam Filter Updates and Microsoft Forefront Security for exchange servers. Microsoft Exchange 2007 Standard Anti-spam Filter updates every two weeks. Microsoft Forefront Security for Exchange Server Filter updates every 24 hours.
The Hub Transport Server role helps you intelligently route messages within an Exchange 2007 environment. The Hub Transport Server routes a message destined to multiple recipients by identifying the most efficient route to send the message. The Hub Transport Server keeps the messages intact for multiple recipients until the most appropriate endpoint by transmitting only one copy of the message to the server. At the server, the message is broken apart, with a copy of the message dropped into each of the recipient's mailboxes at the end point.
The Hub Transport role, Client Access role and Mailbox Server roles of Exchange Server 2007 can be installed on a single server. The Edge Transport Server role cannot be installed on a server that holds other roles; therefore the Edge Transport Server needs to be installed on a separate server. If you need to deploy an Edge Transport Server with another Exchange Server 2007 server to implement the various server roles, you should use two different Exchange 2007 servers.
Deploying the Client Access Server role will not help you achieve the objective. This role in Exchange Server 2007 is required to communicate between themselves and Mailbox Servers. The Client Access Server role controls access to mailboxes from all clients that are not using Microsoft Outlook and do not use Messaging Application Programming Interface (MAPI) connections by using Outlook Web Access (OWA), Exchange ActiveSync, Outlook Anywhere, Post Office Protocol 3 (POP3) or Internet Message Access Protocol (IMAP4).
Deploying the Unified Messaging role will not help you achieve the objective. The Unified Messaging role allows integrating fax, voice mail and e-mail into a user's mailbox. It is recommended that the Unified Messaging role be installed only when the infrastructure to support this role already exists. The Unified Messaging role requires integration with a third-party Private Branch Exchange (PBX) system.
References:
Exchange 2007 - Server Roles
Microsoft Exchange Server 2007 Unleashed, Chapter 1: Exchange Server 2007 Technology Primer, Identifying Exchange Server 2007 Server Roles, page 25.
Objective: Design and plan coexistence and migration.
Sub-objective: Design and plan for migration of legacy Exchange features.
Single answer, multiple-choice
You are the messaging engineer for TXGlobal Corp. Your organization has two Active Directory forests: TXGlobalForestA and TXGlobalForestB. There is a cross-forest trust relationship between these forests. Both the forests have an Exchange Server 2003 messaging system. You plan to migrate the messaging system in TXGlobalForestB to Exchange Server 2007 in six months. You also plan to migrate all computers from Microsoft Office 2003 to Microsoft Office 2007 in the same time frame.
You need to recommend a solution to ensure users in one forest are able to access free/busy data about users in both forests for the next six months. What should you recommend?
A. Use the global address list (GAL) Synchronization feature in Microsoft Integration Identity Server (MIIS) 2003.
B. Use the Availability service.
C. Use the /EnableLegacyOutlook parameter while installing the Mailbox Server.
D. Use the Microsoft Exchange Server Inter-Organization Replication tool.
Answer:
D. Use the Microsoft Exchange Server Inter-Organization Replication tool.
Tutorial:
You should use the Microsoft Exchange Server Inter-Organization Replication tool to ensure users in one forest are able to access free/busy data about users in both forests. The Microsoft Exchange Server Inter-Organization Replication tool allows sharing of free/busy data between users in a cross-forest environment, where one forest does not have any Exchange 2007 Mailbox servers, or users do not use Outlook 2007 to access their e-mail. In this scenario, neither forest will have Exchange Server 2007 for the next six months. To use the Inter-Organization Replication tool, you must have at least one Exchange 2000 Server or Exchange Server 2003 server in each forest.
You should not use the GAL Synchronization feature in MIIS 2003 to ensure users in one forest are able to access free/busy data about users in both forests. GAL Synchronization feature provides users in a forest access to global address list information of both forests. The GAL Synchronization feature does not provide access to free/busy data. The mail recipient information is stored in a GAL for a single forest.
You should enable and configure the GAL Synchronization feature in MIIS 2003 if you have a cross-forest environment. This will ensure the GAL in both forests contains mail recipient information for both forests.
You should not use the Availability service to ensure users in one forest are able to access free/busy data about users in both forests. You should install Exchange Server 2007 in both forests to use the Availability service to enable users in a cross-forest environment to gather free/busy data about users in both forests.
Also, to use the Availability service, users should use Microsoft Office Outlook 2007 client to access their e-mail messages. In this scenario, Exchange Server 2007 will not be deployed for six months. You should use the Microsoft Exchange Server Inter-Organization Replication tool to ensure users in one forest are able to access free/busy data about users in both forests.
You should not use the /EnableLegacyOutlook parameter while installing the Mailbox Server to ensure users in one forest are able to access free/busy data about users in both forests. This parameter is used to create a public folder database on a Mailbox server. To use this parameter, client computers in your messaging system must use Microsoft Office Outlook 2003 or earlier versions. For example, if you want to remove the need for public folder databases in a forest, then you should ensure all client computers in that forest are running Microsoft Office Outlook 2007.
Reference:
Exchange 2007 > Connecting Forest Topologies
Objective: Design and plan coexistence and migration.
Sub-objective: Plan for coexistence (management tools for 2003 and 2007).
Single answer, multiple-choice
You are the messaging engineer for GeoTrek Corp. Your organization has Exchange Server 5.5, Exchange Server 2000 and Exchange Server 2003 servers in the messaging system. You plan to convert your organization from mixed mode to native mode. What should you do to prepare your Exchange organization for conversion to native mode?
A. Decommission Exchange Server 2003.
B. Decommission Exchange Server 2000.
C. Decommission Exchange Server 5.5.
D. Run an in-place upgrade on Exchange Server 5.5 to install Exchange Server 2003.
Answer:
C. Decommission Exchange Server 5.5.
Tutorial:
You should decommission the Exchange Server 5.5 from your Exchange organization to prepare your Exchange organization for conversion to native mode. A mixed mode Exchange organization can contain Exchange Server 2003 or earlier versions. In native mode, the Exchange organization can only contain Exchange Server 2000 or later versions.
After you have removed Exchange Server 5.5 and all versions of Exchange Server before Exchange 2000, you should use Exchange System Manager to switch your Exchange organization to native mode. You have to convert your Exchange organization to native mode if you plan to install Exchange Server 2007 in your messaging system because Exchange Server 2007 does not support mixed mode and can only be installed in native mode.
You should not decommission Exchange Server 2003to prepare your Exchange organization for conversion to native mode. Exchange organization in native mode supports Exchange Server 2000 or later versions. You should remove Exchange Server 5.5 or earlier versions of Exchange to convert your Exchange organization to native mode.
You should not decommission Exchange Server 2000 to prepare your Exchange organization for conversion to native mode. The Exchange organization in native mode supports Exchange Server 2000 or later versions. You should remove Exchange Server 5.5 or earlier versions of Exchange to convert your Exchange organization to native mode.
You cannot run an in-place upgrade on Exchange Server 5.5 to install Exchange Server 2003 to prepare your Exchange organization for conversion to native mode. To upgrade your organization from Exchange Server 5.5 to Exchange Server 2003, you must install Exchange Server 2003 on a separate computer and then decommission the Exchange Server 5.5 from your organization.
References:
Microsoft Help and Support > How To Convert from Mixed Mode to Native Mode in Exchange
Microsoft TechNet > Exchange Organization is in Mixed Mode
Microsoft TechNet > Migrating from Exchange Server 5.5 to Exchange Server 2003
Objective: Define policies and security procedures.
Sub-objective: Design procedures for message content filtering.
Single answer, multiple-choice
You are the messaging engineer for Verigon Corp. You have deployed Exchange Server 2007 in your organization. Your Exchange Server 2007 messaging system has the following servers: VerigonServ1, VerigonServ2, VerigonServ3 and VerigonServ4.
• VerigonServ1 hosts the Edge Transport server role.
• VerigonServ2 hosts the Hub Transport server role and Mailbox server role.
• VerigonServ3 hosts the Client Access server role.
• VerigonServ4 hosts the Unified Messaging server role.
You need to provide a messaging solution to ensure an e-mail message originates from the same Internet domain from which the message claims to have originated. What should you do to achieve the objective?
A. Configure the Sender ID agent on VerigonServ1.
B. Configure the Recipient Filter agent on VerigonServ2.
C. Configure the Connection Filter agent on VerigonServ3.
D. Configure the Sender Filter agent on VerigonServ4.
Answer:
A. Configure the Sender ID agent on VerigonServ1.
Tutorial:
You should configure the Sender ID agent on VerigonServ1 to ensure that an e-mail message originates from the same Internet domain from which the message claims to have originated. The Sender ID agent will verify the Sender ID of an e-mail message. VerigonServ1 hosts the Edge Transport server role that is deployed in the perimeter network and outside the Active Directory forest to provide protection against spam and viruses for Internet-facing mail flow.
The Edge Transport server includes a variety of anti-spam and anti-virus features designed to reduce the spam that enters your organization. A Sender ID agent is an anti-spam agent that verifies each e-mail message has actually originated from the Internet domain that it claims to originate from. This agent examines the IP address of the sender's e-mail address and compares it to the sending ID record in the originator's public Domain Name System (DNS) server. Sender ID agent is one of the anti-spam agents available on Edge Transport Server.
You should not configure the Recipient Filter agent on VerigonServ2 to achieve the objective in this scenario. VerigonServ2 is configured as a Hub Transport Server in this scenario, and you will have to use the Install-Antispamagents.ps1 script to install and enable anti-spam features on the Hub Transport Server. By default, anti-spam features are not enabled on the Hub Transport Server. The Recipient Filter agent performs recipient lookups for inbound messages and blocks e-mail messages sent to nonexistent users. The Recipient Filter agent cannot be used to verify the Sender ID of an e-mail message. In this scenario, you should configure the Sender ID agent on the VerigonServ1 to achieve the objective.
You cannot configure the Connection Filter agent on VerigonServ3 to achieve the objective in this scenario. VerigonServ3 hosts the Client Access server role, and you cannot enable anti-spam features on this server role. The Client Access server role manages client access to your Exchange 2007 server using various clients such as Post Office Protocol version 3 (POP3), Internet Message Access Protocol version 4 (IMAP4), Microsoft Outlook Anywhere, ActiveSync and Outlook Web Access. Connection Filter agent prevents spam from entering your Exchange organization by blocking or allowing e-mail messages from specific networks, IP addresses and IP ranges. However, it cannot be used to verify the Sender ID of an e-mail message.
You cannot configure the Sender Filter agent on VerigonServ4 to achieve the objective in this scenario. VerigonServ4 hosts the Unified Messaging server role that provides support for voice mail, e-mail and fax messages in the Exchange Server 2007 organization. The Sender Filter agent blocks e-mail messages from specific e-mail addresses, domains and sub-domains but cannot be used to verify the Sender ID of an e-mail message.
Reference:
Microsoft TechNet > New Anti-Spam and Antivirus Functionality
Objective: Define policies and security procedures.
Sub-objective: Design secure messaging.
Multiple answer, multiple-choice
You are the messaging engineer for the AccuTech Corp. You have installed Exchange Server 2007 messaging system in your organization. Your Exchange Server 2007 messaging system hosts an Edge Transport Server, a Hub Transport Server, a Mailbox Server and a Client Access Server.
There are various departments in your organization, namely, Sales, Marketing, Research, Vendor and Finance. You have created separate storage groups for each department in the organization. You want to prevent transmission of messages between the Marketing and Vendor groups.
Which two actions should you perform to achieve the objective? (Each correct answer presents part of the solution. Choose two.)
A. Run the Enable-JournalRule cmdlet in the Exchange Management Shell.
B. Run the Set-JournalRule cmdlet in the Exchange Management Shell.
C. Run the New-JournalRule cmdlet in the Exchange Management Shell.
D. Type the $Condition = Get-TransportRulePredicate BetweenMemberOfcommand in the Exchange Management Shell.
E. Run the New-TransportRule cmdlet in the Exchange Management Shell.
Answer:
D. Type the $Condition = Get-TransportRulePredicate BetweenMemberOfcommand in the Exchange Management Shell.
E. Run the New-TransportRule cmdlet in the Exchange Management Shell.
Tutorial:
The options stating that you should type the $Condition = Get-TransportRulePredicate BetweenMemberOfcommand in the Exchange Management Shell and run the New-TransportRule cmdlet in the Exchange Management Shell are correct. To achieve the objective, you should first configure the BetweenMemberOf transport rule predicate by using the $Condition = Get-TransportRulePredicate BetweenMemberOfcommand. This command assigns a condition to the transport rule agent.
The first predicate property value for this condition should be the distribution group object for the Marketing group and the second predicate property value for this condition should be the distribution group object for the Vendors group. Then you should run the New-TransportRule cmdlet in the Exchange Management Shell to prevent transmission of messages between the Marketing and Vendor groups. To block the flow of e-mail messages between two individual users or groups, you should create an ethical wall between them. To create an ethical wall, you should create transport rules on a Hub Transport Server.
After you have created a condition using $Condition = Get-TransportRulePredicate BetweenMemberOf command, you should run the New-TransportRule cmdlet to apply that condition. You should run the New-TransportRule cmdlet on the Hub Transport Server because all messages entering or leaving your Exchange organization are routed through the Hub Transport Server. The Hub Transport server will apply transport rules on all messages. You can also use transport rules to prevent communication between two groups located in different sites.
You should not run the Enable-JournalRule cmdlet in the Exchange Management Shell to achieve the objective in this scenario. A journal rule allows you to save a copy of e-mail messages sent and received from a user, a group or an entire organization in a secured compliance folder. The Enable-JournalRule cmdlet allows you to enable a journal rule disabled earlier. The Enable-JournalRule cmdlet requires you to specify the Identity parameter to identify the journal rule that needs to be enabled. To disable a journal rule, you can use the Disable-JournalRule cmdlets.
You should not run the Set-JournalRule cmdlet in the Exchange Management Shell to achieve the objective in this scenario. A journal rule allows you to save a copy of e-mail messages sent and received from a user, a group or entire organization in a secured compliance folder. The Set-JournalRule cmdlet allows you to modify an existing journal rule. The Set-JournalRule cmdlet requires the Identity parameter to identify the journaling agent that needs to be modified. You can also specify other parameters — such as Recipient, JournalEmailAddress or Scope in any combination — to provide the new values.
You should not run the New-JournalRule cmdlet in the Exchange Management Shell to achieve the objective in this scenario. A journal rule allows you to save a copy of e-mail messages sent and received from a user, a group or an entire organization in a secured compliance folder. The New-JournalRule cmdlet is used to create a new journal rule. This will require you to specify values for the Name, Scope, Recipient and JournalEmailAddress parameters while creating a new journal rule. The Name parameter assigns a name to the new journal rule and the Recipient parameter defines the source whose messages will be copied to the mailbox compliance folder.
References:
Microsoft TechNet > How to Configure an Ethical Wall
Microsoft TechNet > How to Create a New Transport Rule
Microsoft TechNet > Understanding Ethical Walls
Industry News
Outbound IVR Services to Increase Nearly 250 Percent by 2013
A new report by Datamonitor reveals the North American market for hosted outbound integrated voice response (IVR) services is set to more than double from an estimated $213 million in 2008 to $524 million by 2013.
Read more http://www.certmag.com/read2.php?in=3285
IT Channel Seeing Growth in RFID Projects, CompTIA Survey Reveals
The survey found that 46 percent of IT channel companies’ customers have implemented one or more RFID solutions. This is an increase from a 2007 survey, when the figure was 34 percent.
Read more http://www.certmag.com/read2.php?in=3286
OpenSUSE Project Releases Version 1.0 of openSUSE Build Service
The first major release of the Build Service provides developers with direct access to the code repositories for the openSUSE Linux distribution, thus streamlining the ability for all developers to contribute code.
Read more http://www.certmag.com/read2.php?in=3261
Viewed 8096 times.
