Free Salesforce Certified Platform Developer practice test: 30 questions with answers

The static modifier ties the value to the class, and final stops it from being reassigned after it is set. The instance field and the plain static field can both be changed, and const is not an Apex keyword.

A class uses implements and must write a body for every method the interface declares, because Apex interfaces contain only method signatures. extends is for classes, interfaces cannot be instantiated, and no implementation is supplied automatically.

break leaves the innermost loop at once, and execution continues with the statement after the loop. The skip-to-next-iteration behaviour belongs to continue, and break neither returns from the method nor restarts the loop.

Querying once for the whole batch and matching results through a Map keeps SOQL and DML counts flat no matter how many records arrive. DML or SOQL inside the loop repeats the cost for every record, and processing only the first record leaves the rest of the batch unhandled.

SOSL searches text fields across several objects in one call with FIND and RETURNING, which matches this pattern. SOQL reads one object and its related records, so it cannot join unrelated objects or search every field, and upsert writes records rather than searching them.

The recommended pattern is one trigger per object that delegates to handler classes, which keeps logic in one organized and testable place. Per-field and per-profile triggers cause duplicated or unpredictable behaviour, and inline logic is hard to test and reuse.

A static variable lasts for the whole transaction, so a flag set on the first pass lets the trigger skip work on the re-run that the workflow causes. Disabling the trigger, moving logic to a page, or renaming the trigger does not guard against the repeat run.

addError on a record in Trigger.new blocks that record's save and displays the message to the user. Changing the Name field does not stop the save, System.debug only writes to the log, and a Task is created without preventing the save.

A master-detail relationship makes the child required, cascades deletes from the parent, and inherits sharing from it. A lookup is optional with no cascade delete, hierarchical relationships exist only on the User object, and external lookups point to external data rather than Account records.

An External ID field stores an identifier from another system so that upsert can match an incoming record to an existing one without knowing its Salesforce Id. It is not a formula, it is not filled in automatically with the record Id, and it is not limited to standard objects.

Running one SOQL query per record can exceed the per-transaction SOQL governor limit, so the query should run once with a set of Ids and the results should be kept in a Map. The other options still query per record or only move or split the same work without reducing the number of queries.

Multi-tenancy means many customers share the same infrastructure with logically separated data, and governor limits keep one tenant from monopolizing shared resources. Dedicated servers per org, default cross-org queries, and self-maintained database engines do not describe how the platform works.

Lightning Web Components are built on standard web component APIs, including custom elements and the shadow DOM. Aura is Salesforce's older proprietary component model, Visualforce is a page framework, and declarative flow screens do not expose web component code.

A validation rule is a declarative formula that blocks a save and shows an error when its condition is true, so it needs no code. Triggers, Visualforce controllers and JavaScript validators all require code and do not meet the no-code requirement.

A many-to-many relationship is modeled with a junction object that has a master-detail relationship to each parent. A single lookup allows only one parent per record, a self-lookup relates Candidates only to Candidates, and a comma-separated text field cannot be queried or reported relationally.

AI-generated code is a draft that still needs human review, test coverage, and checks against governor limits and sharing rules before production. The other options skip verification or weaken security, which is unsafe.

Visualforce output components escape special characters by default because the escape attribute is true, so the browser renders the script as plain text. Stripping characters, disabling all JavaScript, or encrypting the input are not how this default protection works.

with sharing applies the running user's record-level sharing rules to queries and DML in the class. Field-level security is a separate check, and running in system mode ignores record-level sharing, which is the opposite of with sharing.

WITH SECURITY_ENFORCED makes the query check field and object read access for the running user and throw an exception when access is missing. LIMIT caps rows, FOR UPDATE locks records, and WITH SYSTEM_MODE skips field-level checks, so none of those meets the requirement.

lightning-flow embeds and runs a flow, with its screens displayed in the component. The other base components show a record's fields, show a grid of rows, or edit one field, and none of them runs a flow.

standardController takes the object name, here Account, and gives the page built-in record behaviour. controller names a custom Apex class, extensions names Apex classes that add logic on top of a standard controller, and sObjectType is not an apex:page attribute.

Events travel up the component tree: the child dispatches a CustomEvent and the parent listens with an event handler in its template. Parents should not reach into a child's private state, and global or window storage bypasses the component model.

apex:actionFunction generates a JavaScript function that invokes a controller action and can re-render part of the page. outputLink navigates to another URL, repeat only iterates over a collection, and includeScript only loads a script file.

Production deployments require at least 75 percent overall Apex code coverage across the org. Fifty percent falls below the required threshold, while the 90 and 100 percent options describe targets that are not the minimum requirement.

Test.startTest() gives the code under test a fresh set of governor limits, and Test.stopTest() makes queued asynchronous work run before the test continues. runAs changes the user context, savepoint and rollback manage transactions, and TestSetup creates shared test data.

Scratch orgs are built from a definition file and are meant to be temporary, expiring after a set period. They do not copy production data and are not designed for live business records, and permanent orgs are a different kind of org.

The Execute Anonymous window runs Apex typed straight into the console without creating a class, and it shows the debug output. The Query Editor runs SOQL, the Log Inspector reviews existing logs, and Checkpoints record variable state at chosen lines in a log rather than running new code.

The Apex Jobs page in Setup lists asynchronous work such as batch jobs with their status and error counts, which fits an overnight batch. The other pages show installed packages, company profile details, and email settings, none of which track batch progress.

Test.setMock registers a class that implements HttpCalloutMock, so the code under test receives a canned response instead of calling the real service. Calling the live service makes tests unreliable, SeeAllData exposes org data rather than mocking the callout, and swallowing the exception hides the behaviour under test.

sf project deploy start pushes source from the local project to the target org. The retrieve command goes the other way, org create scratch makes a new org, and apex run test runs existing tests without deploying anything.