Quiz Designing and Implementing Cloud Data Platform Solutions

TESTLET-1.
Overview
General Overview
Proseware, Inc. is a software engineering company that has 100 employees. Proseware has sales,
marketing, accounts, human resources IT, and development departments.
The IT department has one team dedicated to managing the internal resources and one team dedicated to
managing customer resources, which are located in the company’s hosting environment.
Proseware develops websites, basic web apps, and custom web apps. The websites and the apps are
hosted and maintained in the hosting environment of Proseware.
Physical Locations
Proseware has two offices located in Seattle and Montreal. The Seattle office contains all of the hardware
required to host its customers’ websites, web apps, and databases. The Seattle office contains the IT team
for the hosting environment.
The Montreal office contains all of the hardware required to host the company’s internal applications,
databases, and websites.
Each office connects directly to the Internet. Testing reveals that the minimum latency from the offices to
Microsoft Azure is 20 ms.
Existing Environment
InternalMicrosoft SQL Server Environment
Proseware uses a custom customer relationship management (CRM) application.
The internal Microsoft SQL Server environment contains two physical servers named CRM-A and CRM-B.
Both servers run SQL Server 2012 Standard and host databases for the CRM application.
CRM-A hosts the principal instance and CRM-B hosts the mirrored instance of the CRM database. СRM-A
also hosts databases for several other applications that are used by the company’s internal applications.
CRM-A hasa quad core processor and 12 GB of RAM. CRM-В has a dual core processor and 8 GB of
RAM.
Custom Web Applications Environment
Some Proseware customers request custom web-based applications that require more than just
databases, such as SQL Server Integration Services (SSIS) and CLR stored procedures.
Proseware uses a Hyper-V server named Host1. Host1 has four instances of SQL Server 2014 Enterprise
in the host operating system. The instances are mirrored on a server named Host2.
Host1 also hosts four virtual machines named VM1, VM2, VM3, and VM4. VM1 has SQL Server 2005
Standard installed. VM2 has SQL Server 2005 Enterprise Edition installed. VM3 has SQL Server 2008
Standard Edition installed. VM4 has SQL Server 2008 R2 Standard Edition installed.
Host1uses a SAN to store all of the data and log files for the four SQL Server instances and the four virtual
machines.
Websites and Basic Web Apps Environment
Proseware has two physical servers named WebServer1 and WebData1. WebServer1 hosts basic web
apps and websites for its customers. WebData1 has a database for each website and each basic web app
that Proseware hosts. WebData1 has four cores and 8 GB of RAM.
Each website database contains customer information for billing purposes. Proseware generates a
consolidated report that contains data from all of these databases.
The relevant databases on WebData1 are:
- CWDB: Currently 60 GB and is not expected to exceed 100 GB. CWDB contains a table named
PersonalInfo.
- MovieReviewDB: Currently 5 GB and is not expected to exceed 10 GB.
Marketing Department
Proseware has a web app for the marketing department. The web app uses an Azure SQL database.
Managers in the marketing department occasionally bulk load data by using a custom application. The
database is updated daily.
Problem Statements
Proseware identifies the following issues:
- Lack of planning and knowledge has complicated the database environment.
- Customers who have web apps hosted on WebServer1 report frequent outages caused by failures on
WebData1. The current uptime is less than 90 percent.
- Internally, users complain of slow performance by the CRM application when the databases fail over to
CRM-B.
- WebData1 has no high-availability option for the databases or the server.
- An internal licensing audit ofSQL Server identifies that Proseware is non-compliant. Host1, CRM-A, and
CRM-В are licensed properly. VM1, VM2, VM3, VM4, and WebData1 are unlicensed.
Business Requirements
Proseware identifies the following business requirements:
- Upgrade the infrastructure to address the issues reported by the internal users and customers.
- Minimize upgrade costs associated with purchasing hardware and software.
- Ensure that all software is licensed properly.
- Minimize the complexity of the database environment.
- Consolidate the instances of SQL Server that support the custom web app environment.
- Implement a service level agreement (SLA) of 99.95 percent uptime for the website and basic web app
environment.
- Implement a disaster recovery environment in Azure for the CRM application.
- Ensure that any changes to the SQL Server environments either maintain or increase overall
performance.
- Migrate all web front ends to Azure.
- Reuse licenses, whenever possible.
- Minimize the administrative effort required to generate the internalreports from the website databases.
Security Requirements
Proseware hosts a database for a company named Contoso, Ltd. Currently, all of the employees at
Contoso can access all of the data in the database.
Contoso plans to limit user access to the CWDU database so that customer service representatives can
see only the data from the PersonalInfo table that relates to their own customers.

TESTLET-1.
Overview
General Overview
Proseware, Inc. is a software engineering company that has 100 employees. Proseware has sales,
marketing, accounts, human resources IT, and development departments.
The IT department has one team dedicated to managing the internal resources and one team dedicated to
managing customer resources, which are located in the company’s hosting environment.
Proseware develops websites, basic web apps, and custom web apps. The websites and the apps are
hosted and maintained in the hosting environment of Proseware.
Physical Locations
Proseware has two offices located in Seattle and Montreal. The Seattle office contains all of the hardware
required to host its customers’ websites, web apps, and databases. The Seattle office contains the IT team
for the hosting environment.
The Montreal office contains all of the hardware required to host the company’s internal applications,
databases, and websites.
Each office connects directly to the Internet. Testing reveals that the minimum latency from the offices to
Microsoft Azure is 20 ms.
Existing Environment
InternalMicrosoft SQL Server Environment
Proseware uses a custom customer relationship management (CRM) application.
The internal Microsoft SQL Server environment contains two physical servers named CRM-A and CRM-B.
Both servers run SQL Server 2012 Standard and host databases for the CRM application.
CRM-A hosts the principal instance and CRM-B hosts the mirrored instance of the CRM database. СRM-A
also hosts databases for several other applications that are used by the company’s internal applications.
CRM-A hasa quad core processor and 12 GB of RAM. CRM-В has a dual core processor and 8 GB of
RAM.
Custom Web Applications Environment
Some Proseware customers request custom web-based applications that require more than just
databases, such as SQL Server Integration Services (SSIS) and CLR stored procedures.
Proseware uses a Hyper-V server named Host1. Host1 has four instances of SQL Server 2014 Enterprise
in the host operating system. The instances are mirrored on a server named Host2.
Host1 also hosts four virtual machines named VM1, VM2, VM3, and VM4. VM1 has SQL Server 2005
Standard installed. VM2 has SQL Server 2005 Enterprise Edition installed. VM3 has SQL Server 2008
Standard Edition installed. VM4 has SQL Server 2008 R2 Standard Edition installed.
Host1uses a SAN to store all of the data and log files for the four SQL Server instances and the four virtual
machines.
Websites and Basic Web Apps Environment
Proseware has two physical servers named WebServer1 and WebData1. WebServer1 hosts basic web
apps and websites for its customers. WebData1 has a database for each website and each basic web app
that Proseware hosts. WebData1 has four cores and 8 GB of RAM.
Each website database contains customer information for billing purposes. Proseware generates a
consolidated report that contains data from all of these databases.
The relevant databases on WebData1 are:
- CWDB: Currently 60 GB and is not expected to exceed 100 GB. CWDB contains a table named
PersonalInfo.
- MovieReviewDB: Currently 5 GB and is not expected to exceed 10 GB.
Marketing Department
Proseware has a web app for the marketing department. The web app uses an Azure SQL database.
Managers in the marketing department occasionally bulk load data by using a custom application. The
database is updated daily.
Problem Statements
Proseware identifies the following issues:
- Lack of planning and knowledge has complicated the database environment.
- Customers who have web apps hosted on WebServer1 report frequent outages caused by failures on
WebData1. The current uptime is less than 90 percent.
- Internally, users complain of slow performance by the CRM application when the databases fail over to
CRM-B.
- WebData1 has no high-availability option for the databases or the server.
- An internal licensing audit ofSQL Server identifies that Proseware is non-compliant. Host1, CRM-A, and
CRM-В are licensed properly. VM1, VM2, VM3, VM4, and WebData1 are unlicensed.
Business Requirements
Proseware identifies the following business requirements:
- Upgrade the infrastructure to address the issues reported by the internal users and customers.
- Minimize upgrade costs associated with purchasing hardware and software.
- Ensure that all software is licensed properly.
- Minimize the complexity of the database environment.
- Consolidate the instances of SQL Server that support the custom web app environment.
- Implement a service level agreement (SLA) of 99.95 percent uptime for the website and basic web app
environment.
- Implement a disaster recovery environment in Azure for the CRM application.
- Ensure that any changes to the SQL Server environments either maintain or increase overall
performance.
- Migrate all web front ends to Azure.
- Reuse licenses, whenever possible.
- Minimize the administrative effort required to generate the internalreports from the website databases.
Security Requirements
Proseware hosts a database for a company named Contoso, Ltd. Currently, all of the employees at
Contoso can access all of the data in the database.
Contoso plans to limit user access to the CWDU database so that customer service representatives can
see only the data from the PersonalInfo table that relates to their own customers.

TESTLET-1.
Overview
General Overview
Proseware, Inc. is a software engineering company that has 100 employees. Proseware has sales,
marketing, accounts, human resources IT, and development departments.
The IT department has one team dedicated to managing the internal resources and one team dedicated to
managing customer resources, which are located in the company’s hosting environment.
Proseware develops websites, basic web apps, and custom web apps. The websites and the apps are
hosted and maintained in the hosting environment of Proseware.
Physical Locations
Proseware has two offices located in Seattle and Montreal. The Seattle office contains all of the hardware
required to host its customers’ websites, web apps, and databases. The Seattle office contains the IT team
for the hosting environment.
The Montreal office contains all of the hardware required to host the company’s internal applications,
databases, and websites.
Each office connects directly to the Internet. Testing reveals that the minimum latency from the offices to
Microsoft Azure is 20 ms.
Existing Environment
InternalMicrosoft SQL Server Environment
Proseware uses a custom customer relationship management (CRM) application.
The internal Microsoft SQL Server environment contains two physical servers named CRM-A and CRM-B.
Both servers run SQL Server 2012 Standard and host databases for the CRM application.
CRM-A hosts the principal instance and CRM-B hosts the mirrored instance of the CRM database. СRM-A
also hosts databases for several other applications that are used by the company’s internal applications.
CRM-A hasa quad core processor and 12 GB of RAM. CRM-В has a dual core processor and 8 GB of
RAM.
Custom Web Applications Environment
Some Proseware customers request custom web-based applications that require more than just
databases, such as SQL Server Integration Services (SSIS) and CLR stored procedures.
Proseware uses a Hyper-V server named Host1. Host1 has four instances of SQL Server 2014 Enterprise
in the host operating system. The instances are mirrored on a server named Host2.
Host1 also hosts four virtual machines named VM1, VM2, VM3, and VM4. VM1 has SQL Server 2005
Standard installed. VM2 has SQL Server 2005 Enterprise Edition installed. VM3 has SQL Server 2008
Standard Edition installed. VM4 has SQL Server 2008 R2 Standard Edition installed.
Host1uses a SAN to store all of the data and log files for the four SQL Server instances and the four virtual
machines.
Websites and Basic Web Apps Environment
Proseware has two physical servers named WebServer1 and WebData1. WebServer1 hosts basic web
apps and websites for its customers. WebData1 has a database for each website and each basic web app
that Proseware hosts. WebData1 has four cores and 8 GB of RAM.
Each website database contains customer information for billing purposes. Proseware generates a
consolidated report that contains data from all of these databases.
The relevant databases on WebData1 are:
- CWDB: Currently 60 GB and is not expected to exceed 100 GB. CWDB contains a table named
PersonalInfo.
- MovieReviewDB: Currently 5 GB and is not expected to exceed 10 GB.
Marketing Department
Proseware has a web app for the marketing department. The web app uses an Azure SQL database.
Managers in the marketing department occasionally bulk load data by using a custom application. The
database is updated daily.
Problem Statements
Proseware identifies the following issues:
- Lack of planning and knowledge has complicated the database environment.
- Customers who have web apps hosted on WebServer1 report frequent outages caused by failures on
WebData1. The current uptime is less than 90 percent.
- Internally, users complain of slow performance by the CRM application when the databases fail over to
CRM-B.
- WebData1 has no high-availability option for the databases or the server.
- An internal licensing audit ofSQL Server identifies that Proseware is non-compliant. Host1, CRM-A, and
CRM-В are licensed properly. VM1, VM2, VM3, VM4, and WebData1 are unlicensed.
Business Requirements
Proseware identifies the following business requirements:
- Upgrade the infrastructure to address the issues reported by the internal users and customers.
- Minimize upgrade costs associated with purchasing hardware and software.
- Ensure that all software is licensed properly.
- Minimize the complexity of the database environment.
- Consolidate the instances of SQL Server that support the custom web app environment.
- Implement a service level agreement (SLA) of 99.95 percent uptime for the website and basic web app
environment.
- Implement a disaster recovery environment in Azure for the CRM application.
- Ensure that any changes to the SQL Server environments either maintain or increase overall
performance.
- Migrate all web front ends to Azure.
- Reuse licenses, whenever possible.
- Minimize the administrative effort required to generate the internalreports from the website databases.
Security Requirements
Proseware hosts a database for a company named Contoso, Ltd. Currently, all of the employees at
Contoso can access all of the data in the database.
Contoso plans to limit user access to the CWDU database so that customer service representatives can
see only the data from the PersonalInfo table that relates to their own customers.

TESTLET-1.
Overview
General Overview
Proseware, Inc. is a software engineering company that has 100 employees. Proseware has sales,
marketing, accounts, human resources IT, and development departments.
The IT department has one team dedicated to managing the internal resources and one team dedicated to
managing customer resources, which are located in the company’s hosting environment.
Proseware develops websites, basic web apps, and custom web apps. The websites and the apps are
hosted and maintained in the hosting environment of Proseware.
Physical Locations
Proseware has two offices located in Seattle and Montreal. The Seattle office contains all of the hardware
required to host its customers’ websites, web apps, and databases. The Seattle office contains the IT team
for the hosting environment.
The Montreal office contains all of the hardware required to host the company’s internal applications,
databases, and websites.
Each office connects directly to the Internet. Testing reveals that the minimum latency from the offices to
Microsoft Azure is 20 ms.
Existing Environment
InternalMicrosoft SQL Server Environment
Proseware uses a custom customer relationship management (CRM) application.
The internal Microsoft SQL Server environment contains two physical servers named CRM-A and CRM-B.
Both servers run SQL Server 2012 Standard and host databases for the CRM application.
CRM-A hosts the principal instance and CRM-B hosts the mirrored instance of the CRM database. СRM-A
also hosts databases for several other applications that are used by the company’s internal applications.
CRM-A hasa quad core processor and 12 GB of RAM. CRM-В has a dual core processor and 8 GB of
RAM.
Custom Web Applications Environment
Some Proseware customers request custom web-based applications that require more than just
databases, such as SQL Server Integration Services (SSIS) and CLR stored procedures.
Proseware uses a Hyper-V server named Host1. Host1 has four instances of SQL Server 2014 Enterprise
in the host operating system. The instances are mirrored on a server named Host2.
Host1 also hosts four virtual machines named VM1, VM2, VM3, and VM4. VM1 has SQL Server 2005
Standard installed. VM2 has SQL Server 2005 Enterprise Edition installed. VM3 has SQL Server 2008
Standard Edition installed. VM4 has SQL Server 2008 R2 Standard Edition installed.
Host1uses a SAN to store all of the data and log files for the four SQL Server instances and the four virtual
machines.
Websites and Basic Web Apps Environment
Proseware has two physical servers named WebServer1 and WebData1. WebServer1 hosts basic web
apps and websites for its customers. WebData1 has a database for each website and each basic web app
that Proseware hosts. WebData1 has four cores and 8 GB of RAM.
Each website database contains customer information for billing purposes. Proseware generates a
consolidated report that contains data from all of these databases.
The relevant databases on WebData1 are:
- CWDB: Currently 60 GB and is not expected to exceed 100 GB. CWDB contains a table named
PersonalInfo.
- MovieReviewDB: Currently 5 GB and is not expected to exceed 10 GB.
Marketing Department
Proseware has a web app for the marketing department. The web app uses an Azure SQL database.
Managers in the marketing department occasionally bulk load data by using a custom application. The
database is updated daily.
Problem Statements
Proseware identifies the following issues:
- Lack of planning and knowledge has complicated the database environment.
- Customers who have web apps hosted on WebServer1 report frequent outages caused by failures on
WebData1. The current uptime is less than 90 percent.
- Internally, users complain of slow performance by the CRM application when the databases fail over to
CRM-B.
- WebData1 has no high-availability option for the databases or the server.
- An internal licensing audit ofSQL Server identifies that Proseware is non-compliant. Host1, CRM-A, and
CRM-В are licensed properly. VM1, VM2, VM3, VM4, and WebData1 are unlicensed.
Business Requirements
Proseware identifies the following business requirements:
- Upgrade the infrastructure to address the issues reported by the internal users and customers.
- Minimize upgrade costs associated with purchasing hardware and software.
- Ensure that all software is licensed properly.
- Minimize the complexity of the database environment.
- Consolidate the instances of SQL Server that support the custom web app environment.
- Implement a service level agreement (SLA) of 99.95 percent uptime for the website and basic web app
environment.
- Implement a disaster recovery environment in Azure for the CRM application.
- Ensure that any changes to the SQL Server environments either maintain or increase overall
performance.
- Migrate all web front ends to Azure.
- Reuse licenses, whenever possible.
- Minimize the administrative effort required to generate the internalreports from the website databases.
Security Requirements
Proseware hosts a database for a company named Contoso, Ltd. Currently, all of the employees at
Contoso can access all of the data in the database.
Contoso plans to limit user access to the CWDU database so that customer service representatives can
see only the data from the PersonalInfo table that relates to their own customers.

TESTLET-2.
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 named adatum.com. Each office contains one domain
controller.
Each officehas 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.

Tap the image to zoom
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 ofthe 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 andto 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 updatesto 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 whenthey 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 encryptedat 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 toimplement 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:
- Atest 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 minutes. 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 be 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 database.
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.

TESTLET-2.
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 named adatum.com. Each office contains one domain
controller.
Each officehas 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.

Tap the image to zoom
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 ofthe 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 andto 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 updatesto 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 whenthey 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 encryptedat 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 toimplement 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:
- Atest 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 minutes. 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 be 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 database.
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.

TESTLET-2.
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 named adatum.com. Each office contains one domain
controller.
Each officehas 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.

Tap the image to zoom
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 ofthe 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 andto 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 updatesto 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 whenthey 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 encryptedat 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 toimplement 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:
- Atest 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 minutes. 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 be 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 database.
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.

TESTLET-2.
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 named adatum.com. Each office contains one domain
controller.
Each officehas 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.

Tap the image to zoom
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 ofthe 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 andto 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 updatesto 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 whenthey 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 encryptedat 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 toimplement 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:
- Atest 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 minutes. 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 be 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 database.
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.

TESTLET-3.
Overview
Contoso, Ltd. is a national scientific research company that has sales, marketing, and research
departments.
Contoso has a main office in Dallas and more than 20 satelliteoffices across the United States. Some
employees work off-site at customer locations.
Сontoso is expected to double in size during the next two years.
Existing Environment
The Microsoft SQL Server environment contains the servers configured as shown in the following table.

Tap the image to zoom
Contoso currently uses SQL Server 2008 R2 on all of the database servers. SQL01 currently requires six
cores and 50 GB of memory.
Once a day, database snapshots are taken on the mirror to provide ad hoc reporting and to load thedata
warehouse.
One report is used for ad hoc reporting by using the mirrored copy of the OLTP database.
Research Gen II is a Windows application that users currently access by using Remote Desktop.
Requirements
Business Goals
Contoso identifies the following business goals:
- Minimize the costs associated with purchasing hardware and software.
- Prevent any negative impact on performance when moving database platforms to the cloud.
- Audit user access to and query execution on all of the databases in the research department.
Planned changes
Contoso plans to implement the following changes:
- Upgrade SQL03 from SQL Server 2008 R2 to SQL Server 2014 on Windows Server 2012 R2.
- Migrate SQL01 and SQL02 to Infrastructure as a Service (IAAS) on SQL Server 2014.
- Leverage cloud services for a disaster recovery location and for high availability.
- Replace Research Gen II with a cloud-based application named One Research. The database for this
application will be migrated to a cloud service.
Departmental Requirements
Senior research project leaders must be able to upload databases to the cloud. Initially, the databases will
be less than 3 GB. Some databases may grow to 50 GB. The databases must be recoverable to any point
during the past two weeks.
The research project leaders must monitor the performance of their databases. They must view statistics,
such as query performance and overall database performance.
The marketing department plans to use cloud services to host web applications for marketing campaigns.
The databases for the web applications have the requirements shown in the following table.

Tap the image to zoom
Technical Requirements
Contoso identifies the following technical requirements:
- OLTP will be offloaded to Microsoft Azure virtual machines.
- The data for One Report must not be more than l5 minutes old.
- All of the databases for the OLTP system must be implemented on solid state drives (SSDs).
- A solution for the OLTP system must be created to provide disaster recovery and reporting between
SQL01 and SQL02.
- All databases, except for the research and marketing databases, must be recoverable to any point
during the last 30 days.
- A solution for the data warehouse system must be created to provide disaster recovery between SQL03
and an Azure virtual machine named SQL04.

TESTLET-3.
Overview
Contoso, Ltd. is a national scientific research company that has sales, marketing, and research
departments.
Contoso has a main office in Dallas and more than 20 satelliteoffices across the United States. Some
employees work off-site at customer locations.
Сontoso is expected to double in size during the next two years.
Existing Environment
The Microsoft SQL Server environment contains the servers configured as shown in the following table.

Tap the image to zoom
Contoso currently uses SQL Server 2008 R2 on all of the database servers. SQL01 currently requires six
cores and 50 GB of memory.
Once a day, database snapshots are taken on the mirror to provide ad hoc reporting and to load thedata
warehouse.
One report is used for ad hoc reporting by using the mirrored copy of the OLTP database.
Research Gen II is a Windows application that users currently access by using Remote Desktop.
Requirements
Business Goals
Contoso identifies the following business goals:
- Minimize the costs associated with purchasing hardware and software.
- Prevent any negative impact on performance when moving database platforms to the cloud.
- Audit user access to and query execution on all of the databases in the research department.
Planned changes
Contoso plans to implement the following changes:
- Upgrade SQL03 from SQL Server 2008 R2 to SQL Server 2014 on Windows Server 2012 R2.
- Migrate SQL01 and SQL02 to Infrastructure as a Service (IAAS) on SQL Server 2014.
- Leverage cloud services for a disaster recovery location and for high availability.
- Replace Research Gen II with a cloud-based application named One Research. The database for this
application will be migrated to a cloud service.
Departmental Requirements
Senior research project leaders must be able to upload databases to the cloud. Initially, the databases will
be less than 3 GB. Some databases may grow to 50 GB. The databases must be recoverable to any point
during the past two weeks.
The research project leaders must monitor the performance of their databases. They must view statistics,
such as query performance and overall database performance.
The marketing department plans to use cloud services to host web applications for marketing campaigns.
The databases for the web applications have the requirements shown in the following table.

Tap the image to zoom
Technical Requirements
Contoso identifies the following technical requirements:
- OLTP will be offloaded to Microsoft Azure virtual machines.
- The data for One Report must not be more than l5 minutes old.
- All of the databases for the OLTP system must be implemented on solid state drives (SSDs).
- A solution for the OLTP system must be created to provide disaster recovery and reporting between
SQL01 and SQL02.
- All databases, except for the research and marketing databases, must be recoverable to any point
during the last 30 days.
- A solution for the data warehouse system must be created to provide disaster recovery between SQL03
and an Azure virtual machine named SQL04.