QUESTION: 16
You need to prevent several users in the Miami office from establishing more than two concurrent Exchange ActiveSync connections to the Exchange Server organization. The solution must affect only the users in the Miami office. Which two actions should you perform? (Each correct answer presents part of the solution. Choose two.)
A. Create a new throttling policy that has the Organization scope.
B. Create a new throttling policy that has the Global scope.
C. Create a new throttling policy that has the Regular scope.
D. Run the Set-ThrottlingPolicyAssociation cmdlet.
E. Run the Set-ThrottlingPolicy cmdlet.
F. Remove the default throttling policy.
Answer: C,D
Explanation:
New-ThrottlingPolicy
Use the New-ThrottlingPolicy cmdlet to create a non-default user throttling policy.
EXAMPLE 1
This example creates a non-default user throttling policy that can be associated with specific users. Any parameters that you omit inherit the values from the default throttling policy GlobalThrottlingPolicy_<GUID>.
After you create this policy, you must associate it with specific users. New-ThrottlingPolicy -Name ITUserPolicy -EwsMaxConcurrency 4 -ThrottlingPolicyScope Regular
The ThrottlingPolicyScope parameter specifies the scope of the throttling policy. You can use the following values.
Regular Specifies a custom policy that applies to specific users. Organization Specifies a custom policy that applies to all users in your organization. Global Reserved for the default throttling policy.
C
Need to establish a New Throttling policy to limit the Exchange ActiveSync connections and that has a regular scope to associate with specific users.
D
Use the Set-ThrottlingPolicyAssociation cmdlet to associate a throttling policy with a specific object. The object can be a user with a mailbox, a user without a mailbox, a contact, or a computer account.
EXAMPLE 1
This example associates a user with a user name of tonysmith to the throttling policy ITStaffPolicy that has higher limits.
Set-ThrottlingPolicyAssociation -Identity tonysmith -ThrottlingPolicy ITStaffPolicy
NOT A
Need a regular scope
NOT B
Need a regular scope
NOT E
Need to associate the new thottling policy with respective users.
Use the Set-ThrottlingPolicy cmdlet to modify the settings for a user throttling policy.
EXAMPLE 1
This example modifies a throttling policy so that users associated with this policy can have a maximum of four concurrent requests running in Exchange Web Services.
$a = Get-ThrottlingPolicy RemoteSiteUserPolicy
$a | Set-ThrottlingPolicy -EwsMaxConcurrency 4
NOT F
Need to create a new throttling policy
Set-ThrottlingPolicyAssociation: Exchange 2013 Help
Set-ThrottlingPolicy: Exchange 2013 Help
Tuesday, 31 January 2017
Tuesday, 17 January 2017
70-341 Sample Question : 15
QUESTION: 15
You need to resolve the search issue reported by the users in the New York office. You restart the Microsoft Exchange Search service and discover that the active copy of the mailbox database has a content indexing status of Unknown. What should you do next?
A. Rebuild the content index.
B. Run the Update-MailboxDatabaseCopy cmdlet and specify the -manualresume parameter.
C. Restart the Microsoft Exchange Mailbox Replication service.
D. Run the Update-MailboxDatabaseCopy cmdlet and specify the -catalogonly parameter.
Answer: A
Explanation:
Content Indexing also known as CI is a great feature to speed up item searching through mailboxes. Microsoft Exchange Search service
Exchange 2013 introduces the following changes to Exchange Search:
The underlying content indexing engine has been replaced with Microsoft Search Foundation, which provides performance and functionality improvements and serves as the common underlying content indexing engine in Exchange and SharePoint. The management interface, however, remain the same. By default, the Search Foundation handles the most common file formats in email attachments. You no longer need to install Microsoft Office Filter Packs for Exchange Search. For a list of the file formats handled by Exchange Search, see File Formats Indexed By Exchange Search. You can add support for any additional file formats by install IFilters, as in Exchange 2010. Content indexing is more efficient because it now processes messages in the transport pipeline. As a result, messages addressed to multiple recipients or distribution groups are processed only once. An annotation stream is attached to the message, significantly speeding up content indexing while consuming fewer resources.
A:
One of the first actions most Exchange Administrators generally take when troubleshooting suspected problems with Exchange Content Indexing will be to rebuild the impacted Mailbox Database's content index files (either manually or by using the ResetSearchIndex.ps1 script found in the \Exchange Server\Scripts directory). Makes sure that Exchange content index always remain healthy.
NOT B:
Not a database replication issue If the content index catalog for a mailbox database copy gets corrupted, you may need to reseed the catalog. Seeding is also known as updating. Use the Update-MailboxDatabaseCopy cmdlet to seed or reseed a mailbox database copy.
EXAMPLE 1:
This example seeds a copy of the database DB1 on the Mailbox server MBX1. Update-MailboxDatabaseCopy -Identity DB1\MBX1 The ManualResume switch specifies whether to automatically resume replication on the database copy. With this parameter, you can manually resume replication to the database copy.
NOT C:
Not related to an indexing issue. In Exchange 2013, the Microsoft Exchange Replication service periodically monitors the health of all mounted databases. In addition, it also monitors the Extensible Storage Engine (ESE) for any I/O errors or failures. When the service detects a failure, it notifies Active Manager. Active Manager then determines which database copy should be mounted and what it requires to mount that database. In addition, it tracks the active copy of a mailbox database (based on the last mounted copy of the database) and provides the tracking results information to the Client Access server to which the client is connected.
NOT D:
Content index needs to be rebuilt If the content index catalog for a mailbox database copy gets corrupted, you may need to reseed the catalog. Seeding is also known as updating. Use the Update-MailboxDatabaseCopy cmdlet to seed or reseed a mailbox database copy.
EXAMPLE 1:
This example seeds a copy of the database DB1 on the Mailbox server MBX1. Update-MailboxDatabaseCopy -Identity DB1\MBX1 . The CatalogOnly parameter specifies that only the content index catalog for the database copy should be seeded.
Exchange Search: Exchange 2013 Help
You need to resolve the search issue reported by the users in the New York office. You restart the Microsoft Exchange Search service and discover that the active copy of the mailbox database has a content indexing status of Unknown. What should you do next?
A. Rebuild the content index.
B. Run the Update-MailboxDatabaseCopy cmdlet and specify the -manualresume parameter.
C. Restart the Microsoft Exchange Mailbox Replication service.
D. Run the Update-MailboxDatabaseCopy cmdlet and specify the -catalogonly parameter.
Answer: A
Explanation:
Content Indexing also known as CI is a great feature to speed up item searching through mailboxes. Microsoft Exchange Search service
Exchange 2013 introduces the following changes to Exchange Search:
The underlying content indexing engine has been replaced with Microsoft Search Foundation, which provides performance and functionality improvements and serves as the common underlying content indexing engine in Exchange and SharePoint. The management interface, however, remain the same. By default, the Search Foundation handles the most common file formats in email attachments. You no longer need to install Microsoft Office Filter Packs for Exchange Search. For a list of the file formats handled by Exchange Search, see File Formats Indexed By Exchange Search. You can add support for any additional file formats by install IFilters, as in Exchange 2010. Content indexing is more efficient because it now processes messages in the transport pipeline. As a result, messages addressed to multiple recipients or distribution groups are processed only once. An annotation stream is attached to the message, significantly speeding up content indexing while consuming fewer resources.
A:
One of the first actions most Exchange Administrators generally take when troubleshooting suspected problems with Exchange Content Indexing will be to rebuild the impacted Mailbox Database's content index files (either manually or by using the ResetSearchIndex.ps1 script found in the \Exchange Server\Scripts directory). Makes sure that Exchange content index always remain healthy.
NOT B:
Not a database replication issue If the content index catalog for a mailbox database copy gets corrupted, you may need to reseed the catalog. Seeding is also known as updating. Use the Update-MailboxDatabaseCopy cmdlet to seed or reseed a mailbox database copy.
EXAMPLE 1:
This example seeds a copy of the database DB1 on the Mailbox server MBX1. Update-MailboxDatabaseCopy -Identity DB1\MBX1 The ManualResume switch specifies whether to automatically resume replication on the database copy. With this parameter, you can manually resume replication to the database copy.
NOT C:
Not related to an indexing issue. In Exchange 2013, the Microsoft Exchange Replication service periodically monitors the health of all mounted databases. In addition, it also monitors the Extensible Storage Engine (ESE) for any I/O errors or failures. When the service detects a failure, it notifies Active Manager. Active Manager then determines which database copy should be mounted and what it requires to mount that database. In addition, it tracks the active copy of a mailbox database (based on the last mounted copy of the database) and provides the tracking results information to the Client Access server to which the client is connected.
NOT D:
Content index needs to be rebuilt If the content index catalog for a mailbox database copy gets corrupted, you may need to reseed the catalog. Seeding is also known as updating. Use the Update-MailboxDatabaseCopy cmdlet to seed or reseed a mailbox database copy.
EXAMPLE 1:
This example seeds a copy of the database DB1 on the Mailbox server MBX1. Update-MailboxDatabaseCopy -Identity DB1\MBX1 . The CatalogOnly parameter specifies that only the content index catalog for the database copy should be seeded.
Exchange Search: Exchange 2013 Help
Thursday, 12 January 2017
70-341 Sample Question : 14
QUESTION: 14
You need to recommend which tasks must be performed to deliver email messages to the Internet if CH-EX2 and CH-EX3 fail to connect to the Internet. The solution must ensure that all queued email is sent. Which two tasks should you recommend? (Each correct answer presents part of the solution. Choose two.)
A. Run the retry-queue ch-to-internet command.
B. Create a new Send connector on a server in the Baltimore office.
C. Modify the cost of the CH-to-Internet Send connector.
D. Run the set-sendconnector -identity ch-to-internet -frontendproxyenabled Strue command.
E. Disable the CH-to-Internet Send connector.
Answer: B,E
Explanation:
The Baltimore and Chicago offices have independent Internet connections. Internet connectivity for the Los Angeles office is provided through Chicago. Currently no mail servers in Chicago.Only in Baltimore and Los Angeles. Once the transition to Exchange Server 2013 in the Chicago office is complete, all mail flow to and from the Internet will be managed centrally through that office by using a Send connector that has the following configurations:
Connector name: CH-to-Internet
Address space *
Source servers: CH-EX2, CH-EX3
Cost: 10
When you deploy Exchange 2013, outbound mail flow cannot occur until you configure a Send connector to route outbound mail to the Internet.
NOT A:
Will not resolve the issue.
Use the Retry-Queue cmdlet to force a connection attempt for a queue on a Mailbox server or an Edge Transport server.
EXAMPLE 1:
This example forces a connection attempt for all queues that meet the following criteria:
The queues are holding messages for the domain contoso.com.
The queues have a status of Retry.
The queues are located on the server on which the command is executed.
Retry-Queue -Filter {NextHopDomain -eq "contoso.com" -and Status -eq "Retry"}
NOT C:
Modifying the cost will not fix the issue of CH-EX2 and CH-EX3 failing to connect to the Internet.
Cost is used to set the priority of this connector, used when two or more connectors are configured for the same address space. The lower the cost higher the priority.
NOT D:
Modifying the send connector will not fix the internet connection from chicago mail server to the internet. Use the Set-SendConnector cmdlet to modify a Send connector.
EXAMPLE 1:
This example makes the following configuration changes to the Send connector named Contoso.com Send Connector:
Sets the maximum message size limit to 10 MB.
Changes the connection inactivity time-out to 15 minutes.
Set-SendConnector "Contoso.com Send Connector" -MaxMessageSize 10MB - ConnectionInactivityTimeOut
00:15:00
The FrontendProxyEnabled parameter routes outbound messages through the CAS server, where destination specific routing, such as DNS or IP address, is set, when the parameter is set to $true.
E:
Need to disable the send connector from Chicago to the internet so that when a new send connector on the Baltimore server is created, email can be sent to the internet. Send Connectors: Exchange 2013 Help.
You need to recommend which tasks must be performed to deliver email messages to the Internet if CH-EX2 and CH-EX3 fail to connect to the Internet. The solution must ensure that all queued email is sent. Which two tasks should you recommend? (Each correct answer presents part of the solution. Choose two.)
A. Run the retry-queue ch-to-internet command.
B. Create a new Send connector on a server in the Baltimore office.
C. Modify the cost of the CH-to-Internet Send connector.
D. Run the set-sendconnector -identity ch-to-internet -frontendproxyenabled Strue command.
E. Disable the CH-to-Internet Send connector.
Answer: B,E
Explanation:
The Baltimore and Chicago offices have independent Internet connections. Internet connectivity for the Los Angeles office is provided through Chicago. Currently no mail servers in Chicago.Only in Baltimore and Los Angeles. Once the transition to Exchange Server 2013 in the Chicago office is complete, all mail flow to and from the Internet will be managed centrally through that office by using a Send connector that has the following configurations:
Connector name: CH-to-Internet
Address space *
Source servers: CH-EX2, CH-EX3
Cost: 10
When you deploy Exchange 2013, outbound mail flow cannot occur until you configure a Send connector to route outbound mail to the Internet.
NOT A:
Will not resolve the issue.
Use the Retry-Queue cmdlet to force a connection attempt for a queue on a Mailbox server or an Edge Transport server.
EXAMPLE 1:
This example forces a connection attempt for all queues that meet the following criteria:
The queues are holding messages for the domain contoso.com.
The queues have a status of Retry.
The queues are located on the server on which the command is executed.
Retry-Queue -Filter {NextHopDomain -eq "contoso.com" -and Status -eq "Retry"}
NOT C:
Modifying the cost will not fix the issue of CH-EX2 and CH-EX3 failing to connect to the Internet.
Cost is used to set the priority of this connector, used when two or more connectors are configured for the same address space. The lower the cost higher the priority.
NOT D:
Modifying the send connector will not fix the internet connection from chicago mail server to the internet. Use the Set-SendConnector cmdlet to modify a Send connector.
EXAMPLE 1:
This example makes the following configuration changes to the Send connector named Contoso.com Send Connector:
Sets the maximum message size limit to 10 MB.
Changes the connection inactivity time-out to 15 minutes.
Set-SendConnector "Contoso.com Send Connector" -MaxMessageSize 10MB - ConnectionInactivityTimeOut
00:15:00
The FrontendProxyEnabled parameter routes outbound messages through the CAS server, where destination specific routing, such as DNS or IP address, is set, when the parameter is set to $true.
E:
Need to disable the send connector from Chicago to the internet so that when a new send connector on the Baltimore server is created, email can be sent to the internet. Send Connectors: Exchange 2013 Help.
Subscribe to:
Posts (Atom)