Last Updated On : 18-Nov-2026
Salesforce Platform Developer - Plat-Dev-201 Practice Test
Prepare with our free Salesforce Platform Developer - Plat-Dev-201 sample questions and pass with confidence. Our Salesforce-Platform-Developer practice test is designed to help you succeed on exam day.
Salesforce 2026
What are two considerations for running a flow in debug mode? Choose 2 answers
A. Configure external registers as set command when debugging a flow.
B. Use open-source and parallel tasks where the debugging ends.
C. Input variable of type record cannot be passed into the flow.
D. Clicking Pause or executing a Pause element closes the flow and ends debugging.
D. Clicking Pause or executing a Pause element closes the flow and ends debugging.
Explanation
When debugging a Salesforce Flow, there are specific limitations around the values that can be supplied and what happens when a flow reaches a pause point.
C. Input variable of type record cannot be passed into the flow. — Correct
In Flow Builder's debug functionality, an input variable of the Record data type cannot be directly supplied as a debug input in the same way as simple data types.
Developers can provide supported primitive values, such as text, numbers, dates, and IDs, depending on the flow's variables.
D. Clicking Pause or executing a Pause element closes the flow and ends debugging. — Correct
When debugging a flow, reaching a Pause element or selecting the Pause option ends the current debug run. A paused flow is intended to resume later as part of an actual flow execution, rather than continuing within the current Flow Builder debug session.
Why A is incorrect
A. Configure external registers as set command when debugging a flow. — This is not a standard consideration or requirement for Flow Builder debugging. The terminology and behavior described do not correspond to the normal Salesforce Flow debug process.
Why B is incorrect
B. Use open-source and parallel tasks where the debugging ends. — This does not describe a Salesforce Flow debugging consideration. Open-source and parallel tasks are not standard Flow Builder debug requirements.
Key exam point
For Flow Builder debugging, remember the limitations around input variables and Pause behavior:
Record-type input variables have restrictions when supplying debug values.
A Pause element ends the current debug execution.
Therefore, C and D are the correct answers.
A developer must create a Lightning component that allows users to input Contact record information to create a Contact record, including a Salary__c custom field. What should the developer use, along with a lightning-record-edit-form, so that Salary__c field functions as a currency input and is only viewable and editable by users that have the correct field level permissions on Salary__c?
A. < lightning-input type="number" value="Salary__c" formatter="currency" >< /lightning-input >
B. < lightning-input-currency value="Salary__c" >< /lightning-input-currency >
C. < lightning-input-field field-name="Salary__c" >< /lightning-input-field >
D. < lightning-formatted-number value="Salary__c" format-style="Currency" >< /lightningformatted- number >
Explanation:
Why C is correct: The
Automatic Field Behavior: By passing the field name to field-name,
Field-Level Security (FLS): It automatically respects and enforces the running user's Field-Level Security and object permissions, ensuring that users without permission to view or edit Salary__c cannot interact with or see the field.
Why the other options are incorrect:
A & B. (
D.
References
Lightning Web Components Developer Guide: lightning-input-field
Lightning Web Components Developer Guide: Create and Update Records
The values 'High', 'Medium', and 'Low' are Identified as common values for multiple picklist across different object. What is an approach a developer can take to streamline maintenance of the picklist and their values, while also restricting the values to the ones mentioned above?
A. Create the Picklist on each object and use a Global Picklist Value Set containing the Values.
B. Create the Picklist on each object as a required field and select "Display values alphabeticaly, not in the order entered".
C. Create the Picklist on each object and select "Restrict picklist to the values defined in the value set".
D. Create the Picklist on each and add a validation rule to ensure data integrity.
Explanation:
When multiple objects use the same picklist values (e.g., 'High', 'Medium', 'Low'), the best practice is to:
Define the values once in a Global Picklist Value Set, and
Reference it when creating picklist fields on different objects.
This makes it easier to manage and update values centrally, while also restricting entries to just the predefined list.
Why the other options are incorrect:
B. Alphabetical display setting – Only affects the order of display, not maintenance or restrictions.
C. "Restrict picklist to values defined in value set" – This is good practice, but without using a Global Value Set, you’d have to maintain values separately on each object.
D. Validation rule to ensure data integrity – Not efficient or scalable; better handled with restricted picklists and value sets.
If apex code executes inside the execute() method of an Apex class when implementing the Batchable interface, which statement are true regarding governor limits? Choose 2 answers
A. The Apex governor limits might be higher due to the asynchronous nature of the transaction.
B. The apex governor limits are reset for each iteration of the execute() method.
C. The Apex governor limits are relaxed while calling the constructor of the Apex class.
D. The Apex governor limits cannot be exceeded due to the asynchronous nature of the transaction,
B. The apex governor limits are reset for each iteration of the execute() method.
Explanation:
Key Concept:
Batch Apex runs asynchronously. Each batch chunk of records runs in its own separate transaction.
This means governor limits are reset for each execution of the execute() method.
Governor limits are not relaxed just because it’s asynchronous. You can still hit limits if you’re not careful.
Options Breakdown:
A. The Apex governor limits might be higher due to the asynchronous nature of the transaction. ❌
Limits are the same as other asynchronous contexts (e.g., @future). They’re not “higher” than normal asynchronous limits.
❌ Incorrect.
B. The Apex governor limits are reset for each iteration of the execute() method. ✅
Yes! Each batch execution gets its own governor limits because it’s its own transaction.
✅ Correct.
C. The Apex governor limits are relaxed while calling the constructor of the Apex class. ❌
No, constructors don’t get relaxed limits. Normal limits still apply.
❌ Incorrect.
D. The Apex governor limits cannot be exceeded due to the asynchronous nature of the transaction. ❌
You can definitely exceed them (e.g., too many SOQL queries, too many DMLs) even in Batch Apex.
❌ Incorrect.
✅ Correct Answers:
B
…and also A? Wait — let’s be extra careful here.
Actually, Salesforce does give slightly higher limits for asynchronous operations (like Batch Apex and Queueable). For example:
➡️ SOQL query rows limit: 50,000 in synchronous vs. 50,000 (but per batch execution).
➡️ Future, Batch, Queueable sometimes allow more total queries and DML statements compared to synchronous.
So A is also correct: asynchronous contexts can have higher limits compared to synchronous execution.
Which three code lines are required to create a Lightning component on a Visualforce page? Choose 3 answers
A. $Lightning.createComponent
B. < apex:slds > < /apex:slds>
C. $Lightning.useComponent
D. $Lightning.use
E. < apex : includeLightning / >
D. $Lightning.use
E. < apex : includeLightning / >
Explanation:
To embed a Lightning component on a Visualforce page, Salesforce provides the $Lightning global object and some required Visualforce tags.
A. $Lightning.createComponent
Used to dynamically create and insert the Lightning component into the Visualforce page.
D. $Lightning.use
Initializes the Lightning runtime and specifies which Lightning component bundle to use. It's required before calling createComponent.
E.
Incorrect Options:
B. < apex : slds >
This is used to include SLDS styles, not required to embed a Lightning component.
C. $Lightning.useComponent
Not a real method — invalid in the Lightning global object.
| Salesforce-Platform-Developer Exam Questions - Home | Previous |
| Page 4 out of 37 Pages |