How should you design the timer job?

You are designing an application that will use a timer job that will run each night to send documents to a
SharePoint 2010 Records Center site for archiving. The security on the site requires higher privileges than those
normally associated with the application. The security requirements for this application specify that:
It must not require customized storage of the user credentials.
.The user token used for security access must expire within 24 hours unless specifically refreshed to prevent
extended or unintended use over time.
.The security mechanism must require a two-way trust to prevent unauthorized activity between domains.
.The application must use the SharePoint object model to accomplish this.
You need to design the application to support these security requirements.
How should you design the timer job?

You are designing an application that will use a timer job that will run each night to send documents to a
SharePoint 2010 Records Center site for archiving. The security on the site requires higher privileges than those
normally associated with the application. The security requirements for this application specify that:
It must not require customized storage of the user credentials.
.The user token used for security access must expire within 24 hours unless specifically refreshed to prevent
extended or unintended use over time.
.The security mechanism must require a two-way trust to prevent unauthorized activity between domains.
.The application must use the SharePoint object model to accomplish this.
You need to design the application to support these security requirements.
How should you design the timer job?

A.
To inherit the security role assignments

B.
To log on to the Records Center site with a service account stored in a database

C.
To run with elevated privileges

D.
To run with impersonation



Leave a Reply 0

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