Migrating Microsoft SQL Server to AWS with SQL Server Reporting Services

Answer: C.

SQL Server Reporting Services is not available on Amazon RDS instances.

If this service and feature are required in the AWS cloud, the only viable option is to install the Microsoft SQL Server database on EC2 instances.

Therefore, option C is CORRECT, and all other options are incorrect.

Reference:

The correct answer for this scenario is A: Create a Microsoft SQL Server on Amazon RDS database instance. Create a new Option Group and configure the SQLSERVER_SSRS option. Associate the option group with the RDS database instance.

Explanation:

SQL Server Reporting Services (SSRS) is a feature in Microsoft SQL Server that allows users to create, deploy, and manage reports. In order to continue using this feature in AWS, we need to create a Microsoft SQL Server instance on Amazon RDS.

Amazon RDS is a managed database service that makes it easier to set up, operate, and scale a relational database in the cloud. With Amazon RDS, we can deploy a SQL Server instance in minutes without worrying about infrastructure provisioning, software installation, or patching.

Option groups are a way to customize an RDS database instance by specifying configuration options that control its behavior. In this case, we need to create a new option group and configure the SQLSERVER_SSRS option. This option enables SQL Server Reporting Services on the RDS instance.

Here are the steps to create an RDS instance with SSRS enabled:

1. Sign in to the AWS Management Console and navigate to the RDS dashboard.
2. Click the "Create database" button and select "Microsoft SQL Server" as the engine type.
3. Choose the edition, version, and instance class that meet your requirements.
4. In the "Additional configuration" section, create a new option group and select "SQLSERVER_SSRS" as the option.
5. Configure any other desired options and create the RDS instance.
6. After the instance is created, associate the option group with the RDS instance.

Option B is incorrect because parameter groups are used to configure database engine settings, not RDS options.

Option C is also a valid solution, but it requires more management overhead because we need to provision, configure, and maintain the EC2 instances ourselves. Additionally, we need to ensure high availability and scalability for the SQL Server instance, which can be challenging.

Option D is unrelated to the requirement of enabling SQL Server Reporting Services on the RDS instance. Amazon RDS Performance Insights is a feature that provides database performance metrics and recommendations. While it's a useful feature, it doesn't address the SSRS requirement.