Which code segment should you execute?
###BeginCaseStudy###
Case Study: 4
Scenario 4
Application Information
You are a database administrator for a manufacturing company.
You have an application that stores product data. The data will be converted to technical
diagrams for the manufacturing process.
The product details are stored in XML format. Each XML must contain only one product that
has a root element named Product. A schema named Production.ProductSchema has been
created for the products xml.
You develop a Microsoft .NET Framework assembly named ProcessProducts.dll that will be
used to convert the XML files to diagrams. The diagrams will be stored in the database as
images. ProcessProducts.dll contains one class named ProcessProduct that has a method
name of Convert(). ProcessProducts.dll was created by using a source code file named
ProcessProduct.es.
All of the files are located in C:\Products\.
The application has several performance and security issues.
You will create a new database named ProductsDB on a new server that has SQL Server
2012 installed. ProductsDB will support the application.
The following graphic shows the planned tables for ProductsDB:
You will also add a sequence named Production.ProductID_Seq.
You plan to create two certificates named DBCert and ProductsCert. You will create
ProductsCert in master. You will create DBCert in ProductsDB.
You have an application that executes dynamic T-SQL statements against ProductsDB. A
sample of the queries generated by the application appears in Dynamic.sql.
Application Requirements
The planned database has the following requirements:
• All stored procedures must be signed.
• The amount of disk space must be minimized.
• Administrative effort must be minimized at all times.
• The original product details must be stored in the database.
• An XML schema must be used to validate the product details.
• The assembly must be accessible by using T-SQL commands.
• A table-valued function will be created to search products by type.
• Backups must be protected by using the highest level of encryption.
• Dynamic T-SQL statements must be converted to stored procedures.
• Indexes must be optimized periodically based on their fragmentation.
• Manufacturing steps stored in the ManufacturingSteps table must refer to a product by
the sameidentifier used by the Products table.
ProductDetails_Insert.sql
Product, xml
All product types are 11 digits. The first five digits of the product id reference the category of
the product and the remaining six digits are the subcategory of the product.
The following is a sample customer invoice in XML format:
ProductsByProductType.sql
Dynamic.sql
Category FromType.sql
IndexManagement.sql
###EndCaseStudy###
You need to modify Production.ProductDetails_Insert to comply with the application
requirements.
Which code segment should you execute?
Which development approach and mode should you use?
###BeginCaseStudy###
Case Study: 2
Contoso
Ltd Case A
General Background
You are the SQL Server Administrator for Contoso, Ltd. You have been tasked with
upgrading all existing SQL Server instances to SQL Server 2012.
Technical Background
The corporate environment includes an Active Directory Domain Services (AD DS) domain
named contoso.com. The forest and domain levels are set to Windows Server 2008. All
default containers are used for computer and user accounts. All servers run Windows Server
2008 R2 Service Pack 1 (SP1). All client computers run Windows 7 Professional SP1. All
servers and client computers are members of the contoso.com domain.
The current SQL Server environment consists of a single instance failover cluster of SQL
Server 2008 R2 Analysis Services (SSAS). The virtual server name of the cluster is
SSASCluster. The cluster includes two nodes: Node1 and Node2. Node1 is currently the
active node. In anticipation of the upgrade, the prerequisites and shared components have
been upgraded on both nodes of the cluster, and each node was rebooted during a weekly
maintenance window.
A single-server deployment of SQL Server 2008 R2 Reporting Services (SSRS) in native
mode is installed on a server named SSRS01. The Reporting Server service is configured to
use a domain service account. SSRS01 hosts reports that access the SSAS databases for sales
data as well as modeling data for the Research team. SSRS01 contains 94 reports used by the
organization. These reports are generated continually during business hours. Users report that
report subscriptions on SSRS01 are not being delivered. You run the reports on demand from
Report Manager and find that the reports render as expected.
A new server named SSRS02 has been joined to the domain, SSRS02 will host a singleserver deployment of SSRS so that snapshots of critical reports are accessible during the upgrade.
The server configuration is shown in the exhibit. (Click the Exhibit button.)
The production system includes three SSAS databases that are described in the following table.
All SSAS databases are backed up once a day, and backups are stored offsite.
Business Requirements
After the upgrade users must be able to perform the following tasks:
• Ad-hoc analysis of data in the SSAS databases by using the Microsoft
Excel PivotTable client.
• Daily operational analysis by executing a custom application that uses
ADOMD.NET and existing Multidimensional Expressions (MDX) queries.
The detailed data must be stored in the model.
Technical Requirements
You need to minimize downtime during the SSASCluster upgrade. The upgrade must
minimize user intervention and administrative effort.
The upgrade to SQL Server 2012 must maximize the use of all existing servers, require the
least amount of administrative effort, and ensure that the SSAS databases are operational as
soon as possible.
You must implement the highest level of domain security for client computers connecting to
SSRS01. The SSRS instance on SSRS01 must use Kerberos delegation to connect to the
SSAS databases. Email notification for SSRS01 has not been previously configured. Email
notification must be configured to use the SMTP server SMTP01 with a From address of
reports@contoso.com. Report distribution must be secured by using SSL and must be limited
to the contoso.com domain.
You have the following requirements for SSRS02:
• Replicate the SSRS01 configuration.
• Ensure that all current reports are available on SSRS02.
• Minimize the performance impact on SSR501.
In preparation for the upgrade, the SSRS-related components have been installed on the new
SSRS02 server by using the Reporting Services file-only installation mode. The Reporting
Services databases have been restored from SSRS01 and configured appropriately.
You must design a strategy to recover the SSRS instance on SSRS01 in the event of a system
failure. The strategy must ensure that SSRS can be recovered in the minimal amount of time
and that reports are available as soon as possible. Only functional components must be
recovered.
SSRS02 is the recovery server and is running the same version of SSRS as SSRS01. A full
backup of the SSRS databases on SSRS01 is performed nightly. The report server
configuration files, custom assemblies, and extensions on SSRS02 are manually synchronized
with SSRS01.
Prior to implementing the upgrade to SQL Server 2012, you must back up all existing SSAS
databases.
Databases on SSRS01 is performed nightly. The report server configuration files, custom
assemblies, and extensions on SSRS02 are manually synchronized with SSRS01.
Prior to implementing the upgrade to SQL Server 2012, you must back up all existing SSAS
databases. The backup must include only the partitioning, metadata, and aggregations to
minimize the processing time required when restoring the databases. You must minimize
processing time and the amount of disk space used by the backups.
Before upgrading SSAS on the SSASCluster, all existing databases must be moved to a
temporary staging server named SSAS01 that hosts a default instance of SQL Server 2012
Analysis Services. This server will be used for testing client applications connecting to SSAS
2012, and as a disaster recovery platform during the upgrade. You must move the databases
by using the least amount of administrative effort and minimize downtime.
All SSAS databases other than the Research database must be converted to tabular BI
Semantic Models (BISMs) as part of the upgrade to SSAS 2012. The Research team must
have access to the Research database for modeling throughout the upgrade. To facilitate this,
you detach the Research database and attach it to SSAS01.
While testing the Research database on SSAS01, you increase the compatibility level to
1100. You then discover a compatibility issue with the application. You must roll back the
compatibility level of the database to 1050 and retest.
After completing the upgrade, you must do the following:
1. Design a role and assign an MDX expression to the Allowed member set property of the
Customer dimension to allow sales representatives to browse only members of the Customer
dimension that are located in their sales regions. Use the sales representatives’ logins and
minimize impact on performance.
2. Deploy a data model to allow the ad-hoc analysis of data. The data model must be cached
and source data from an OData feed.
###EndCaseStudy###
You need to develop a BISM that meets the business requirements for ad-hoc and daily
operational analysis. You must minimize development effort.
Which development approach and mode should you use?
You need to ensure that the dimension processes successfully
A production SQL Server Analysis Services (SSAS) cube is processed daily. The users
query products by using a hierarchy named Products from a dimension named Product.
The DimProduct table in the data source view is used as the source of the Product
dimension. The table has the following structure.
The Product dimension has three attribute hierarchies:
Product
Subcategory
Category
The attributes have the following relationships defined: Product > Subcategory > Category.
Each attribute has a key and a name sourced from the related key and name columns in the
DimProduct table.
During processing, you receive the following error message: ‘Errors in the OLAP storage
engine: A duplicate attribute key has been found when processing: Table: ‘dbo_DimProduct’,
Column: ‘SubCategoryKey1, Value: “23′. The attribute is Subcategory’.”
You verify that the data is accurate.
You need to ensure that the dimension processes successfully.
What should you do?
Which three actions should you perform in sequence?
DRAG DROP
You have a single SQL Server 2008 R2 Analysis Services (SSAS) instance. You are
planning to upgrade the instance to SQL Server 2014.
You need to import an existing PowerPivot workbook to create a tabular project.
Which three actions should you perform in sequence? (To answer, move the appropriate
actions from the list of actions to the answer area and arrange them in the correct order.)
Which code segment should you use to complete the function?
###BeginCaseStudy###
Case Study: 4
Scenario 4
Application Information
You are a database administrator for a manufacturing company.
You have an application that stores product data. The data will be converted to technical
diagrams for the manufacturing process.
The product details are stored in XML format. Each XML must contain only one product that
has a root element named Product. A schema named Production.ProductSchema has been
created for the products xml.
You develop a Microsoft .NET Framework assembly named ProcessProducts.dll that will be
used to convert the XML files to diagrams. The diagrams will be stored in the database as
images. ProcessProducts.dll contains one class named ProcessProduct that has a method
name of Convert(). ProcessProducts.dll was created by using a source code file named
ProcessProduct.es.
All of the files are located in C:\Products\.
The application has several performance and security issues.
You will create a new database named ProductsDB on a new server that has SQL Server
2012 installed. ProductsDB will support the application.
The following graphic shows the planned tables for ProductsDB:
You will also add a sequence named Production.ProductID_Seq.
You plan to create two certificates named DBCert and ProductsCert. You will create
ProductsCert in master. You will create DBCert in ProductsDB.
You have an application that executes dynamic T-SQL statements against ProductsDB. A
sample of the queries generated by the application appears in Dynamic.sql.
Application Requirements
The planned database has the following requirements:
• All stored procedures must be signed.
• The amount of disk space must be minimized.
• Administrative effort must be minimized at all times.
• The original product details must be stored in the database.
• An XML schema must be used to validate the product details.
• The assembly must be accessible by using T-SQL commands.
• A table-valued function will be created to search products by type.
• Backups must be protected by using the highest level of encryption.
• Dynamic T-SQL statements must be converted to stored procedures.
• Indexes must be optimized periodically based on their fragmentation.
• Manufacturing steps stored in the ManufacturingSteps table must refer to a product by
the sameidentifier used by the Products table.
ProductDetails_Insert.sql
Product, xml
All product types are 11 digits. The first five digits of the product id reference the category of
the product and the remaining six digits are the subcategory of the product.
The following is a sample customer invoice in XML format:
ProductsByProductType.sql
Dynamic.sql
Category FromType.sql
IndexManagement.sql
###EndCaseStudy###
You need to create a function that will use a SELECT statement in
ProductsByProductType.sql.
Which code segment should you use to complete the function?
You need to use SQL Server Management Studio (SSMS) to make the SSAS databases available for application testi
###BeginCaseStudy###
Case Study: 2
Contoso
Ltd Case A
General Background
You are the SQL Server Administrator for Contoso, Ltd. You have been tasked with
upgrading all existing SQL Server instances to SQL Server 2012.
Technical Background
The corporate environment includes an Active Directory Domain Services (AD DS) domain
named contoso.com. The forest and domain levels are set to Windows Server 2008. All
default containers are used for computer and user accounts. All servers run Windows Server
2008 R2 Service Pack 1 (SP1). All client computers run Windows 7 Professional SP1. All
servers and client computers are members of the contoso.com domain.
The current SQL Server environment consists of a single instance failover cluster of SQL
Server 2008 R2 Analysis Services (SSAS). The virtual server name of the cluster is
SSASCluster. The cluster includes two nodes: Node1 and Node2. Node1 is currently the
active node. In anticipation of the upgrade, the prerequisites and shared components have
been upgraded on both nodes of the cluster, and each node was rebooted during a weekly
maintenance window.
A single-server deployment of SQL Server 2008 R2 Reporting Services (SSRS) in native
mode is installed on a server named SSRS01. The Reporting Server service is configured to
use a domain service account. SSRS01 hosts reports that access the SSAS databases for sales
data as well as modeling data for the Research team. SSRS01 contains 94 reports used by the
organization. These reports are generated continually during business hours. Users report that
report subscriptions on SSRS01 are not being delivered. You run the reports on demand from
Report Manager and find that the reports render as expected.
A new server named SSRS02 has been joined to the domain, SSRS02 will host a singleserver deployment of SSRS so that snapshots of critical reports are accessible during the upgrade.
The server configuration is shown in the exhibit. (Click the Exhibit button.)
The production system includes three SSAS databases that are described in the following table.
All SSAS databases are backed up once a day, and backups are stored offsite.
Business Requirements
After the upgrade users must be able to perform the following tasks:
• Ad-hoc analysis of data in the SSAS databases by using the Microsoft
Excel PivotTable client.
• Daily operational analysis by executing a custom application that uses
ADOMD.NET and existing Multidimensional Expressions (MDX) queries.
The detailed data must be stored in the model.
Technical Requirements
You need to minimize downtime during the SSASCluster upgrade. The upgrade must
minimize user intervention and administrative effort.
The upgrade to SQL Server 2012 must maximize the use of all existing servers, require the
least amount of administrative effort, and ensure that the SSAS databases are operational as
soon as possible.
You must implement the highest level of domain security for client computers connecting to
SSRS01. The SSRS instance on SSRS01 must use Kerberos delegation to connect to the
SSAS databases. Email notification for SSRS01 has not been previously configured. Email
notification must be configured to use the SMTP server SMTP01 with a From address of
reports@contoso.com. Report distribution must be secured by using SSL and must be limited
to the contoso.com domain.
You have the following requirements for SSRS02:
• Replicate the SSRS01 configuration.
• Ensure that all current reports are available on SSRS02.
• Minimize the performance impact on SSR501.
In preparation for the upgrade, the SSRS-related components have been installed on the new
SSRS02 server by using the Reporting Services file-only installation mode. The Reporting
Services databases have been restored from SSRS01 and configured appropriately.
You must design a strategy to recover the SSRS instance on SSRS01 in the event of a system
failure. The strategy must ensure that SSRS can be recovered in the minimal amount of time
and that reports are available as soon as possible. Only functional components must be
recovered.
SSRS02 is the recovery server and is running the same version of SSRS as SSRS01. A full
backup of the SSRS databases on SSRS01 is performed nightly. The report server
configuration files, custom assemblies, and extensions on SSRS02 are manually synchronized
with SSRS01.
Prior to implementing the upgrade to SQL Server 2012, you must back up all existing SSAS
databases.
Databases on SSRS01 is performed nightly. The report server configuration files, custom
assemblies, and extensions on SSRS02 are manually synchronized with SSRS01.
Prior to implementing the upgrade to SQL Server 2012, you must back up all existing SSAS
databases. The backup must include only the partitioning, metadata, and aggregations to
minimize the processing time required when restoring the databases. You must minimize
processing time and the amount of disk space used by the backups.
Before upgrading SSAS on the SSASCluster, all existing databases must be moved to a
temporary staging server named SSAS01 that hosts a default instance of SQL Server 2012
Analysis Services. This server will be used for testing client applications connecting to SSAS
2012, and as a disaster recovery platform during the upgrade. You must move the databases
by using the least amount of administrative effort and minimize downtime.
All SSAS databases other than the Research database must be converted to tabular BI
Semantic Models (BISMs) as part of the upgrade to SSAS 2012. The Research team must
have access to the Research database for modeling throughout the upgrade. To facilitate this,
you detach the Research database and attach it to SSAS01.
While testing the Research database on SSAS01, you increase the compatibility level to
1100. You then discover a compatibility issue with the application. You must roll back the
compatibility level of the database to 1050 and retest.
After completing the upgrade, you must do the following:
1. Design a role and assign an MDX expression to the Allowed member set property of the
Customer dimension to allow sales representatives to browse only members of the Customer
dimension that are located in their sales regions. Use the sales representatives’ logins and
minimize impact on performance.
2. Deploy a data model to allow the ad-hoc analysis of data. The data model must be cached
and source data from an OData feed.
###EndCaseStudy###
You need to use SQL Server Management Studio (SSMS) to make the SSAS databases
available for application testing.
What should you do?
What is the best deployment option to use?
You have a SQL Server Analysis Services (SSAS) database named DB1 on a server named
Server1.
You need to deploy DB1 from Server1 to four other servers. If the destination server already
contains a copy of DB1, the database must be updated only. If the destination server does
not contain a copy of DB1, the database must be copied to the destination server.
What is the best deployment option to use? More than one answer choice may achieve the
goal. Select the BEST answer.
Which code segment should you use?
###BeginCaseStudy###
Case Study: 4
Scenario 4
Application Information
You are a database administrator for a manufacturing company.
You have an application that stores product data. The data will be converted to technical
diagrams for the manufacturing process.
The product details are stored in XML format. Each XML must contain only one product that
has a root element named Product. A schema named Production.ProductSchema has been
created for the products xml.
You develop a Microsoft .NET Framework assembly named ProcessProducts.dll that will be
used to convert the XML files to diagrams. The diagrams will be stored in the database as
images. ProcessProducts.dll contains one class named ProcessProduct that has a method
name of Convert(). ProcessProducts.dll was created by using a source code file named
ProcessProduct.es.
All of the files are located in C:\Products\.
The application has several performance and security issues.
You will create a new database named ProductsDB on a new server that has SQL Server
2012 installed. ProductsDB will support the application.
The following graphic shows the planned tables for ProductsDB:
You will also add a sequence named Production.ProductID_Seq.
You plan to create two certificates named DBCert and ProductsCert. You will create
ProductsCert in master. You will create DBCert in ProductsDB.
You have an application that executes dynamic T-SQL statements against ProductsDB. A
sample of the queries generated by the application appears in Dynamic.sql.
Application Requirements
The planned database has the following requirements:
• All stored procedures must be signed.
• The amount of disk space must be minimized.
• Administrative effort must be minimized at all times.
• The original product details must be stored in the database.
• An XML schema must be used to validate the product details.
• The assembly must be accessible by using T-SQL commands.
• A table-valued function will be created to search products by type.
• Backups must be protected by using the highest level of encryption.
• Dynamic T-SQL statements must be converted to stored procedures.
• Indexes must be optimized periodically based on their fragmentation.
• Manufacturing steps stored in the ManufacturingSteps table must refer to a product by
the sameidentifier used by the Products table.
ProductDetails_Insert.sql
Product, xml
All product types are 11 digits. The first five digits of the product id reference the category of
the product and the remaining six digits are the subcategory of the product.
The following is a sample customer invoice in XML format:
ProductsByProductType.sql
Dynamic.sql
Category FromType.sql
IndexManagement.sql
###EndCaseStudy###
An administrator provides a digital certificate named ServerCert.
You need to implement Transparent Data Encryption (TDE) on ProductsDB.
Which code segment should you use?
Which configuration settings should you use?
###BeginCaseStudy###
Case Study: 2
Contoso
Ltd Case A
General Background
You are the SQL Server Administrator for Contoso, Ltd. You have been tasked with
upgrading all existing SQL Server instances to SQL Server 2012.
Technical Background
The corporate environment includes an Active Directory Domain Services (AD DS) domain
named contoso.com. The forest and domain levels are set to Windows Server 2008. All
default containers are used for computer and user accounts. All servers run Windows Server
2008 R2 Service Pack 1 (SP1). All client computers run Windows 7 Professional SP1. All
servers and client computers are members of the contoso.com domain.
The current SQL Server environment consists of a single instance failover cluster of SQL
Server 2008 R2 Analysis Services (SSAS). The virtual server name of the cluster is
SSASCluster. The cluster includes two nodes: Node1 and Node2. Node1 is currently the
active node. In anticipation of the upgrade, the prerequisites and shared components have
been upgraded on both nodes of the cluster, and each node was rebooted during a weekly
maintenance window.
A single-server deployment of SQL Server 2008 R2 Reporting Services (SSRS) in native
mode is installed on a server named SSRS01. The Reporting Server service is configured to
use a domain service account. SSRS01 hosts reports that access the SSAS databases for sales
data as well as modeling data for the Research team. SSRS01 contains 94 reports used by the
organization. These reports are generated continually during business hours. Users report that
report subscriptions on SSRS01 are not being delivered. You run the reports on demand from
Report Manager and find that the reports render as expected.
A new server named SSRS02 has been joined to the domain, SSRS02 will host a singleserver deployment of SSRS so that snapshots of critical reports are accessible during the upgrade.
The server configuration is shown in the exhibit. (Click the Exhibit button.)
The production system includes three SSAS databases that are described in the following table.
All SSAS databases are backed up once a day, and backups are stored offsite.
Business Requirements
After the upgrade users must be able to perform the following tasks:
• Ad-hoc analysis of data in the SSAS databases by using the Microsoft
Excel PivotTable client.
• Daily operational analysis by executing a custom application that uses
ADOMD.NET and existing Multidimensional Expressions (MDX) queries.
The detailed data must be stored in the model.
Technical Requirements
You need to minimize downtime during the SSASCluster upgrade. The upgrade must
minimize user intervention and administrative effort.
The upgrade to SQL Server 2012 must maximize the use of all existing servers, require the
least amount of administrative effort, and ensure that the SSAS databases are operational as
soon as possible.
You must implement the highest level of domain security for client computers connecting to
SSRS01. The SSRS instance on SSRS01 must use Kerberos delegation to connect to the
SSAS databases. Email notification for SSRS01 has not been previously configured. Email
notification must be configured to use the SMTP server SMTP01 with a From address of
reports@contoso.com. Report distribution must be secured by using SSL and must be limited
to the contoso.com domain.
You have the following requirements for SSRS02:
• Replicate the SSRS01 configuration.
• Ensure that all current reports are available on SSRS02.
• Minimize the performance impact on SSR501.
In preparation for the upgrade, the SSRS-related components have been installed on the new
SSRS02 server by using the Reporting Services file-only installation mode. The Reporting
Services databases have been restored from SSRS01 and configured appropriately.
You must design a strategy to recover the SSRS instance on SSRS01 in the event of a system
failure. The strategy must ensure that SSRS can be recovered in the minimal amount of time
and that reports are available as soon as possible. Only functional components must be
recovered.
SSRS02 is the recovery server and is running the same version of SSRS as SSRS01. A full
backup of the SSRS databases on SSRS01 is performed nightly. The report server
configuration files, custom assemblies, and extensions on SSRS02 are manually synchronized
with SSRS01.
Prior to implementing the upgrade to SQL Server 2012, you must back up all existing SSAS
databases.
Databases on SSRS01 is performed nightly. The report server configuration files, custom
assemblies, and extensions on SSRS02 are manually synchronized with SSRS01.
Prior to implementing the upgrade to SQL Server 2012, you must back up all existing SSAS
databases. The backup must include only the partitioning, metadata, and aggregations to
minimize the processing time required when restoring the databases. You must minimize
processing time and the amount of disk space used by the backups.
Before upgrading SSAS on the SSASCluster, all existing databases must be moved to a
temporary staging server named SSAS01 that hosts a default instance of SQL Server 2012
Analysis Services. This server will be used for testing client applications connecting to SSAS
2012, and as a disaster recovery platform during the upgrade. You must move the databases
by using the least amount of administrative effort and minimize downtime.
All SSAS databases other than the Research database must be converted to tabular BI
Semantic Models (BISMs) as part of the upgrade to SSAS 2012. The Research team must
have access to the Research database for modeling throughout the upgrade. To facilitate this,
you detach the Research database and attach it to SSAS01.
While testing the Research database on SSAS01, you increase the compatibility level to
1100. You then discover a compatibility issue with the application. You must roll back the
compatibility level of the database to 1050 and retest.
After completing the upgrade, you must do the following:
1. Design a role and assign an MDX expression to the Allowed member set property of the
Customer dimension to allow sales representatives to browse only members of the Customer
dimension that are located in their sales regions. Use the sales representatives’ logins and
minimize impact on performance.
2. Deploy a data model to allow the ad-hoc analysis of data. The data model must be cached
and source data from an OData feed.
###EndCaseStudy###
You need to configure SSRS to send the required notification messages.
Which configuration settings should you use? (Each correct answer presents a partial
solution. Choose all that apply.)
Which deployment method should you use?
You are deploying an update to a SQL Server Analysis Services (SSAS) cube to a
production environment.
The production database has been configured with security roles.
You need to preserve the existing security roles in the production database. Database roles
and their user accounts from the development environment must not be deployed to the
production server.
Which deployment method should you use?