Which use case is an appropriate fit for the @future asynchronous Apex method? (Choose two.)
A. A developer has jobs that need larger query results than regular transactions allow
B. A developer needs to segregate DML operations and bypass the mixed save DML error
C. A developer has long-running jobs with large data volumes that need to be performed in batches
D. A developer has long-running methods and needs to prevent delaying an Apex transaction
Suggest answer: BD
Reference:
No comments:
Please share to make the community better.