In the configuration file, the delivery method is set through the SendUsing configuration setting.

SendUsing specifies a method for sending messages. You can choose between a network SMTP service or a local SMTP service pickup directory. To use a remote SMTP service, this value must be set to 2 in the RSReportServer.config file.

SMTPServer specifies the remote SMTP server or forwarder. This value is a required value if you are using a remote SMTP server or forwarder.

G:

From scenario: Report distribution must be secured by using SSL and must be limited to the contoso.com domain.

Note:

Configuration Options for Remote SMTP Service

The connection between the report server and an SMTP server or forwarder is determined by the following configuration settings:

SendUsing specifies a method for sending messages. You can choose between a network SMTP service or a local SMTP service pickup directory. To use a remote SMTP service, this value must be set to 2 in the RSReportServer.config file.

SMTPServer specifies the remote SMTP server or forwarder. This value is a required value if you are using a remote SMTP server or forwarder.

From sets the value that appears in the From: line of an e-mail message. This value is a required value if you are using a remote SMTP server or forwarder.

Other values that are used for remote SMTP service include the following (note that you do not need to specify these values unless you want to override the default values).

SMTPServerPort is configured for port 25.

SMTPAuthenticate specifies how the report server connects to the remote SMTP server.

Question No: 42 – (Topic 4)

Use the SQL Server Configuration Manager to reset the SQL Service account credentials.

Answer: A

Question No: 43 – (Topic 4)

You need to use Reporting Services Configuration Manager to configure SSRS to complete the installation on SSRS02.

What should you do? (Each correct answer presents a partial solution. Choose all that apply.)

Change the encryption key.

Specify the execution account.

Join the scale-out deployment.

Set the Report Server Web Service URL.

Set the Report Manager URL.

Delete the encryption key.

Answer: A,B,E

Explanation: A: We need to restore a copy of the encryption key from SSRS01. This step is necessary for enabling reversible encryption on pre-existing connection strings and credentials that are already in the report server database.

B: Reporting Services provides a special account that is used for unattended report processing and for sending connection requests across the network. The account is used in the following ways:

/ Send connection requests over the network for reports that use database authentication, or connect to external report data sources that do not require or use authentication.

/ Retrieve external image files that are used in report. If you want to use an image file and the file cannot be accessed through Anonymous access, you can configure the unattended report processing account and grant the account permission to access the file.

E: Example:

First of all open Internet Explorer and go to Report Manager URL which is something like below:

Click on your SSRS project. So now it will show you the list of reports which are deployed on your report server.

Now click on down arrow on the report which you want to subscribe and selectManage. Etc.

From Scenario:

/ A new server named SSRS02 has been joined to the domain, SSRS02 will host a single- server deployment of SSRS so that snapshots of critical reports are accessible during the upgrade.

/ 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 SSRS01.

/ 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.

/ SSRS02 is the recovery server and is running the same version of SSRS as SSRS01. The report server configuration files, custom assemblies, and extensions on SSRS02 are manually synchronized with SSRS01.

Question No: 44 – (Topic 4)

You need to implement the Customer Sales and Manufacturing data models.

What should you do? (Each correct answer presents a partial solution. Choose all that apply.)

Use the Database Synchronization Wizard to upgrade the database to tabular mode.

Use SQL Server Integration Services (SSIS) to copy the database design to the SSAS instance, and specify tabular mode as the destination.

Use SQL Server Data Tools (SSDT) to redevelop and deploy the projects.

Use the current SSAS instance.

Install a new instance of SSAS in tabular mode.

Answer: C,E Explanation:

C: Tabular models are authored in SQL Server Data Tools (SSDT) using new tabular model project templates. You can import data from multiple sources, and then enrich the model by adding relationships, calculated columns, measures, KPIs, and hierarchies.

Models can then be deployed to an instance of Analysis Services where client reporting applications can connect to them. Deployed models can be managed in SQL Server Management Studio just like multidimensional models. They can also be partitioned for optimized processing and secured to the row-level by using role based security.

E: If you are installing Analysis Services to use the new tabular modeling features, you must install Analysis Services in a server mode that supports that type of model. The server mode is Tabular, and it is configured during installation.

After you install the server in this mode, you can use it host solutions that you build in tabular model designer. A tabular mode server is required if you want tabular model data access over the network.

From scenario:

/ 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.

/ 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.

The Business Intelligence Semantic Model (BISM) is a single unified BI platform which has both multi-dimensional as well as tabular data modeling capabilities to offer best of both worlds and choice for the developer.

Question No: 45 – (Topic 4)

You need to use SQL Server Management Studio (SSMS) to make the SSAS databases available for application testing.

What should you do?

Restore the SSAS databases from the latest backup to SSAS01.

Script the databases as a Create script to a new window and then execute the script on SSAS01.

Detach the SSAS databases from the SSASCluster, and then attach them to SSAS01.

Use the Import/Export Wizard to copy the databases from the production server to the development server.

Answer: A

Question No: 46 – (Topic 4)

You need to design the recovery strategy for SSRS01.

What should the strategy include? (Each correct answer presents part of the solution. Choose all that apply.)

Re-create the SQL Server Agent jobs that are used to trigger schedules.

Restore the ReportServer and ReportServerTempDB databases with recovery.

Restore the ReportServer and ReportServerTempDB databases with no recovery.

Restore the msdb database.

Restore the Report Server encryption key.

Restore the database encryption key.

Answer: A,B,E

Question No: 47 DRAG DROP – (Topic 4)

You need to upgrade the SSASCluster.

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.)

Answer:

Explanation:

Box 1:

Box 2:

Box 3:

Note:

From scenario:

/ 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.

The upgrade must minimize user intervention and administrative effort. So we’ll upgrade using the scripted method rather than the GUI method.

(box 1)

/ SQL Server Setup provides the ability to generate a configuration file based upon the system default and run-time inputs. You can use the configuration file to deploy SQL Server throughout the enterprise with the same configuration. You can also standardize manual installations throughout the enterprise, by creating a batch file that launches Setup.exe.

/ How to generate a configuration file

Insert the SQL Server installation media. From the root folder, double-click Setup.exe. To install from a network share, locate the root folder on the share, and then double-click

Setup.exe.

Follow the wizard through to the Ready to Install page. The path to the configuration file is specified in the Ready to Install page in the configuration file path section. For more information about how to install SQL Server, see Install SQL Server 2012 from the Installation Wizard (Setup).

Cancel the setup without actually completing the installation, to generate the INI file.

(box 2) First upgrade the passive node node2.

To be able to use the configuration file we use the command prompt. After the upgrade, the cluster will fail over to the upgraded node.

*( Box 3) upgrade Node1 (which is now the passive node)

You can upgrade a SQL Server failover cluster to a SQL Server 2008 failover cluster by using the SQL Server Installation Wizard or a command prompt. One of the main features of SQL Server 2008 failover clustering is minimal downtime for rolling upgrades and updates.

To control the failover behavior of cluster nodes during the upgrade process, run the upgrade operation at the command prompt and use the

/FAILOVERCLUSTERROLLOWNERSHIP parameter.

To upgrade a SQL Server failover cluster to SQL Server 2008 R2, you must run the Setup on one failover cluster node at a time, starting with the passive nodes. Setup determines when to fail over to the upgraded node, depending on the total number of nodes in the failover cluster instance, and the number of nodes that have already been upgraded. When half of the nodes or more have already been upgraded, Setup by default will cause a failover to an upgraded node.

To control the failover behavior of cluster nodes during the upgrade process, run the upgrade operation at the command prompt and use the

/FAILOVERCLUSTERROLLOWNERSHIP parameter to control the failover behavior before the upgrade operation takes the node offline. Use of this parameter is as follows:

/FAILOVERCLUSTERROLLOWNERSHIP=0 will not roll cluster ownership (move group) to upgraded nodes, and does not add this node to the list of possible owners of the SQL Server cluster at the end of upgrade.

/FAILOVERCLUSTERROLLOWNERSHIP=1 will roll cluster ownership (move group) to upgraded nodes, and will add this node to the list of possible owners of the SQL Server cluster at the end of upgrade.

/FAILOVERCLUSTERROLLOWNERSHIP=2 is the default setting. It will be used if this parameter is not specified. This setting indicates that SQL Server Setup will manage cluster ownership (move group) as needed.

Topic 5, Data Architect General Background

You are a Data Architect for a company that uses SQL Server 2012 Enterprise edition.

You have been tasked with designing a data warehouse that uses the company#39;s financial database as the data source. From the data warehouse, you will develop a cube to simplify the creation of accurate financial reports and related data analysis.

Background

You will utilize the following three servers:

->ServerA runs SQL Server Database Engine. ServerA is a production server and also hosts the financial database.

->The financial database is used by a third-party application and the table structures cannot be modified.

The relevant tables in the financial database are shown in the exhibit. (Click the Exhibit button.)

The SalesTransactions table is 500 GB and is anticipated to grow to 2 TB. The table is

partitioned by month. It contains only the last five years of financial data. The CouponUsed, OnSale, and Closeout columns contain only the values Yes or No. Each of the other tables is less than 10 MB and has only one partition.

The SecurityFilter table specifies the sites to which each user has access.

Business Requirements

The extract, transform, load (ETL) process that updates the data warehouse must run daily between 8:00 P.M. and 5:00 A.M. so that it doesn#39;t impact the performance of ServerA during business hours. The cube data must be available by 8:00 A.M.

The cube must meet the following business requirements:

->Ensure that reports display the most current information available.

->Allow fast access to support ad-hoc reports and data analysis.

Business Analysts will access the data warehouse tables directly, and will access the cube by using SSRS, Microsoft Excel, and Microsoft SharePoint Server 2010 PerformancePoint Services. These tools will access only the cube and not the data warehouse.

Technical Requirements

SSIS solutions must be deployed by using the project deployment model.

You must develop the data warehouse and store the cube on ServerB. When the number of concurrent SSAS users on ServerB reaches a specific number, you must scale out SSAS to ServerC and meet following requirements:

->Maintain copies of the cube on ServerB and ServerC.

->Ensure that the cube is always available on both servers.

->Minimize query response time.

The cube must meet the following technical requirements:

->The cube must be processed by using an SSIS package.

->The cube must contain the prior day#39;s data up to 8:00 P.M. but does not need to contain same-day data.

->The cube must include aggregation designs when it is initially deployed.

->A product dimension must be added to the cube. It will contain a hierarchy comprised of product name and product color.

Because of the large size of the SalesTransactions table, the cube must store only aggregations-the data warehouse must store the detailed data. Both the data warehouse and the cube must minimize disk space usage.

As the cube size increases, you must plan to scale out to additional servers to minimize processing time.

The data warehouse must use a star schema design. The table design must be as denormalized as possible. The history of changes to the Customer table must be tracked in the data warehouse. The cube must use the data warehouse as its only data source.

Security settings on the data warehouse and the cube must ensure that queries against the SalesTransactions table return only records from the sites to which the current user has

access.

The ETL process must consist of multiple SSIS packages developed in a single project by using the least amount of effort. The SSIS packages must use a database connection string that is set at execution time to connect to the financial database. All data in the data warehouse must be loaded by the SSIS packages.

You must create a Package Activity report that meets the following requirements: