Certified Platform DeveloperDemo

An Apex REST service class must use the @RestResource annotation with a urlMapping that defines the endpoint URL. HTTP method annotations such as @HttpGet or @HttpPost are then applied to its methods.

A Global Picklist Value Set centralizes the shared values for picklists across multiple objects, so they are maintained in one location. Global value sets are restricted picklists, allowing only the administrator-defined values and preventing unapproved values from being used.

Salesforce records Flow coverage in the Tooling API FlowTestCoverage object. SOQL queries against this object can identify Flow versions with coverage and active autolaunched Flows that lack coverage before deployment.

lightning:flow represents a flow interview in Lightning runtime for Aura components. The similarly named lightning-flow component is used in Lightning Web Components, not Aura markup.

For managed packages, the global access modifier makes Apex classes and methods available outside their namespace. A public class or method is accessible only within its own namespace; therefore, both the class and the method must be declared global.

A private static variable declared in a helper class has one shared value for the Apex transaction and can be read or updated by all trigger executions during that transaction. Apex static variables are transaction-scoped; final would prevent subsequent changes to the value.

An Apex method annotated with @TestSetup creates common baseline test records once for the test class and makes them available to each test method. This removes repeated setup code while preserving the ability for individual tests to add data for their specific cases.

An Order Number from an external order system should be an External ID so imported records can be matched or upserted using that source-system identifier. It should also be marked Unique to enforce one Order Number per Salesforce record and prevent duplicate orders.

Record-type metadata obtained from Opportunity.SObjectType.getDescribe().getRecordTypeInfos() reflects the current user’s record-type mappings. The Schema.RecordTypeInfo.isDefaultRecordTypeMapping() method identifies the default mapping; the matching RecordTypeInfo supplies the record type ID to use before inserting the Opportunity.

A scheduled Salesforce Data Export job can automatically generate full-org backup files at monthly intervals. The export can be configured to include all data as well as images, documents, and attachments, which meets the monthly backup requirement.

Visual Studio Code, with the Salesforce Extension Pack, is Salesforce’s recommended editor for developing and correcting Lightning web components and deploying the updated component to an org. Lightning web components cannot be developed in the Salesforce Developer Console.

Queueable executions create AsyncApexJob records, whose status fields can be queried with SOQL. They are also monitored in Setup on the Apex Jobs page, which lists asynchronous Apex jobs and their execution status. The Apex Flex Queue applies to batch Apex jobs rather than Queueable jobs.

Apex methods used with the Lightning Web Components wire service must be annotated with @AuraEnabled(cacheable=true). The cacheable=true attribute is required for wired Apex calls, which provision read-only data through the client-side cache.

Inline autocomplete requires Auto Completions to be enabled, and telemetry must be enabled for Agentforce Vibes in Code Builder. VS Code Inline Suggest affects accepting the next word of an existing suggestion, while autocomplete automatically re-enables after one hour of inactivity.

The Developer Console provides an interface for running Apex tests in an org, and the Tooling API supports programmatic execution of Apex tests. The Bulk API is intended for processing large volumes of data, while the Metadata API is used primarily for metadata migration operations.

Data Loader imports that use the Bulk API insert or update Account records through Salesforce DML. Before triggers run before those record changes are saved, so the applicable Account before trigger is invoked by default.

A QueryException is handled by the catch (QueryException eX) block, which writes Query Exception. The finally block executes after the matching catch block and writes Done., so the resulting output is Query Exception.Done. Salesforce identifies QueryException as a built-in Apex exception that can be handled with a try-catch block.

The Database.insert overload with its allOrNone argument set to false allows partial success. Records that pass validation are inserted, while failed records are reported individually in the returned Database.SaveResult collection.

Aura Components use the Aura programming model, and Lightning Web Components use the Lightning component model with standard DOM events. Both are client-side component technologies used to build responsive Salesforce user interfaces and handle user interactions. Visualforce pages and Visualforce components follow the Visualforce server-rendered page model instead.

Declarative customizations generally need less maintenance because they use Salesforce’s built-in, metadata-driven capabilities instead of custom programmatic logic. Salesforce also delivers automatic platform upgrades during its releases, so declarative metadata is updated with the platform. Declarative configuration does not guarantee the absence of runtime errors and does not automatically generate test classes.

Record-Triggered Flows automate logic when records are created or updated, and Validation Rules enforce data-quality and business constraints without code. Batch Jobs and Remote Actions require Apex.

Batch and future executions are asynchronous Apex jobs. The Apex Jobs page exposes job status, and Developer Console can inspect the associated asynchronous-job information. The Apex Flex Queue applies only to queued Batch Apex jobs, whereas Paused Flow Interviews is for Flow executions. Salesforce documents monitoring asynchronous Apex jobs through the Apex Jobs page.

The Data Import Wizard supports accounts, contacts, leads, solutions, campaign members, person accounts, and custom objects, but not Opportunity records. Data Loader supports all Salesforce objects, including Opportunity, and can import the records.

Lightning web components can import static resources through @salesforce/resourceUrl, content asset files through @salesforce/contentAssetUrl, and SVG resources from the component bundle. External libraries and third-party web components are not the listed Salesforce resource types.