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