Enthuware

Hi, I have a doubt...

Will Runtime Exception cause the database Rollback or not in this case. i.e. if we change the Seq of updates in Option 1 and 2 will that work? Please explain.

A runtime exception (assuming that it is not marked as ApplicationException), will cause a transaction to be marked for rollback.

Since the question does not mention the RuntimeException is an application exception or system exception, I would eliminate the first three options.

The last two options specify that there will be a system exception thrown if the database update fails.
That leads me to choose the last two options.

If the Active Directory update fails..

This mean that Active Directory could (theoretically) be in inconsistent state (partially updated) ?
If yes, is this indeed good solution?

No, why do you think so? The update may also fail because the server is down, data violates some business rule, security, or any such reason. That doesn't mean the data is inconsistent.

I am not saying it be definitely be the case, but there is a possibility.
For example, AD server went down during update.

Yes, there is always a possibility of inconsistent data no matter what you do. You can only minimize it but cannot eliminate it. Even two phase commit is not 100% correct. Such data is fixed manually based on business rules. So I am not sure what is your point.

Thank you for your reply. Everything is clear.