Why is the compress NOT removing any state?

An administrator runs a nightly compares on a versioned geodatabase. In the morning the

administrator checks the compares _ log and sees it is successful, but the number of state did NOT decrease. All users are working on the DEFAULT version an tend to run geoproccessing tools overnight.

Why is the compress NOT removing any state?
A . The connected map sessions are locking state.
B . The connected map sessions are locking the compress_log
C . The administrator needs INSERT and DELETE permission on the compress_log
D . The administration needs INSERT, UPDATE and DELETE permission on the state table.

View Answer

Answer: C