Exam Certified Platform Developer II topic 1 question 69 discussion

1. Queueable Jobs can contain the member variable as SObjects or custom Apex Types. 2. When using queueable jobs it will make the AsyncApexJob which we can monitor like Scheduled jobs. 3. Queueable Apex can be called from the future and batch class. 4. Using Queueable Apex will chain up to queueable jobs and in Developer Edition it is only 5 Jobs.

So ignoring the part that B is spelled wrong, D is needed for several reasons, most already mentioned. There is a second part to this though that allows for the queueable process to be reviewed, and this is generally handled with a transaction finalizer. Trailhead: https://trailhead.salesforce.com/content/learn/modules/asynchronous_apex/async_apex_queueable Finalizers: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_transaction_finalizers.htm

It's gotta be a queue. Database.AllowsCallouts (not Database.AllowCallouts) is the correct name of the interface.

Methods with the future annotation must be static methods, and can only return a void type. The specified parameters must be primitive data types, arrays of primitive data types, or collections of primitive data types. Methods with the future annotation cannot take sObjects or objects as arguments.