Overview

General Overview

ADatum Corporation is a real estate firm that has offices throughout North America.

ADatum has a main office and four branch offices. The main office is located in Seattle. The branch offices are located in New York, Montreal, Denver, and Vancouver.

Existing Environment

Network Infrastructure

The network contains one Active Directory domain namedADatum.com. Each office contains one domain controller.

Each office has a 100-Mbps connection to the Internet that is 20 percent saturated on average. The offices connect to each other through the Internet by using VPN appliances.

ADatum uses the public IP addresses shown in the following table.

SQL Server Infrastructure

In the main office, ADatum hosts a Microsoft SQL Server instance on a server named SQL1. SQL1 has a 400-GB database named Listings. Log-shipped copies of Listings are present in each branch office. The copies are used for reporting. Currently, all of the SQL Server instances run SQL Server 2014 Enterprise edition.

Each branch office has an application server that hosts an application named App1. App1 is configured to connect to the Listings database on each local SQL Server instance for reporting and to connect to the SQL Server instance in the main office for any updates to property listings.

The main office also has an application server that hosts App1. The application server connects to the local Listings database for reporting and for any updates to the property listings.

Historic activity of the Listings database shows a maximum of 475 concurrent requests from as many as 200 concurrent connections.

User Issues

Users report that, frequently, they are disconnected from the Listings database when they run reports. Users also report that there is an unacceptable delay between when a property listing is updated and when the updated listing appears in the listings reports.

Developers report concerns about the lack of a testing environment in which code changes can be validated before being deployed to the production Listings database.

Requirements

Business Requirements

ADatum identifies the following business requirements:

Minimize costs, whenever possible.

Ensure that confidential data is encrypted at all times.

Ensure that the primary

database is hosted in Microsoft Azure.

Ensure that all production databases maintain 99.9 percent availability.

Ensure that all of the data between the offices and Azure is encrypted.

Planned changes

ADatum plans to implement the following changes:

Move

the primary database to Azure.

Implement a data warehouse for reporting to offload reporting from the transactional Listings database.

Technical Requirements

ADatum identifies the following technical requirements:

A test environment that has a 200-GB

subset of data from the Listings database must be implemented. The new database will be named ListTest. The new test environment will have a maximum of 10 concurrent connections.

The migration of the Listings database must be completed in less than 60 minu

tes. During the migration, data must be prevented from being modified.

The firewall settings of the Azure SQL databases must be configured to provide access to the main office only.

Changes to the settings and the properties of the Listings database must b

e audited at all times.

Access to the Clients table must be audited and data from the audit must be queryable.

The query performance of the ListTest database must be monitored at all times.

Reporting must be offloaded from the transactional Listings databa

se.

High-Availability and Recovery Requirements

ADatum identifies the following high-availability and recovery requirements:

All production databases must support automatic failover.

Backups for the Listings database must be stored in Azure.

The database

must be recoverable if a major data loss occurs.

A weekly backup of the ListTest database must be maintained on-premises.

SQL1 must be integrated into the high-availability solution as a reporting server.

You are evaluating whether an Azure SQL Database

elastic database pool suits your workload and usage patterns.

What are two possible ways to identify the elastic database transaction units (eDTUs)? Each correct answer presents a complete solution.

A. Aggregate data from sys.dm_os_wait_stats.

B. Run

the Database Engine Tuning Advisor.

C. Run the Service Tier Advisor.

D. Aggregate data from sys.dm_db_resource_stats.

E. Aggregate data from sys.dm_os_performance_counters.

Explanation: