Pass the Salesforce Developers PDII Questions and answers with ExamsMirror

The correct order in tests with callouts is Test.startTest(), then Test.setMock(), followed by the method invocation, and finally Test.stopTest(). This ensures the mock callout is used.

The correct answer is B, lightning-messages. This Lightning Web Components (LWC) service component provides a way to display error messages that are generated during the processing of lightning-input-field components within a lightning-record-edit-form.

Apex triggers on Contact and Account with a helper class is the best practice for code reuse and maintaining clean trigger logic.

To notify an external system about an unhandled exception in a batch job, the appropriate approach is to have the external system subscribe to a custom Platform Event that gets published using EventBus.publish(). When an exception occurs, the batch job can publish this event which the external system can listen for and respond to accordingly. References:

Platform Events Developer Guide

When a test method calls an @future method that performs DML operations, the changes made by the @future method won't be visible until after the Test.stopTest() is called. This method ensures that all asynchronous processes are completed before the test execution continues. Therefore, Test.startTest() should be before the call to the @future method and Test.stopTest() immediately after.

Custom metadata types are ideal for storing payment processor settings that need to be changed by an administrator post-deployment. They can be deployed with managed packages and are upgradeable. Unlike Custom Objects, Custom Metadata Types also support a deployment with active data and can have their records retrieved via SOQL in Apex.

Big objects provide a solution for storing and managing large amounts of data within Salesforce. They are ideal for compliance purposes when tracking long-term usage data that will accumulate over time into very large record counts.

When scheduled Apex runs into DML limits due to a high number of records, implementing the Batchable interface is recommended. This allows the job to be broken down into smaller batches that are processed separately, thus avoiding hitting governor limits. References:

Using Batch Apex

When developing a custom screen that requires both an Account and Contact to be created together, using setSavepoint() and rollback() within a try-catch block is a reliable way to ensure that if the Contact creation fails, the Account creation is also rolled back, maintaining data integrity.

The correct SOQL query to retrieve all fields for a specific Account is to use the FIELDS(ALL) function within the SELECT clause of the SOQL query. This will return all fields for the Account named 'Acme'.