Microsoft Pro: Designing and Deploying Messaging Solutions with Microsoft Exchange Server 2010 - 70-663무료 덤프문제 풀어보기

You have an Exchange Server 2007 organization.
You deploy servers that run Exchange Server 2010 Service Pack 1 (SP1) to the organization.
Your network contains two Active Directory sites named Site1 and Site2. The organization
contains five servers. The servers are configured as shown in the following table.

You plan to move all mailboxes to Servers and to decommission Server1 and Server2.
You need to recommend the process to decommission Server1 and Server2. The solution must prevent interruptions to the mail flow.
What should you do?
To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Select and Place:
정답:

Explanation:
http://technet.microsoft.com/en-us/library/aa996855(v=exchg.80).aspx
The Edge Subscription Process
The Edge Subscription process is the procedure that an administrator follows to establish an Edge Subscription for an Edge Transport server. You subscribe an Edge Transport server to an Active Directory site to associate the Edge Transport server with the Exchange organization. A subscribed Edge Transport server is stamped with an Active Directory site attribute. Among other things, this association enables you to configure the Edge Subscription as a source server for Send connectors that are created in the Exchange organization. The Hub Transport servers in the Exchange organization use an implicit intra-organizational Send connector to route e-mail messages to the Internet through the subscribed Edge Transport server. The Active Directory site association enables the Hub Transport servers to locate the Edge Transport server for routing purposes.
You are the enterprise administrator for an Exchange Server 2010 organization. All users run Microsoft Office Outlook 2010.
You are designing a sharing solution for your organization and a partner organization. The partner organization also uses Exchange Server 2010.
You need to recommend a strategy for sharing information with the partner organization to meet the following requirements:
-Provide cross-organizational access to user contacts
-Provide cross-organizational access to free\busy information

정답: A
설명: (Fast2test 회원만 볼 수 있음)
Your network contains an internal network and a perimeter network. The perimeter network contains an Exchange Server 2010 Edge Transport server.
You need to recommend a remote management solution for the Edge Transport server that meets the following requirements:
-All management traffic must be encrypted
-The solution must allow remote administration from the internet network
-The solution must support the use of the Exchange Management Console (EMC)
What should you recommend?

정답: C
설명: (Fast2test 회원만 볼 수 있음)
You have an Exchange Server 2010 Service Pack 1 (SP1) organization named contoso.com. A partner company named Fabrikam, Inc., has an Exchange Server 2010 (SP1) organization named fabrikam.com.
All client computers in contoso.com and fabrikam.com run Microsoft Outlook 2010. You need to ensure that users in fabrikam.com can view the availability information of users in contoso.com.
What should you do?
Select and Place:
정답:

Explanation/Reference: Corrected
The question is stating "users in fabrikam.com can view the availability information of users in contoso.com" , so contoso admin should grant fabrikam that relationship permission.
For users in your organization to have access to external users' free/busy information or to allow for one-way sharing of their free/busy information with the external organization, the administrator in the external organization must also create an organization relationship with your organization. However, the external administrator can specify a different level of access for their users that's different from the level you specified. In a one-way sharing example, the external administrator would configure their organization relationship so that their users' free/busy information isn't shared with users in your organization, but the free/busy information for your users would be visible to the users in the external organization based on your organization relationship settings. http://technet.microsoft.com/en-us/library/dd638083(v=exchg.141).aspx ************** The organization-level prerequisites to enabling two-way free/busy access between organizations are:
1- Both organizations must be running Exchange Server 2010 Client Access servers.
2- Both organizations must have federation trusts created and configured for the SMTP domains of the users who will be accessing free/busy between the organizations. The creation and management of federation trusts is discussed in detail in the "Federated Trust" section of this chapter.
3- Both parties must have created and configured an organization relationship with the other organization as discussed in the "Organization Relationship" section of this chapter. http://mscerts.programming4.us/application_server/exchange%20%20server%202010%20%20% 20federation%20scenarios%20(part%201)%20-%20freebusy%20access.aspx
================================== The old Answer & comments: ==================================

I think this answer is wrong and the correct answer is that Fabrikam should created the trust and the organization relationship
Implementing Federated Sharing
With federated sharing, you can use federation technologies to establish trusted relationships and hence enable secure Internet communications between organizations. This requires that you use Microsoft Federation Gateway as a trust broker, that each participating organization establish and manage its trust, and that federated sharing is supported for all messaging clients. To establish a federation trust, organizations exchange security certificates with public keys with each other or with a trusted third party and use those certificates to authenticate and secure all interorganizational communications.
The Microsoft Federation Gateway
The Microsoft Federation Gateway is an identity service that runs over the Internet and functions as a trust
broker for federated sharing. It provides a broker service to establish the communication between the
organizations but does not authenticate individual users or store any user account information from either
organization.
To enable federated sharing, you need to register your organization with the Federation Gateway and then
configure a federated sharing relationship with another organization that also registers with the Federation
Gateway. The Federation Gateway then acts as a hub for all connections that the organizations make with
each other, For example, Client Access servers in each organization connect through the Federation
Gateway to exchange availability information and enable calendar sharing. These Client Access servers
use the federated trust that you configure with the Federation Gateway to verify you partner's Client Access
servers and to encrypt traffic sent between the organizations. Users can also send encrypted and
authenticated email messages between the organizations.
In federated sharing, each organization needs only to manage its trust relationship with the Federation
Gateway and its own user accounts. After an organization establishes a trust relationship with the
Federation Gateway, you can identify other trusted organizations and the types of information you want to
share with them. When you enable federation sharing, all interorganizational communication is sent through
your organization's Exchange Server 2010 servers. This traffic is transparent to the messaging clients so
that federated sharing works with any client that can connect to Exchange Server 2010, including Microsoft
Outlook Web Access, Outlook 2003, Outlook 2007, and Outlook 2010.
Note:
FEDERATION GATEWAY
For more information about the Federation Gateway, see http://msdn.microsoft.com/en-us/library/
cc287610.aspx. For information about how to connect to and use the Federation Gateway, see http:// msdn.microsoft.com/en-us/library/dd164396.aspx.
Federated Sharing Requirements
To implement federated sharing, you need to establish and configure the following components in Exchange Server 2010:
A federation trust A federation trust configures the Federation Gateway as a federation partner with the Exchange Server organization, which enables Exchange Server 2010 Web Services on the Client Access servers to validate all Federation Gateway authentication requests. You establish a federation trust by submitting your organization's public key and a valid X.509 certificate issued by a Certificate Authority (CA) trusted by Windows Live Domain Services to the Federation Gateway and downloading the Federation Gateway public key and certificate. An organization identifier An organization identifier defines what authoritative domains in an Exchange organization are available for federation. If your organization supports multiple SMTP domains, you can include one or all of your domain names in your organization identifier. Users can participate in Federated Sharing only if they have email addresses in the domains that you configure with the organization identifier. The first domain you specify with the organization identifier is known as the account namespace. Federation Gateway creates federated user identifiers within this namespace when the Client Access server requests a delegation token for a user. This process is transparent to the Exchange Server organization.
Create a new organisational relationship
To enable free/busy sharing between two cloud-based organisations, run the following command:
Get-FederationInformation -DomainName <the other cloud-based organization> | New-OrganizationRelationship -Name <the other tenant domain> -FreeBusyAccessEnabled $true -FreeBusyAccessLevel LimitedDetails
Here's an example of what the command would look like in the Contoso scenario, where the administrator for the Contoso organisation configures an organisational relationship with Fabrikam College:
Get-FederationInformation -DomainName fabrikam.edu | New-OrganizationRelationship -Name Fabrikam -FreeBusyAccessEnabled $true -FreeBusyAccessLevel LimitedDetails
A corporate environment includes Exchange Server 2010 SP1 and Active Directory Domain Services (AD DS).
Members of the Legal security group must be able to do the following:
-Perform keyword searches across all mailboxes.
-Store the search results in a secure mailbox.
You need to recommend a solution that meets the requirements.
Which two actions should you recommend? (Each correct answer presents part of the solution.Choose two.)

정답: B,C
A corporate environment includes Exchange Server 2010. Two teams of support technicians manage mailboxes for the organization.
You have the following requirements:
-The Tier 1 support team must manage mailboxes for all users other than those in the Executive
Organizational Unit (OU).
-The Tier 2 support team must manage mailboxes for all users in the Executive OU.
You need to recommend a solution that meets the requirements.
What should you recommend?

정답: A
You have an Exchange Server 2010 Hub Transport server named Hub1. You install an application on a third-party server named Server1.
You discover that the application cannot authenticate to remote servers.
You need to ensure that the application can relay e-mail messages by using Hub1.
What should you do?

정답: D
You have an Exchange Server 2010 Service Pack 1 (SP1) organization named contoso.com.
You are planning the anti-spam infrastructure for the organization.
You need to identify which Exchange Server 2010 SP1 anti-spam technologies achieve your antispam
requirements.
Which technologies should you identify?
To answer, drag the appropriate anti-spam technology to the correct anti-spam requirement in the answer
area.
Select and Place:
정답:

Explanation/Reference:
I think the correct answers are Sender ID - Content Filtering - Sender Filtering - Recipient Filtering
Content Filtering - Content filtering provides another tool to help manage the flow of messages entering and exiting your enterprise mail stream. Content filtering enables you to filter messages using a variety of filtering tools. These include: Sender-domains filtering (for Realtime and Manual scan jobs), Subject line filtering (for Realtime and Manual scan jobs).Filter set templates (simplify the creation and management of file and content filters on all scan jobs)
Sender ID -The Sender ID Framework is an e-mail authentication technology protocol that helps address the problem of spoofing and phishing by verifying the domain name from which e-mail messages are sent. Sender ID validates the origin of e-mail messages by verifying the IP address of the sender against the alleged owner of the sending domain. Now adopted by more than 10 million domains worldwide, Sender ID is providing brand owners, senders, and receiving networks with significant business and technical value
Sender Filtering -The Sender Filter agent is an anti-spam filter that's enabled on computers that have the Microsoft Exchange Server 2010 Edge Transport server role installed. The Sender Filter agent relies on the MAIL FROM: SMTP header to determine what action, if any, to take on an inbound e-mail message. When you configure anti-spam filters on an Edge Transport server, the filters act on messages cumulatively to reduce the number of unsolicited messages that enter the enterprise. For more information about how to plan and deploy the anti-spam features, see Understanding Anti-Spam and Antivirus Functionality. The Sender Filter agent acts on messages from specific senders outside the organization. Administrators of Edge Transport servers maintain a list of senders who are blocked from sending messages to the organization. As an administrator, you can block single senders ([email protected]), whole domains (*.contoso.com), or domains and all subdomains (*.contoso.com). You can also configure what action the Sender Filter agent should take when a message that has a blocked sender is found.
You can configure the following actions:
-The Sender Filter agent rejects the SMTP request with a "554 5.1.0 Sender Denied" SMTP session error and closes the connection.
-The Sender Filter agent accepts the message and updates the message to indicate that the message came from a blocked sender. Because the message came from a blocked sender and it's marked as such, the Content Filter agent will use this information when it calculates the spam confidence level (SCL).
Recipient Filtering - The Recipient Filter agent blocks messages according to the characteristics of the intended recipient in the organization.
The Recipient Filter agent can help you prevent the acceptance of messages in the following scenarios:
-Nonexistent recipients You can prevent delivery to recipients that are not in the organization's address book. For example, you may want to stop delivery to frequently misused account names, such as [email protected] or [email protected].
-Restricted distribution lists You can prevent delivery of Internet mail to distribution lists that should be used only by internal users.
Mailboxes that should never receive messages from the Internet You can prevent delivery of Internet mail to a specific mailbox or alias that is typically used inside the organization, such as Helpdesk.
The Recipient Filter agent acts on recipients that are stored in one or both of the following data sources:
-Recipient Block list An administrator-defined list of recipients for which inbound messages from the Internet should never be accepted.
-Recipient Lookup Verification that the recipient is in the organization. Recipient Lookup requires access to Active Directory directory service information that is provided by EdgeSync to Active Directory Application Mode (ADAM).
Sender Reputation -Sender reputation weighs each of these statistics and calculates an SRL for each sender. The SRL is a number from 0 through 9 that predicts the probability that a specific sender is a spammer or otherwise malicious user. A value of 0 indicates that the sender isn't likely to be a spammer; a value of 9 indicates that the sender is likely to be a spammer.
You can configure a block threshold from 0 through 9 at which sender reputation issues a request to the Sender Filter agent, and, therefore, blocks the sender from sending a message into the organization. When a sender is blocked, the sender is added to the Blocked Senders list for a configurable period. How blocked messages are handled depends on the configuration of the Sender Filter agent.
The following actions are the options for handling blocked messages:
-Reject
-Delete and archive
-Accept and mark as a blocked sender
-If a sender is included in the IP Block list or Microsoft IP Reputation Service, sender reputation issues an immediate request to the Sender Filter agent to block the sender. To take advantage of this functionality, you must enable and configure the Microsoft Exchange Anti-spam Update Service.
By default, the Edge Transport server sets a rating of 0 for senders that haven't been analyzed. After a sender has sent 20 or more messages, sender reputation calculates an SRL that's based on the statistics listed earlier in this topic.

우리와 연락하기

문의할 점이 있으시면 메일을 보내오세요. 12시간이내에 답장드리도록 하고 있습니다.

근무시간: ( UTC+9 ) 9:00-24:00
월요일~토요일

서포트: 바로 연락하기 

English Deutsch 繁体中文 日本語