70-384 Exam
Most recent 70-384 Exam Study Guides With New Update Exam Questions
Master the 70-384 Recertification for MCSE: Communication content and be ready for exam day success quickly with this Actualtests 70-384 rapidshare. We guarantee it!We make it a reality and give you real 70-384 questions in our Microsoft 70-384 braindumps.Latest 100% VALID Microsoft 70-384 Exam Questions Dumps at below page. You can use our Microsoft 70-384 braindumps and pass your exam.
Q21. - (Topic 10)
An administrator makes several security changes to the firewalls.
After you deploy Enterprise Voice, remote users report that they fail to access their voice mail by using the Call Voice Mail option in the Lync client.
You verify that the users can access their voice mail by dialing the subscriber access number.
You need to ensure that the users can access their voice mail by clicking Call Voice Mail.
Which two sets of ports should you open? (Each correct answer presents part of the solution. Choose two.)
A. TCP 443 and UDP 3478 on the internal firewall
B. TCP 443 and UDP 3478 on the external firewall
C. TCP 5062 and 8057 on the internal firewall
D. UDP 50,000 to 59,999 on the external firewall
E. TCP 5062 and 8057 on the external firewall
F. UDP 50,000 to 59,999 on the internal firewall
Answer: A,B
144. - (Topic 10)
You need to configure DHCP to support the technical requirement for the Lync Phone Edition devices.
Which DHCP options should you include in the solution? (Each correct answer presents part of the solution. Choose all that apply.)
A. 40
B. 43
C. 80
D. 120
E. 144
Answer: B,D
Explanation:
B: DHCP Option 43
Option 43 is not really a single option but a number of sub-options which tell the phone
where to locate the Certificate Provisioning service on the Lync server.
D: DHCP Option 120
Once the certificate is downloaded to the phone then a valid Lync registrar server needs to
be located. The value of Option 120 will be the FQDN of the Lync server which will handle
authentication requests from the phones.
* From scenario:
Microsoft Lync Phone Edition devices must be supported.
Reference: Configuring Lync Server for Phone Edition Devices
Q22. - (Topic 12)
You have a Lync Server 2013 infrastructure and a Microsoft Exchange Server 2013
organization.
Unified Messaging (UM) integration is enabled.
You need to prevent the use of call answering rules.
Which Windows PowerShell command should you run?
A. Set-CSVoicePolicy
B. Set-UMMailboxPolicy
C. Remove-UMCallAnsweringRule
D. Set-UMDialPlan
Answer: D
Q23. HOTSPOT - (Topic 6)
You have a Lync Server 2013 infrastructure. The infrastructure has monitoring reports and Call Admission Control (CAC) deployed.
A user named User1 reports poor audio quality during web conferences. You need to identify whether User1 uses the Siren codec for audio conferences.
Which monitoring report should you use from the Microsoft Lync Server 2013 Control Panel?
To answer, select the appropriate report in the answer area.
Answer:
Q24. HOTSPOT - (Topic 12)
Your company has two offices. The offices are located in New York and Amsterdam. The dialing habits of the users in each office are shown in the following table.
You need to create a dial plan for the users in the Amsterdam office.
Which match patterns should you use in the normalization rules? To answer, select the appropriate match patterns in the answer area.
Answer:
Q25. - (Topic 7)
You need to prepare the Enterprise Voice infrastructure for E911.
Which two cmdlets should you run? (Each correct answer presents part of the solution. Choose two.)
A. Set-CsPstnUsage
B. Enable-CSPublicProvider
C. Set-CsVoiceConfiguration
D. New-CsVoiceRoute
E. New-CsVoiceRoutingPolicy
Answer: A,D
Explanation:
http://technet.microsoft.com/en-us/library/gg398496.aspx
Q26. - (Topic 1)
You need to recommend a solution to resolve the audio issues for the users in the Boston office.
Which three possible recommendations should you include in the solution? (Each correct answer presents a complete solution. Choose three.)
A. user services
B. Quality of Service (QoS)
C. Call Admission Control (CAC)
D. a location policy
E. a conferencing policy
Answer: B,C,E
Q27. HOTSPOT - (Topic 12)
You have a Lync Server 2013 infrastructure.
You plan to configure Exchange Online to host voice mail. You need to identify where to perform the following actions:
Configure the hosted voice mail policy.
Set the external access number for the voice mail.
Enable a user for Unified Messaging (UM).
Configure the Contact object used for the hosted voice mail.
Define a Unified Messaging (UM) IP gateway.
Which environment should you identify for each action?
.....
To answer, select the appropriate environment for each task in the answer area.
Answer:
Q28. - (Topic 4)
You are evaluating the migration of the response groups.
You need to identify which statement correctly describes the migration of the response
groups to Lync Server 2013.
Which statement should you identify?
A. All of the response groups must be recreated after the users are moved to Lync Server 2013.
B. All of the response groups must be migrated in a single migration operation.
C. An administrator must modify the topology after the response groups are migrated to Lync Server 2013.
D. An administrator must re-enable all users for Enterprise Voice after the response groups are migrated to Lync Server 2013.
Answer: B
Q29. - (Topic 2)
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. 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.
B. From the Topology Builder, publish the topology and install the databases.
C. On the SQL Server servers, install Failover Clustering.
D. On the Front End Servers, install Failover Clustering.
E. Run the Update-CsUserDatabase cmdlet.
F. Run the Invoke-CsDatabaseFailover cmdlet.
Answer: A,B
Explanation: http://technet.microsoft.com/en-us/library/jj204992.aspx DEPLOYING SQL MIRRORING FOR BACK END SERVER HIGH AVAILABILITY
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 e04-ocs.los_a.lsipt.local\rtc. Port 5022 is accessible through the firewall if Windows Firewall is enabled in the mirror SQL Server K16-ocs.los_a.lsipt.local\rtc. Port 7022 is accessible through the firewall if Windows Firewall is enabled in the witness SQL Server AB14-lct.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.
Q30. HOTSPOT - (Topic 6)
You have a Lync Server 2013 infrastructure.
You plan to deploy Persistent Chat features to meet the following requirements:
Support up to 50,000 concurrent users.
Enable the Persistent Chat Server Compliance service.
Ensure that all of the features are automatically available if a single server fails.
You need to identify the minimum number of Front End Servers and Microsoft SQL Server Back End Servers that are required for the planned deployment.
How many servers should you identify? (To answer, select the appropriate number of servers for each component in the answer area.)
...
Answer: