Until the current transaction is processed, no other ____________ can be submitted.

• A. Access Requests
• B. Invoices
• C. Change Requests
• D. Reports

Answer: (A)

The situation tests how systems manage sequence and locking in workflows, especially for sensitive actions like access provisioning. When a transaction is being processed, the system often locks the related process to prevent conflicting changes and maintain a clean, auditable flow. Access requests are inherently security-critical because they determine who can see or do what in the system. If a new access request were allowed to be submitted while another is still in progress, it could create duplicates, conflicting entitlements, or gaps in approvals. Requiring that no additional access requests be submitted until the current one finishes keeps the provisioning process orderly, ensures proper approvals, and preserves a clear audit trail.

Invoices, change requests, and reports follow different workflow rules and aren’t the type of sensitive, mutually exclusive action that typically needs to be serialized in this way. They can often be processed according to their own queues without blocking new access submissions.