You administer a SQL Server 2008 Reporting Services (SSRS) environment. You restore the ReportServer and ReportServerTempDB databases to a new server. When you browse to the Report Manager Web page, you receive an error message. You are unable to view the folder structure and the reports.
You need to view the folder structure and the reports.
What should you do?

A.
Restore the symmetric key.

B.
Restore the msdb database.

C.
Restore the master database.

D.
Configure the IIS virtual directory.

Explanation:
Tip: "restore the ReportServer and ReportServerTempDB databases to a new server" = "symmetric key"

http://technet.microsoft.com/en-us/library/ms156016.aspx
Report Server Database
A report server is a stateless server that uses the SQL Server Database Engine to store metadata and object definitions. A Reporting Services installation uses two databases to separate persistent data storage from temporary storage requirements. The databases are created together and bound by name. By default, the database names are reportserver and reportservertempdb, respectively.
The databases can run on a local or remote Database Engine instance. Choosing a local instance is useful if you have sufficient system resources or want to conserve software licenses, but running the databases on a remote computer can improve performance.
The report server database is a SQL Server database that stores the following content:
– Items managed by a report server (reports and linked reports, shared data sources, report models, folders, resources) and all of the properties and security settings that are associated with those items.
– Subscription and schedule definitions.
– Report snapshots (which include query results) and report history.
– System properties and system-level security settings.
– Report execution log data.
– Symmetric keys and encrypted connection and credentials for report data sources.
Administering a Report Server Database
A Reporting Services deployment uses two SQL Server relational databases for internal storage. By default, the databases are named ReportServer and ReportServerTempdb. ReportServerTempdb is created with the primary report server database and is used to store temporary data, session information, and cached reports.
In Reporting Services, database administration tasks include backing up and restoring the report server databases and managing the encryption keys that are used to encrypt and decrypt sensitive data.
Moving the Report Server Databases to Another Computer
Both the reportserver and reportservertempdb databases must be moved or copied together. A Reporting Services installation requires both databases; the reportservertempdb database must be related by name to the primary reportserver database you are moving.
Moving a database does not effect scheduled operations that are currently defined for report server items.
– Schedules will be recreated the first time that you restart the Report Server service.
– SQL Server Agent jobs that are used to trigger a schedule will be recreated on the new database instance. You do not have to move the jobs to the new computer, but you might want to delete jobs on the computer that will no longer be used.
– Subscriptions, cached reports, and snapshots are preserved in the moved database. If a snapshot is not picking up refreshed data after the database is moved, clear the snapshot options in Report Manager, click Apply to save your changes, re-create the schedule, and click Apply again to save your changes.
– Temporary report and user session data that is stored in reportservertempdb are persisted when you move that database.
Use the following steps to move the databases:
1. Backup the encryption keys for the report server database you want to move. You can use the Reporting Services Configuration tool backup the keys.
2. Stop the Report Server service. You can use the Reporting Services Configuration tool to stop the service.
3. Start SQL Server Management Studio and open a connection to the SQL Server instance that hosts the report server databases.
4 Right-click the report server database, point to Tasks, and click Detach. Repeat this step for the report server temporary database.
5. Copy or move the .mdf and .ldf files to the Data folder of the SQL Server instance you want to use. Because you are moving two databases, make sure that you move or copy all four files.
6. In Management Studio, open a connection to the new SQL Server instance that will host the report server databases.
7. Right-click the Databases node, and then click Attach.
8. Click Add to select the report server database .mdf and .ldf files that you want to attach. Repeat this step for the report server temporary database.
9. After the databases are attached, verify that the RSExecRole is a database role in the report server database and temporary database. RSExecRole must have select, insert, update, delete, and reference permissions on the report server database tables, and execute permissions on the stored procedures. For more information, see How to: Create the RSExecRole.
10. Start the Reporting Services Configuration tool and open a connection to the report server.
11. On the Database page, select the new SQL Server instance, and then click Connect.
12. Select the report server database that you just moved, and then click Apply.
13. On the Encryption Keys page, click Restore. Specify the file that contains the backup copy of the keys and the password to unlock the file.
14. Restart the Report Server service.