You are designing a SharePoint 2010 farm in your organization. You need to design the library to meet the
following requirements:
The budget approval office needs a custom document library, which will send an e-mail as soon as each budget
document is updated by a user.
.The SharePoint farm administrator wants to block the addition of any document that is larger than 100 MB and
send out a message to users informing them of the failure. Which approach should you recommend?
A.
Design the following event receivers:
.An asynchronous event receiver to send an e-mail after the document is updated
.A synchronous event receiver to display a warning message when a file is added that is larger than 100 MB
B.
Design the following event receivers:
.A synchronous event receiver to send an e-mail after the document is updated
.An asynchronous event receiver to display a warning message when a file is added that is larger than 100 MB
C.
Design a timer job to send the following:
.A batch of �budget document updated� e-mails at the end of each day
.A synchronous event receiver to display a warning message when a file is added that is larger than 100 MB
D.
Design a service application to send the following:
.A batch of �budget document updated� e-mails at the end of each day
.A synchronous event receiver to display a warning message when a file is added that is larger than 100 MB
“send an e-mail as soon as each budget document is updated” in asynchronous in order to let the upload continues without blocking it.
The event-receiver “OnAdding” in synchronous to block the upload if the file > 100MB.
http://msdn.microsoft.com/en-us/library/gg749858(v=office.14).aspx
Synchronous event receivers are called in sequential order based on the sequence number specified during event binding. This applies to both Before and After synchronous events.
Asynchronous After event receiver threads are initiated in sequential order based on the sequence number. However, there is no guarantee that they will finish in that same order.
An asynchronous After event can start at any time after its associated user action is performed. It may start before, at the same time as, or after the Web request is completed.