NEW QUESTION: 2
Das Scrum-of-Scrums-Meeting soll es Clustern von Scrum-Teams ermöglichen, ihre Arbeit zu diskutieren, wobei der Schwerpunkt auf Überlappungs- und Integrationsbereichen liegt.
Wer sollte im Namen Ihres Scrum-Teams an den Scrum-of-Scrum-Meetings teilnehmen?
A. DSDM
B. Lean
C. DevOps
D. Waterfall
Answer: D

NEW QUESTION: 3
You are evaluating the implementation of SQL Server Database Mirroring on new SQL Server Servers for the planned Lync Server 2013 deployment.
You need to recommend which tasks must be performed to prepare SQL Server Database Mirroring for Lync Server 2013.
Which two actions should you recommend?
(Each correct answer presents part of the solution. Choose two.)
A. Run the Invoke-CsDatabaseFailover cmdlet.
B. Run the Update-CsUserDatabase cmdlet.
C. On the Front End Servers, install Failover Clustering.
D. From the Topology Builder, publish the Topology and install the Databases.
E. From the Topology Builder, create a new Enterprise Edition Front End Pool and a new SQL Server database, SQL Server Database Mirroring, and a Witness.
F. On the SQL Server servers, install Failover Clustering.
Answer: D,E
Explanation:
http://technet.microsoft.com/en-us/library/jj204992.aspx
DEPLOYING SQL MIRRORING FOR BACK END SERVER HIGH AVAILABILITY
LYNC SERVER 2013 TOPIC LAST MODIFIED: 2012-10-11
To be able to deploy SQL mirroring, your servers must run a minimum of SQL Server 2008 R2. This version
must run on all the involved servers: the primary, mirror, and the witness. For details, see http://
go.microsoft.com/fwlink/p/?linkid=3052&kbid=2083921.
In general, setting up SQL mirroring between the two Back End Servers with a witness requires the
following:
The primary server's version of SQL Server must support SQL mirroring.
The primary, mirror, and the witness (if deployed) must have the same version of SQL Server.
The primary and the mirror must have the same edition of SQL Server. The witness may have a different
edition.
For SQL best practices in terms of what SQL versions are supported for a Witness role, see "Database
Mirroring Witness" in the MSDN Library at http://go.microsoft.com/fwlink/p/?LinkId=247345.
You use Topology Builder to deploy SQL mirroring. You select an option in Topology Builder to mirror the
databases, and Topology Builder sets up the mirroring (including setting up a witness, if you want) when
you publish the topology. Note that you set up or remove the witness at the same time you set up or remove
the mirror. There is no separate command to deploy or remove only a witness.
To configure server mirroring, you must first set up SQL database permissions correctly. For details, see
"Set Up Login Accounts for Database Mirroring or AlwaysOn Availability Groups (SQL Server)" at http://
go.microsoft.com/fwlink/p/?LinkId=268454.
With SQL mirroring, database recovery mode is always set to Full, which means you must closely monitor
transaction log size and back up transaction logs on a regular basis to avoid running out of disk space on
the Back End Servers. The frequency of transaction log backups depends on the log growth rate, which in
turn depends on database transactions incurred by user activities on the Front End pool. We recommend
that you determine how much transaction log growth is expected for your Lync deployment workload so that
you can do the planning accordingly. The following articles provide additional information on SQL backup
and log management:
Database recovery models: "Recovery Models (SQL Server)" at http://go.microsoft.com/fwlink/p/?
LinkId=268446
Backup overview: "Backup Overview (SQL Server)" at http://go.microsoft.com/fwlink/p/?LinkId=268449
Backup transaction log: "Backup a Transaction Log (SQL Server)" at http://go.microsoft.com/fwlink/p/?
LinkId=268452
With SQL mirroring, you can either configure the topology for mirroring when you create the pools, or after the pools are already created.
IMPORTANT:
Using Topology Builder or cmdlets to set up and remove SQL mirroring is supported only when the primary, mirror, and witness (if desired) servers all belong to the same domain. If you want to set up SQL mirroring among servers in different domains, see your SQL Server documentation.
TO CONFIGURE SQL MIRRORING WHILE CREATING A POOL IN TOPOLOGY BUILDER
On the Define the SQL Store page, click New next to the SQL store box.
On the Define new SQL Store page, specify the primary store, select This SQL instance is in
mirroring relation, specify the SQL mirroring port number (the default is 5022), and then click OK.
Back on the Define the SQL store page, select Enable SQL Store mirroring.
In the Define new SQL Store page, specify the SQL store to be used as the mirror. Select This
SQL instance is in mirroring relation, specify the port number (the default is 5022), and then
click OK.
If you want a witness for this mirror, do the following:
Select Use SQL mirroring witness to enable automatic failover.
In the Define the SQL Store page, select Use SQL mirroring witness to enable
automatic failover, and specify the SQL store to be used as the witness.
Specify the port number (the default is 7022) and click OK.
After you are done defining your Front End pool and all other roles in your topology, use Topology Builder to
publish the topology. When the topology is published, if the Front End pool that hosts Central Management
store has SQL mirroring enabled, you will see an option to create both primary and mirror SQL store
databases.
Click Settings, and type the path to use as the file share for the mirroring backup.
Click OK and then Next to create the databases and publish the topology. The mirroring and the witness
(if specified) will be deployed.
You can use Topology Builder to edit the properties of an already existing pool to enable SQL mirroring.
TO ADD SQL MIRRORING TO AN EXISTING FRONT END POOL IN TOPOLOGY BUILDER
In Topology Builder, right-click the pool and then click Edit Properties.
Select Enable SQL Store Mirroring, and then click New next to Mirroring SQL Store.
Specify the SQL store that you want to use as the mirror.
Select This SQL instance is in mirroring relation, specify the SQL mirroring port number the
default port is 5022), and then click OK.
If you want to configure a witness, select Use SQL mirroring witness to enable automatic
failover, and click New.
Specify the SQL store that you want to use as the witness.
Select This SQL instance is in mirroring relation, specify the SQL mirroring port number (the
default port is 7022), and then click OK.
Click OK.
Publish the topology. When you do so, you will be prompted to install the database.
You must then install the database before going on to the next procedure.
You should keep the following in mind when setting up SQL mirroring:
If a mirroring endpoint already exists, it will be reused using the ports defined there, and will ignore the ones
you specify in the topology.
Any port already allocated for other applications on the same server, including those for other SQL
instances, should not be used for the installed SQL instances at hand. This implies that if you have more
than one SQL instance installed on the same server, they must not use the same port for mirroring. For
details, see the following articles:
"Specify a Server Network Address (Database Mirroring)" in the MSDN Library at http://go.microsoft.com/
fwlink/p/?LinkId=247346
"The Database Mirroring Endpoint (SQL Server)" at http://go.microsoft.com/fwlink/p/?LinkId=247347
USING LYNC SERVER MANAGEMENT SHELL CMDLETS TO SET UP SQL MIRRORING
The easiest way to set up mirroring is by using Topology Builder, but you can also do so using cmdlets. Open a Lync Server Management Shell window and run the following cmdlet: Install-CsMirrorDatabase [-ConfiguredDatabases] [-ForInstance] [-ForDefaultInstance] [-DatabaseType <Application | Archiving | CentralMgmt | Monitoring | User | BIStaging | PersistentChat | PersistentChatCompliance >] -FileShare <fileshare> -SqlServerFqdn <primarySqlserverFqdn> [-SqlInstanceName] [-DatabasePathMap] [-ExcludeDatabaseList] [-DropExistingDatabasesOnMirror] Verbose
For example: Install-CsMirrorDatabase -ConfiguredDatabases -FileShare \\PRIMARYBE\csdatabackup -SqlServerFqdn primaryBE.contoso.com -DropExistingDatabasesOnMirror -Verbose
You will see the following: Database Name:rtcxds Data File:D:\CsData\BackendStore\rtc\DbPath\rtcxds.mdf Log File:D:\CsData\BackendStore\rtc\LogPath\rtcxds.ldf Primary SQL: e04-ocs.los_a.lsipt.local\rtc Account: LOS_A\e04-ocs$ Mirror SQL: K16-ocs.los_a.lsipt.local\rtc Account: LOS_A\K16-ocs$ Witness SQL : AB14-lct.los_a.lsipt.local\rtc Account: LOS_A\AB14-lct$ Database Name:rtcshared Data File:D:\CsData\BackendStore\rtc\DbPath\rtcshared.mdf Log File:D:\CsData\BackendStore\rtc\LogPath\rtcshared.ldf Primary SQL: e04-ocs.los_a.lsipt.local\rtc Account: LOS_A\e04-ocs$ Mirror SQL: K16-ocs.los_a.lsipt.local\rtc Account: LOS_A\K16-ocs$ Witness SQL : AB14-lct.los_a.lsipt.local\rtc Account: LOS_A\AB14-lct$ Database Name:rtcab Data File:D:\CsData\ABSStore\rtc\DbPath\rtcab.mdf
Log File:D:\CsData\ABSStore\rtc\LogPath\rtcab.ldf
Primary SQL: e04-ocs.los_a.lsipt.local\rtc
Account: LOS_A\e04-ocs$
Mirror SQL: K16-ocs.los_a.lsipt.local\rtc
Account: LOS_A\K16-ocs$
Witness SQL : AB14-lct.los_a.lsipt.local\rtc
Account: LOS_A\AB14-lct$
Database Name:rgsconfig
Data File:D:\CsData\ApplicationStore\rtc\DbPath\rgsconfig.mdf
Log File:D:\CsData\ApplicationStore\rtc\LogPath\rgsconfig.ldf
Primary SQL: e04-ocs.los_a.lsipt.local\rtc
Account: LOS_A\e04-ocs$
Mirror SQL: K16-ocs.los_a.lsipt.local\rtc
Account: LOS_A\K16-ocs$
Witness SQL : AB14-lct.los_a.lsipt.local\rtc
Account: LOS_A\AB14-lct$
Database Name:rgsdyn
Data File:D:\CsData\ApplicationStore\rtc\DbPath\rgsdyn.mdf
Log File:D:\CsData\ApplicationStore\rtc\LogPath\rgsdyn.ldf
Primary SQL: e04-ocs.los_a.lsipt.local\rtc
Account: LOS_A\e04-ocs$
Mirror SQL: K16-ocs.los_a.lsipt.local\rtc
Account: LOS_A\K16-ocs$
Witness SQL : AB14-lct.los_a.lsipt.local\rtc
Account: LOS_A\AB14-lct$
Database Name:cpsdyn
Data File:D:\CsData\ApplicationStore\rtc\DbPath\cpsdyn.mdf
Log File:D:\CsData\ApplicationStore\rtc\LogPath\cpsdyn.ldf
Primary SQL: e04-ocs.los_a.lsipt.local\rtc
Account: LOS_A\e04-ocs$
Mirror SQL: K16-ocs.los_a.lsipt.local\rtc
Account: LOS_A\K16-ocs$
Witness SQL : AB14-lct.los_a.lsipt.local\rtc
Account: LOS_A\AB14-lct$
Database Name:xds
Data File:D:\CsData\CentralMgmtStore\rtc\DbPath\xds.mdf
Log File:D:\CsData\CentralMgmtStore\rtc\LogPath\xds.ldf
Primary SQL: e04-ocs.los_a.lsipt.local\rtc
Account: LOS_A\e04-ocs$
Mirror SQL: K16-ocs.los_a.lsipt.local\rtc
Account: LOS_A\K16-ocs$
Witness SQL : AB14-lct.los_a.lsipt.local\rtc
Account: LOS_A\AB14-lct$
Database Name:lis
Data File:D:\CsData\CentralMgmtStore\rtc\DbPath\lis.mdf
Log File:D:\CsData\CentralMgmtStore\rtc\LogPath\lis.ldf
Primary SQL: e04-ocs.los_a.lsipt.local\rtc
Account: LOS_A\e04-ocs$
Mirror SQL: K16-ocs.los_a.lsipt.local\rtc
Account: LOS_A\K16-ocs$
Witness SQL : AB14-lct.los_a.lsipt.local\rtc
Account: LOS_A\AB14-lct$
[Y] Yes [A] Yes to All [N] No
[L] No to All [S] Suspend [?] Help (default is "Y"):
Verify the following: Port 5022 is accessible through the firewall if Windows Firewall is enabled in the primary SQL Server e04ocs.los_a.lsipt.local\rtc. Port 5022 is accessible through the firewall if Windows Firewall is enabled in the mirror SQL Server K16ocs.los_a.lsipt.local\rtc. Port 7022 is accessible through the firewall if Windows Firewall is enabled in the witness SQL Server AB14lct.los_a.lsipt.local\rtc. Accounts running the SQL Servers on all primary and mirror SQL servers have read/write permission to the file share \\E04-OCS\csdatabackup Verify that the Windows Management Instrumentation (WMI) provider is running on all these servers. The cmdlet uses this provider to find the account information for SQL Server services running on all primary,
mirror and witness servers.
Verify that the account running this cmdlet has permission to create the folders for the data and log files for
all the mirror servers.
Note that the user account that the SQL instance uses to run must have read/write permission to the file
share. If the file share is on a different server, and the SQL instance runs a local system account, you must
grant file share permissions to the server that hosts the SQL instance.
Type A and press ENTER.
The mirroring will be configured.
Install-CsMirrorDatabase installs the mirror and configures mirroring for all the databases that are
present on the primary SQL store. If you want to configure mirroring for only specific databases, you can
use the -DatabaseType option, or if you want to configure mirroring for all databases except for a few, you
can use the -ExcludeDatabaseList option, along with a comma-separated list of database names to
exclude.
For example, if you add the following option to Install-CsMirrorDatabase, all databases except rtcab
and rtcxds will be mirrored.
-ExcludeDatabaseList rtcab,rtcxds
For example, if you add the following option to Install-CsMirrorDatabase, only the rtcab, rtcshared,
and rtcxds databases will be mirrored.
-DatabaseType User
REMOVING OR CHANGING SQL MIRRORING
To remove the SQL mirroring of a pool in Topology Builder, you must first use a cmdlet to remove the mirror
in SQL Server. You can then use Topology Builder to remove the mirror from the topology. To remove the
mirror in SQL Server, use the following cmdlet:
Uninstall-CsMirrorDatabase -SqlServerFqdn <SQLServer FQDN> [-SqlInstanceName <SQLServer instance
name>] -DatabaseType <Application | Archiving | CentralMgmt | Monitoring | User | BIStaging |
PersistentChat | PersistentChatCompliance> [-DropExistingDatabasesOnMirror] [-Verbose]
For example, to remove mirroring and drop the databases for the User databases, type the following:
Uninstall-CsMirrorDatabase -SqlServerFqdn primaryBE.contoso.com -SqlInstanceName rtc -Verbose -
DatabaseType User -DropExistingDatabasesOnMirror
The -DropExistingDatabasesOnMirror option causes the affected databases to be deleted from the mirror.
Then, to remove the mirror from the topology, do the following:
In Topology Builder, right-click the pool and click Edit Properties.
Uncheck Enable SQL Store Mirroring and click OK.
Publish the topology.
IMPORTANT:
Whenever you make a change to a Back End Database mirroring relationship, you must restart all the Front
End Servers in the pool.
For a change in mirroring, (such as changing the location of a mirror), you must use Topology Builder to
perform these three steps:
Remove mirroring from the old mirror server.
Add mirroring to the new mirror server.
Publish the topology.
REMOVING A MIRRORING WITNESS
Use this procedure if you need to remove the witness from a Back End Server mirroring configuration.
In Topology Builder, right-click the pool and click Edit Properties.
Uncheck Use SQL Server mirroring witness to enable automatic failover and click OK.
Publish the topology.
After publishing the topology, Topology Builder you will see a message that includes the following
Run the Uninstall-CsMirrorDatabase cmdlet to remove databases that are paired with following primary
databases.
However, do not follow that step, and do not type Uninstall-CsMirrorDatabase as that would uninstall the
entire mirroring configuration.
To remove just the witness from the SQL Server configuration, follow the instructions in "Remove the
Witness from a Database Mirroring Session (SQL Server)" at http://go.microsoft.com/fwlink/p/?
LinkId=268456.
Topic 2, Margie's Travel
Overview
General Overview
Margie's Travel is an executive travel company that has 7,000 employees. The company has a sales department and a research department.
Physical Locations
The company has a main office and two branch offices.
The main office is located in Montreal.
The branch offices are located in New York and Seattle.
The number of users in each office is shown in the following table.

All offices connect to each other by using a WAN link.
Existing Environment
Active Directory Environment
The network contains one Active Directory forest named margiestravel.com. Each office is configured as an Active Directory site.
Lync Server Environment
The company has a Lync Server 2010 infrastructure in the Montreal office.
The network contains four servers.
The servers are configured as shown in the following table.

Lync Server 2013 Standard Edition is deployed in the Montreal office as a pilot on a
separate network segment.
You create several test users on the Lync Server 2013 pilot.
User Issue
An administrator modifies the global client version policy of the Lync Server 2013 pilot deployment. After the modification, Lync Server 2013 users report that they fail to sign in to
Microsoft Lync 2010 and they receive the following error message.

Requirements
Planned Changes
After a successful pilot program, the company plans to deploy Lync Server 2013 on the
production network for all users.
The Lync Server 2013 deployment will include the following roles:
Edge Server
Front End Server
Mediation Server
Monitoring Server
Office Web Apps Server
Lync Server 2013 and Lync Server 2010 will coexist for six month.
Monitoring Requirements
A monitoring solution must save call quality data for 180 days.
Backup Requirements
An administrator plans to perform a weekly manual backup of the Lync Server databases. The backup files will be copied to an offsite location.
Conferencing Requirements
The company plans to implement a conferencing solution to meet the following requirements:
The company's executives must be able to create conferences that contain up to 250
participants.
The company's managers must be able to create conferences that contain up to 50 participants.
All other users must be prevented from creating conferences that contain more than 15 users.