Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
What are three considerations when using the @lnvocableMethod annotation in Apex?
Choose 3 answers
Option A: Only one method annotated with@InvocableMethodcan exist per class.
Option C: The method must bestatic.
Option E: The method can be declared asPublicorGlobalfor broader accessibility.
:Invocable Methods Documentation
A developer wrote Apex code that calls out to an external system using REST API.
How should a developer write the test to prove the code is working as intended?
To test Apex code that makes HTTP callouts, Salesforce provides theHTTPCalloutMockinterface. Developers create a test class that implementsHTTPCalloutMockto define the fake response that will be returned when the callout is executed during the test.
This ensures that tests do not depend on the availability or behavior of the external system.
Why not other options?
BandC: These are not relevant for testing HTTP callouts.
D: There is no concept of extendingHTTPCalloutMock. It is implemented, not extended.
:
Apex Testing for HTTP Callouts
Universal Containers wants a list button to display a Visualforce page that allows users to edit multiple records.
Which Visualforce feature supports this requirement?
TherecordSetVarattribute of the
Why not other options?
A: Standard controllers can be extended, but usingrecordSetVaris the direct and best-supported method for this scenario.
B: There is no such concept as a 'Custom List Controller' in Visualforce.
C:<spex:listButton>is not a valid Visualforce tag.
:
Visualforce Standard Controller with RecordSetVar
Universal Containers is building a recruiting app with an Applicant object that stores information about an individual person and a Job
object that represents a job. Each applicant may apply for more than one job.
What should a developer implement to represent that an applicant has applied for a job?
A . Junction object between Applicant and Job:
Since anApplicantcan apply for multipleJobsand eachJobcan have multipleApplicants, this is amany-to-many relationship.
Salesforce requires ajunction objectto represent many-to-many relationships. The junction object will have two master-detail relationships: one to the Applicant object and one to the Job object.
The junction object could be named something like JobApplication__c, which would represent the specific instance of an applicant applying for a particular job.
Why this is the correct approach?
A junction object allows for robust data management and reporting capabilities in a many-to-many relationship.
This design ensures that each combination of applicant and job is captured as a unique record in the JobApplication__c junction object.
It also allows storing additional details about the application, such as application date, status, and feedback.
Why not the other options?
B . Lookup field from Applicant to Job:
A lookup field creates a one-to-many relationship. While an Applicant could reference one Job, it does not support the many-to-many relationship required in this scenario.
C . Master-detail field from Applicant to Job:
A master-detail relationship is a one-to-many relationship, which is unsuitable for a many-to-many relationship. Additionally, you cannot have two master-detail fields on a single object to connect Applicant and Job directly.
D . Formula field on Applicant that references Job:
A formula field cannot establish relationships between records or represent a many-to-many relationship. It is only for computed fields.
Creating Many-to-Many Relationships with Junction Objects
Master-Detail and Lookup Relationship Details
How many Accounts will be inserted by the following block of code?
Execution Flow:
The loop runs 500 times (iranges from 0 to 499).
In each iteration, a newAccountrecord is created and inserted.
Governor Limits:
This code violates the governor limit of 150 DML statements per transaction because eachinsertis executed individually.
However, the code logically attempts to insert 500 accounts.
Key Consideration:
The code demonstrates inefficient handling of DML operations and would fail in a real-world scenario.
Which annotation exposes an Apex class as a RESTful web service?
The@RestResourceannotation exposes an Apex class as a RESTful web service. TheurlMappingparameter defines the endpoint's URL.
Incorrect Options:
A:@RemoteActionis used for JavaScript remoting.
C:@HttpInvocableis used for invocable methods, not REST services.
D:@AuraEnabledis for enabling methods in Aura components or LWC, not REST services.
Exam domains verified against: Official Salesforce Plat-Dev-201 exam guide, last checked September 2026.
Understand multi-tenant concepts and design frameworks such as MVC architecture and Lightning Component Framework. Learn to identify common use cases and best practices for choosing between declarative and programmatic customizations, including how to work with governor limits, formula fields, and roll-up summaries.
Sample question from this domain above: Q4
Master declarative process automation features and Apex language fundamentals including variables, constants, methods, and interfaces. Write and optimize SOSL, SOQL, and DML statements while understanding governor limits, transaction execution, exception handling, and best practices for triggers and classes.
Prevent security vulnerabilities in user interfaces and data access controls. Build custom UI components using Lightning Web Components, Flow, and Visualforce, and implement Apex to work effectively with various page components including Lightning components, Flow, and Agentforce.
Sample question from this domain above: Q3
Write and execute comprehensive tests for triggers, controllers, classes, and flows using various test data sources. Use Salesforce Developer tools like Salesforce DX, Salesforce CLI, and Developer Console, then approach debugging and deployment with knowledge of environments, requirements, and processes.
Sample question from this domain above: Q2
Common questions about the exam itself
