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 is one limitation of Agentforce's language support capabilities?
A. Language support for toxicity is the same as the supported languages
B. Topic and action instructions are supported in multiple languages
C. Language and tone settings impact the output of agent actions when specified
D. Language support may differ by agent type
Explanation:
A documented limitation of Agentforce's multilingual capabilities is that language support is not uniform across all agent types. Different Agentforce agent types, such as Agentforce Service Agent, Agentforce for Sales, and custom agents built via Agent Builder, can have different levels of supported languages depending on the underlying channel, model, and feature set they use. This means a language that works well for one agent type may not be fully supported or may behave differently for another agent type. Therefore, developers and administrators should verify language support for each agent type rather than assuming uniform coverage across the entire Agentforce platform.
Why the other options are wrong:
A. Language support for toxicity is the same as the supported languages.
This is not accurate as a limitation. Toxicity detection, which is part of the Einstein Trust Layer, and general agent language support are separate, independently governed capabilities with their own coverage. They are not guaranteed to align, so this statement does not correctly describe a documented limitation of language support itself.
B. Topic and action instructions are supported in multiple languages.
This describes a capability or benefit rather than a limitation. The question specifically asks for a limitation, so a positive capability statement does not fit.
C. Language and tone settings impact the output of agent actions when specified.
This describes expected or intended behavior, not a limitation or constraint on the platform's capabilities.
Reference
Guide to Understanding Multi-Language Support in Agentforce – Salesforce
Since Agentforce is a fast-evolving product area with frequent documentation updates, it is recommended to cross-check this information against the latest Salesforce Certified Platform Developer I exam guide, as newer exam content involving Agentforce may not be fully reflected in older PDI preparation materials.
Which two operations affect the number of times a trigger can fire?
A. After-save record-triggered flow
B. Email messages
C. Roll-up summary fields
D. Criteria-based sharing calculations
C. Roll-up summary fields
Explanation:
A. After-save record-triggered flow
An after-save (after-insert/after-update) record-triggered Flow can perform additional DML operations (updating fields, creating related records, etc.) on the same or related records. If that Flow updates a record in a way that causes another save on the object, such as updating a field on the same record type, or updating a related record that has its own triggers, it can cause the trigger to fire again, potentially leading to recursive trigger execution within the same transaction.
C. Roll-up summary fields
Roll-up summary fields, defined on a master object in a Master-Detail relationship, automatically recalculate whenever a detail (child) record is created, updated, or deleted. This recalculation constitutes an update to the master record, which means it fires the master object's triggers as well, even though no direct DML was performed on the master record by the user or developer's code. This is a well-known consideration when designing trigger logic on objects that have roll-up summary relationships.
Why the other options are wrong:
B. Email messages
Sending or receiving email, such as via Email-to-Case or Apex-sent emails, does not by itself cause DML on records or trigger firing of Apex triggers unless it explicitly creates or updates a record, such as an EmailMessage record tied to a Case. However, email messages as a general operation are not a standard consideration for trigger firing counts in the same category as flows or roll-up summaries.
D. Criteria-based sharing calculations
Sharing rule recalculations manage record visibility and access and run as a background or asynchronous process. They do not perform DML on the record's core data in a way that invokes standard Apex triggers on that object.
Reference
Roll-Up Summary Fields and Triggers | Trigger Recursion Considerations
A developer is asked to update code that requires them to validate input into a trigger. Which Apex Control Flow Statement should the developer use?
A. Conditional (If-Else) Statement
B. While Loop
C. Switch Statement
D. For Loop
Explanation:
Why A is correct: When validating field inputs, checking record criteria, or enforcing custom error conditions inside an Apex trigger using .addError(), developers rely on Conditional (if-else) statements. After iterating through the trigger collection using a loop, an if condition checks whether specific field values violate business rules and triggers the appropriate error response.
Why the other options are incorrect:
B. While Loop — A while loop is used for iterative looping based on a Boolean condition rather than checking individual field value conditions for record-by-record validation.
C. Switch Statement — A switch statement evaluates a single expression against multiple discrete values or patterns, which is less suited for general Boolean condition validation across custom field inputs.
D. For Loop — While a for loop is used to iterate through Trigger.new or Trigger.old to ensure proper bulkification, the validation logic itself, such as checking whether a value meets certain criteria and throwing an error, is governed by conditional if-else statements.
References
Salesforce Apex Developer Guide: Conditional Statements (if-then-else)
A developer receives an error when compiling the following code:
switch on sObject {
when Account a, Contact c {
System.debug('account ' + a);
System.debug('contact ' + c);
}
when null {
System.debug('null');
}
when else {
System.debug('default');
}
}
What is the error?
A. Switch statements cannot contain multiple when values.
B. There is incompatible variable binding.
C. Only one sObject type per when block can be used.
D. There is an unexpected token 'Contact'.
Explanation:
Why C is correct: In Apex, when using a switch statement on an sObject type, each when block can only evaluate a single sObject type along with its variable binding. You cannot combine multiple different sObject types, such as Account a and Contact c, into a single comma-separated when block. Each sObject type requires its own separate when block.
Why the other options are incorrect:
A. Switch statements cannot contain multiple when values — Switch statements can contain multiple values, but only for specific types such as primitive literals, including integers and strings, or enums. This does not mean multiple variable-bound sObject types can be combined in a single when block.
B & D. Incompatible variable binding / Unexpected token — The syntax error is specifically caused by the limitation of pairing multiple different sObject types in a single when statement clause rather than by an unexpected token or a generic variable binding failure.
References
Salesforce Apex Developer Guide: Switch Statements (Example with sObjects)
A developer completed modifications to a customized feature that is comprised of two
elements:
•
Apex trigger
•
Trigger handler Apex class
What are two factors that the developer must take into account to properly deploy the
modification to the production environment?
Choose 2 answers
A. All methods in the test classes must use 'assert'.
B. At least one line of code must be executed for the Apex trigger.
C. At least 75% of Apex code must be covered by unit tests.
D. The Apex trigger must be included in a Change Set.
C. At least 75% of Apex code must be covered by unit tests.
Explanation:
The modification consists of an Apex trigger and its trigger handler Apex class. Before deploying Apex to a Salesforce production environment, the developer must satisfy Salesforce's Apex testing and code coverage requirements.
B. At least one line of code must be executed for the Apex trigger. — Correct
Salesforce requires that every Apex trigger have some test coverage before it can be deployed to production.
The test must actually execute the trigger. For example, if the trigger is a before insert trigger, the test should perform an insert operation that causes the trigger to execute.
Simply testing the trigger handler class directly does not provide coverage for the trigger itself.
C. At least 75% of Apex code must be covered by unit tests. — Correct
Salesforce requires at least 75% Apex code coverage for production deployment.
The tests should cover the Apex trigger and its handler class sufficiently to meet the required overall coverage. A good test should also verify the expected behavior using assertions, although assertions themselves are not the specific deployment requirement represented by option A.
Why A is incorrect
A. All methods in the test classes must use assert. — Assertions are important because they verify that the code behaves as expected, but Salesforce does not require every test method to contain an assert statement as a condition for deployment.
Why D is incorrect
D. The Apex trigger must be included in a Change Set. — A Change Set is one deployment mechanism, but the trigger does not specifically have to be deployed through a Change Set. Apex can be deployed through other supported mechanisms, such as Salesforce CLI or Metadata API.
The deployment requirements concern testing and code coverage, not the specific deployment tool.
| Salesforce-Platform-Developer Exam Questions - Home | Previous |
| Page 3 out of 37 Pages |