How should you design the stored procedure so that callers that do not paver permissions on CommDB and SalesDB can run the dbo.ABC_addEntry stored procedure successfully?

You work as a database developer at ABC.com. ABC.com has a SQL Server 2012 database
infrastructure with several databases. You have permissions on two of these databases, namely,
CommDB and SalesDB.
You need to develop a stored procedure named dbo.ABC_addEntry in a database named
AssetsDB. The dbo.ABC_addEntry stored procedure will run stored procedures in CommDB and
SalesDB.
How should you design the stored procedure so that callers that do not paver permissions on
CommDB and SalesDB can run the dbo.ABC_addEntry stored procedure successfully?

A.
You should configure the stored procedure to call the xp_cmdshell extended stored procedure.

B.
You should configure the stored procedure to call the sp_configure system stored procedure.

C.
You should assign users permission to the stored procedure.

D.
You should include the EXECUTE AS CALLER clause when creating the stored procedure.

E.
You should include the EXECUTE AS OWNER clause when creating the stored procedure.

Explanation: