You need to ensure that the login for the ticketingapplication cannot access other production databases

You administer a single server that contains a Microsoft SQL Server 2012 default instance on which several
production databases have been deployed.
You plan to install a new ticketing application that requires the deployment of a database on the server.
The SQL login for this application requires sysadmin permissions.
You need to ensure that the login for the ticketingapplication cannot access other production databases.
What should you do?

You administer a single server that contains a Microsoft SQL Server 2012 default instance on which several
production databases have been deployed.
You plan to install a new ticketing application that requires the deployment of a database on the server.
The SQL login for this application requires sysadmin permissions.
You need to ensure that the login for the ticketingapplication cannot access other production databases.
What should you do?

A.
Use the SQL Server default instance and enable Contained Databases.

B.
Use the SQL Server default instance and configurea user-defined server role. Add the login for the ticketing
application to this role.

C.
Install a new named SQL Server instance on the server.

D.
Install a new default SQL Server instance on the server.



Leave a Reply 6

Your email address will not be published. Required fields are marked *


Terence

Terence

It is because you can install only one default instance but can install multiple named instances.

Shujie

Shujie

Furthermore ‘sysadmin’ role members can perform all activities possible on the Database Engine instance. And this server role is fixed and it is not possible to modify the permissions assigned to the role. So it will give the ticketing application access to other databases on the instance.

Iheb

Iheb

Why answer B is uncorrect ??

Lewis

Lewis

becaseu:
The SQL login for this application requires sysadmin permissions