###BeginCaseStudy###
Topic 1, Fabrikam inc.
Overview
Fabrikam. Inc. is an international manufacturing company that has 5,000 employees. The company has sales,
marketing research and human resources departments. Fabrikam has two main offices and three branch
offices. The main offices are located in New York and London. The branch offices are located in Seattle,
Montreal, and Paris. The offices connect to each other by using a WAN link. Each office connects directly to the
Internet. The WAN connections from the main offices to the branch offices are reliable.
Existing Environment
Exchange Environment
The Exchange Server organization contains servers that have either Exchange Server 2010 or Exchange Server
2013 installed. Each main office contains two Exchange Server 2013 servers. Each branch office contains one
Exchange Server 2010 server.
MX records are configured to deliver email to the offices in New York and London. Email is delivered to the
London office only if the New York office is unavailable.
Each office is configured to use a separate namespace for client access. The New York office is configured to
use a namespace of mail.fabrikam.com.
The servers in the New York and London offices are members of a database availability group (DAG).
Each mailbox database in the New York and London offices has three copies.
The technical support staff in the branch offices have administrative access to the existing Exchange servers
and are assigned Organization Management permissions.
Users from the sales department frequently send email messages that contain the Social Security number of
customers in the United States.
Problem Statements
Fabrikam identifies the following issues on the network:
Users in the Paris office report that when launching Microsoft Outlook, they receive a security alert
indicating a certificate name mismatch. The security alert is not generated when they connect to Outlook
Web Access. Users from the other offices do not report receiving the security alert.
Network administrators report that the mailbox databases in the New York office sometimes activate on
the Exchange servers in the London office, resulting in poor performance for the New York office users.
Planned Changes
Fabrikam plans to implement the following changes to the network:
Upgrade the organization to Exchange Server 2016 during the next six months.
Enable online document viewing and editing from Outlook on the web.
High Availability Requirements
Fabrikam identifies the following high-availability requirements for the planned deployment:
Mailbox databases that contain mailboxes for the New York office users must only be activated on the
servers in the London office manually.
All client access connections to the London and New York offices must use load-balanced namespaces.
The load balancing mechanism must perform health checks.
Security and compliance requirements
Fabrikam identifies the following security and compliance requirements:
After the planned upgrade, the maximum mailbox size must be 5 GB.
Administrators from the branch offices must be able to view the mailbox properties and reset the
passwords of the users, but must be prevented from changing the mailbox database configurations.
Users who are involved in legal disputes with customers must be prevented from permanently deleting
email messages pertaining to the dispute. The users must be able to delete all other messages
permanently.
If a user enters a Social Security number in an email message addressed to an external recipient, the user
must receive a notification before sending the message If the user sends the message. The message must
not be delivered. A compliance officer must be notified of the violation.
Connectivity requirements
Fabrikam identifies the following connectivity requirements:
Connections for inbound and outbound email must be initiated and terminated from an Edge Transport
server in the perimeter network.
All external client connections from the branch office users must be proxied from the New York office to
the branch offices.
The number of namespaces used for client access must be minimized.
###EndCaseStudy###
You need to recommend changes to the existing environment to meet the high-availability
requirements for the mailbox databases. What should you recommend?

A.
Run the Set-MailBoxDatabase cmdlet.
B.
Run the Set-DatabaseAvailabilityGroup cmdlet
C.
Run the Set-MailBoxServer cmdlet.
D.
Run the Set-MailBoxDatabaseCopy cmdlet.
B
0
0
B is correct
https://eightwone.com/2010/08/24/blocking-automatic-activation-in-dags/
0
0
The link you provided indicates C is correct.
0
0
Agree with you. Answer is C. The task is “Mailbox databases that contain mailboxes for the New York office users must only be activated on the servers in the London office manually”
You should use
Set-MailboxServer -Identity -DatabaseCopyAutoActivationPolicy Blocked
https://technet.microsoft.com/ru-ru/library/dd298046(v=exchg.160).aspx
0
0
Requirement says: “Mailbox databases that contain mailboxes for the New York office users must only be activated on the servers in the London office manually”
I think this means that we should prevent out-of-site activation using command:
Set-MailboxServer -Identity -DatabaseCopyAutoActivationPolicy IntrasiteOnly
So it could be C
0
0
You’re right.
The cmdlet Set-DatabaseAvailabilityGroup does not help, since it does not contain any parameters for blocking the activation of databases.
0
0
Hi,
I think you will get better explanation here why B should be the correct answer:
https://technet.microsoft.com/en-us/library/dd297934(v=exchg.160).aspx
also, I found useful this article:
http://powershell.ws/command/Set-DatabaseAvailabilityGroup/
0
0
Sorry, I don’t find the clue? Which parameter of Set-DatabaseAvailabilityGroup cmdlet affects to activation? Help me?
0
0
Answer is C.
Use the Shell to configure the activation policy for a server
This example configures the database copies on server MBX2 as blocked for activation.
Set-MailboxServer -Identity MBX2 -DatabaseCopyAutoActivationPolicy Blocked
This example configures the database copies on server MBX3 as blocked for out-of-site activation.
Set-MailboxServer -Identity MBX3 -DatabaseCopyAutoActivationPolicy IntrasiteOnly
This example configures the database copies on server MBX4 as unblocked for activation.
Set-MailboxServer -Identity MBX4 -DatabaseCopyAutoActivationPolicy Unrestricted
0
0
Answer could also be D, but you’d have to apply it to each database on each server, instead of using set-mailboxserver and applying it to each server.
Answer C takes less effort so it’s the correct answer.
0
0
From https://technet.microsoft.com/en-us/library/dd297934(v=exchg.160).aspx,
the parameter that specifics whether DAG networks should be automatically configured or not is ManualDagNetworkConfiguration
As in the HA requirements in the Case Study,
“Mailbox databases that contain mailboxes for New York office users must only be activated on the servers in the London office manually”
Hence, we have to manually configure the New York mailbox databases within the DAG (from London)
0
0
The only relevant part of this is that you quote the question properly. The link and your comments have nothing to do with the question.
0
0
If you block the activation using Set-MailboxServer in London Office, the local (London office) Databases are also denied auto activation, which is not the case.
It is clearly written, to be be applied only for NY users databases activation on London servers, not for local London databases.
So I’d rather use —
Suspend-MailboxDatabaseCopy –identity \ –ActivationOnly
0
0
I mean –
Suspend-MailboxDatabaseCopy –identity \ –ActivationOnly
0
0
Suspend-MailboxDatabaseCopy –identity DatabaseID\LondonServerID –ActivationOnly
0
0
The answer is C “Run the Set-MailBoxServer cmdlet”
Reference: https://technet.microsoft.com/en-us/library/dd298046(v=exchg.160).aspx
Scenario is relevant to this example.
This example configures the database copies on server MBX3 as blocked for out-of-site activation.
Set-MailboxServer -Identity MBX3 -DatabaseCopyAutoActivationPolicy IntrasiteOnly
0
0
Besides, part of that new 104Q 70-345 dumps are available here:
https://drive.google.com/open?id=0B-ob6L_QjGLpck5vRk5XUVFQb00
Best Regards!
0
0
As far as I understand:
– the main office is composed of NY and London
– the main office hosts several databases, let’s just go with two for the sake of simplification
– there’s a DAG configured in the main office that spans between NY and London
– all active copies are on NY, London only hosts passive copies
– we want to prevent the automatic activation of DB copies on the London site
I believe we need to run Set-MailboxServer -Identity -DatabaseCopyAutoActivationPolicy Blocked. IMO. there’s no reason to set it to intra-site only because I don’t see any benefit. London does not have any active copies.
0
0
I agree with the C answeer. Read the article below:
http://www.msexchange.org/kbase/ExchangeServerTips/ExchangeServer2010/HighAvailability/PreventDatabaseCopiesfromAutomaticallyMountinginotherSites.html
0
0