Platform Developer II Sample Questions & Answers

Custom Metadata Types are the best fit for this scenario. They are deployable, meaning the configuration data can be moved between environments as metadata. They can be queried using SOQL, and they support relationships, allowing the developer to model the parent-child structure between 'Service Levels' and 'Country Surcharges'. Custom Objects are data, not metadata, and are harder to deploy. Custom Settings are not as well-suited for complex relational structures and are less easily deployed.

The query is timing out because it is non-selective. It has to perform a full table scan on 10 million records to find contacts where LastLoginDate is older than 180 days. Standard date fields like LastLoginDate are not indexed by default. The most effective solution is to work with Salesforce Support to create a custom index on this field. This will make the query highly selective and allow it to execute efficiently without timing out.

This statement is true. The External ID field must uniquely identify a single record for the upsert operation to succeed. If the value of the External ID field is not unique and matches multiple existing records, the operation will fail and a DmlException will be thrown, indicating that multiple records were found for the upsert.

The @InvocableMethod annotation is specifically designed to expose an Apex method as a callable action in declarative tools like Process Builder, Flow, and the REST API. The method must be static and can have only one parameter, which must be a list of a primitive data type or a custom Apex class.

Queueable Apex is the best fit. It runs asynchronously, so it won't delay the Opportunity save. Crucially, a Queueable job can enqueue another job from within its execute method, which allows for complex patterns like implementing a retry mechanism. The job can maintain a retryCount state variable and, upon failure, re-enqueue itself if the count is below the threshold. @future methods cannot call other @future methods, and Batch Apex is overkill for a single callout.

The standard and recommended best practice for preventing trigger recursion within a single transaction is to use a static Boolean variable. A utility class holds the static variable (e.g., hasAlreadyRun). The trigger checks this variable before executing its logic. If it's false, it sets it to true and runs the logic. If it's already true, it bypasses the logic, preventing the recursive call from re-executing.

Custom Labels are the standard Salesforce feature for storing translatable text. By creating a Custom Label for each piece of text and referencing it in Visualforce with the syntax $Label.MyLabelName, the platform will automatically display the correct translation based on the user's language setting, provided that translations have been entered in the Translation Workbench.

To create an Apex REST service, the class must be annotated with @RestResource(urlMapping='/Your/Endpoint/*'). Within this class, specific methods handle different HTTP verbs. The method to handle GET requests must be annotated with @HttpGet, and the method to handle POST requests must be annotated with @HttpPost.

A controller extension's constructor requires an instance of ApexPages.StandardController as its argument. To test it, you must first create the record the controller will be based on (e.g., an Account). Then, you create a new ApexPages.StandardController instance, passing the test record to its constructor. Finally, you instantiate your extension, passing the standard controller instance to its constructor.

The Lightning Data Service provides client-side caching for @AuraEnabled(cacheable=true) methods, but this is primarily leveraged when using the @wire service. If components call the same cacheable Apex method imperatively (e.g., in connectedCallback), the framework does not automatically deduplicate these calls. The @wire service is designed to recognize identical requests (method and parameters) and serve subsequent requests from its client-side cache, resulting in only one server trip.