70-341 Core Solutions of Microsoft Exchange Server Practice Questions

This statement is false. A key architectural change in Exchange 2013 was the introduction of the Managed Store. Each mounted database has its own worker process (Microsoft.Exchange.Store.Worker.exe), but these processes run under the context of the Network Service account, not Local System. This provides better isolation and security compared to previous versions where the entire Information Store ran as a single process under a highly privileged account.

The built-in anti-malware capabilities are configured through anti-malware policies in the Exchange Admin Center (EAC) under the 'Protection' section. Within the default (or a custom) policy, you can define the action to take when malware is detected (e.g., 'Delete the entire message') and configure sender notifications, including customizing the text for internal and external senders.

Exchange workload management uses throttling policies to control resource consumption by users. To create a custom set of throttling limits for a specific group, you must first create a new policy using New-ThrottlingPolicy. You can then modify its parameters (like RCAPercentTimeInAD, RCAPercentTimeInCAS, etc.) and assign it to the power users. The other cmdlets manage different aspects of the Exchange configuration but are not used for creating user throttling policies.

The 'Discovery Management' role group is specifically designed for this purpose. It contains the 'Mailbox Search' and 'Legal Hold' roles, which grant permissions to perform In-Place eDiscovery searches across all mailboxes.

While this is assigned by default, verifying that the necessary role ('Mailbox Search') is part of the role group is a critical step. The combination of adding the user to the correct group and ensuring the group has the correct role provides the required permissions.

The described behavior is a classic symptom of incorrect load balancer affinity (also known as persistence or stickiness). When a user authenticates to OWA, a session is established with one CAS server. If a subsequent request within the same session is sent to the other CAS server, the user will be prompted to re-authenticate. The load balancer must be configured with client affinity (e.g., source IP or cookie-based) to ensure all requests from a single client session are sent to the same CAS server.

For Kerberos authentication to function correctly with a Client Access Server array or load-balanced CAS, the credentials must be shared among the servers. This is accomplished by using a shared alternate service account (ASA) credential. The ms-Exch-EPI-Token-Serialization extended right allows Exchange servers to read and write the service principal name (SPN) and encryption keys from the alternate service account in Active Directory. The other cmdlets configure different aspects of authentication but do not address the core requirement of sharing Kerberos credentials.

The ReplayLagManagerEnabled property, which is enabled by default, allows the system to automatically play down log files for lagged copies when certain conditions are met, such as low disk space or when the lagged copy has been determined to be the only available copy for a specific period. This feature, also known as lazy log truncation, helps prevent the log drive from filling up while still preserving the intended replay lag for recovery purposes. Circular logging is incompatible with lagged copies. Setting TruncationLagTime delays truncation but is superseded by ReplayLagTime.

The most direct and efficient way to exempt a specific domain from a transport rule is to use the 'The sender's domain is...' exception. This condition specifically checks the domain part of the sender's email address. Using 'The sender's IP address is in the range' is less reliable as IP addresses can change. Creating a separate, higher-priority rule to stop processing is more complex than necessary. Using a message header is a valid but less straightforward method for this common requirement.

To prevent automatic failover to a specific site, you must block the activation of database copies in that site. This is achieved by setting the -DatabaseCopyAutoActivationPolicy parameter on the Mailbox server to Blocked. This ensures that even if the server is part of the DAG and has healthy database copies, Managed Availability will not automatically activate them. A manual server switchover would be required to bring the databases online in DC3. DAC mode is necessary for site resilience but doesn't prevent failover to a specific site. Activation preference influences the target of a failover but doesn't block it.

The New-Mailbox -Room cmdlet is the correct command to create a new room mailbox, which is a specific type of resource mailbox.

The Set-CalendarProcessing cmdlet is used to configure the automated booking policies for a resource mailbox. Setting AutomateProcessing to AutoAccept fulfills the requirement for automatic acceptance, and -DeleteComments $true fulfills the requirement to remove comments.