Salesforce PDII Online Practice Questions and Exam Preparation

Salesforce PDII Online Questions & Answers

• Question 31:

  A query using OR between a Date and a RecordType is performing poorly in a Large Data Volume environment. How can the developer optimize this?

  A. Break down the query into two individual queries and join the two result sets.
  B. Annotate the method with the @Future annotation.
  C. Use the Database.querySelector method to retrieve the accounts.
  D. Create a formula field to combine the CreatedDate and RecordType value, then filter based on the formula.
  A. Break down the query into two individual queries and join the two result sets.

  ---

  Explanation

  In SOQL, using the OR operator often prevents the Query Optimizer from using indexes effectively, especially if the fields involve different types of data. This is known as a "non-selective" query structure in LDV environments.

  By breaking the query into two separate SOQL statements (Option A), the developer allows each query to be evaluated independently.

  SELECT ... FROM Account WHERE CreatedDate = :thisDate (Uses the standard index on CreatedDate).

  SELECT ... FROM Account WHERE RecordTypeId = :goldenRT (Uses the standard index on RecordTypeId).

  The developer can then combine the results into a Map<Id, Account> to ensure uniqueness (preventing duplicates if a record meets both criteria). This approach ensures both queries are "selective" and run much faster than a single query with an OR filter.

  Option D is a common anti-pattern because formulas are generally not indexed unless they are "deterministic" and a custom index is requested from Salesforce support; even then, filtering on formulas is often slower than direct field filters.

  Option B and C do not address the underlying database performance issue.

• Question 32:

  What is the transaction limit for SOQL queries?

  A. 20 (synchronous), 200 (async)
  B. 150 (synchronous), 20 (async)
  C. 150 (synchronous), 200 (async)
  D. 100 (synchronous), 200 (async)
  E. 200 (synchronous), 100 (async)
  D. 100 (synchronous), 200 (async)

• Question 33:

  A developer has a Visualforce page that automatically assigns ownership of an Account to a queue upon save. The page appears to correctly assign ownership, but an assertion validating the correct ownership fails.

  What can cause this problem?

  A. The test class does not use the Bulk API for loading test data.
  B. The test class does not retrieve the updated value from the database.
  C. The test class does not use the seeAllData=true annotation.
  D. The test class does not implement the Queueable interface.
  B. The test class does not retrieve the updated value from the database.

  ---

  Explanation

  A frequent mistake in Apex unit testing is failing to recognize that SObject variables in memory do not automatically reflect changes made to the database by triggers, flows, or other logic. When the developer saves the Account record in the test, the database is updated (e.g., a trigger or the controller changes the OwnerId to the Queue ID). However, the variable used in the test still holds the original data that was present when it was first instantiated or inserted.

  To successfully assert the change, the developer must perform a "refresh" query. This involves using a SOQL statement to retrieve the record from the database using its ID: Account updatedAcc = [SELECT OwnerId FROM Account WHERE Id = :acc.Id];. The assertion should then be performed against updatedAcc.OwnerId.

  Option B correctly identifies this as the root cause. Option D is irrelevant as Queueable is an asynchronous execution pattern. Option C (seeAllData=true) is a poor practice and is not required for testing logic that modifies records. Option A is unrelated to assertion logic. Standard test isolation requires that you explicitly re-query the database to verify side effects caused by platform automation or controller logic.

• Question 34:

  What is a consideration when using bind variables with dynamic SOQL? (Choose two.)

  A. Dynamic SOQL cannot reference fields on bind variables
  B. Dynamic SOQL cannot use bind variables
  C. Bind variables must be public or global
  D. Bind variables must be in local scope
  A. Dynamic SOQL cannot reference fields on bind variables
  D. Bind variables must be in local scope

• Question 35:

  An Apex trigger creates a Contract record every time an Opportunity record is marked as Closed end Won. This trigger is working great, except (due to a recent acquisition) historical Opportunity records need to be loaded into the Salesforce instance.

  When a test batch of records are loaded, the Apex trigger creates Contract records. A developer is tasked with preventing Contract records from being created when mass loading the Opportunities, but the daily users still need to have the Contract records created.

  What is the most extendable way to update the Apex trigger to accomplish this?

  A. Use a List Custom Setting to disable the trigger for the user who loads the data.
  B. Add a Validation Rule to the Contract to prevent Contract creation by the user who loads the data.
  C. Use a Hierarchy Custom Setting to skip executing the logic inside the trigger for the user who loads the data.
  D. Add the Profile ID of the user who loads the data to the trigger so the trigger will not fire for this user.
  C. Use a Hierarchy Custom Setting to skip executing the logic inside the trigger for the user who loads the data.

  ---

  Explanation

  When managing trigger logic that needs to be conditionally bypassed (often called a "Trigger Kill Switch"), using Hierarchy Custom Settings (Option C) is the best practice for scalability and maintainability. A developer can create a Hierarchy Custom Setting named Trigger_Settings__c with a checkbox field Disable_Opportunity_Trigger__c. In the Apex trigger, the code should first check this setting:

  if (Trigger_Settings__c.getInstance().Disable_Opportunity_Trigger__c) return;

  Because it is a hierarchy setting, an administrator can enable this checkbox specifically for the User or Profile performing the data load without affecting the daily operations of other sales reps. Once the data load is complete, the setting can be toggled off. This approach is "extendable" because it doesn't require hardcoding IDs (Option D), which change between environments (Sandbox vs. Production).

  Option A (List Custom Settings) is less flexible because it doesn't support the Profile-to-User hierarchy.

  Option B (Validation Rules) would stop the record creation but would result in a DML error in the trigger, potentially failing the entire data load transaction rather than simply skipping the logic. Hierarchy Custom Settings provide a clean, metadata-driven way to control execution flow across different user contexts.

• Question 36:

  A company wants to run different logic based on an Opportunity's record type. Which code segment handles this request and follows best practices?

  A. List<RecordType> recTypes = [SELECT Id, NameFROM RecordTypeWHERE SobjectType = 'Opportunity' AND IsActive = true];Map<String, Id> recTypeMap = new Map<String, Id>();for (RecordType rt : recTypes) {recTypeMap.put(rt.Name, rt.Id);}for (Opportunity o : Trigger.new) {if (o.RecordTypeId == recTypeMap.get('New')) {// do some logic Record Type 1} else if (o.RecordTypeId == recTypeMap.get('Renewal')) {// do some logic for Record Type 2}}
  B. for (Opportunity o : Trigger.new) {if (o.RecordType.Name == 'New') {// do some logic Record Type 1} else if (o.RecordType.Name == 'Renewal') {// do some logic for Record Type 2}}
  C. List<RecordType> recTypes = [SELECT Id, NameFROM RecordTypeWHERE SobjectType = 'Opportunity' AND IsActive = true];Map<String, Id> recTypeMap = new Map<String, Id>();for (RecordType rt : recTypes) {recTypeMap.put(rt.Name, rt.Id);}for (Opportunity o : Trigger.new) {if (recTypeMap.get('New') != null && o.RecordTypeId == recTypeMap.get('New')) {// do some logic Record Type 1} else if (recTypeMap.get('Renewal') != null && o.RecordTypeId == recTypeMap.get('Renewal')) {// do some logic for Record Type 2}}
  D. Id newRecordTypeId =Schema.SObjectType.Opportunity.getRecordTypeInfosByName().get('New').getRecordTypeId();Id renewalRecordTypeId =Schema.SObjectType.Opportunity.getRecordTypeInfosByName().get('Renewal').getRecordTypeId();for (Opportunity o : Trigger.new) {if (o.RecordTypeId == newRecordTypeId) {// do some logic Record Type 1} else if (o.RecordTypeId == renewalRecordTypeId) {// do some logic for Record Type 2}}
  A. List<RecordType> recTypes = [SELECT Id, NameFROM RecordTypeWHERE SobjectType = 'Opportunity' AND IsActive = true];Map<String, Id> recTypeMap = new Map<String, Id>();for (RecordType rt : recTypes) {recTypeMap.put(rt.Name, rt.Id);}for (Opportunity o : Trigger.new) {if (o.RecordTypeId == recTypeMap.get('New')) {// do some logic Record Type 1} else if (o.RecordTypeId == recTypeMap.get('Renewal')) {// do some logic for Record Type 2}}

  ---

  Explanation

  In Salesforce Apex development, the best practice for retrieving Record Type IDs is to avoid SOQL queries and instead use the Schema Describe methods. Option D utilizes Schema.SObjectType.Opportunity.getRecordTypeInfosByName(), which retrieves metadata directly from the application's local cache.

  There are three primary reasons why Option D is superior to the others:

  Governor Limits: Salesforce imposes a strict limit of 100 SOQL queries per synchronous transaction. Options A and C consume one of these limited queries just to fetch metadata. In a complex environment where many triggers and flows execute, saving SOQL queries for actual business data is crucial. Describe calls do not count against SOQL limits.

  Performance: Fetching data from the metadata cache is significantly faster than executing a database query, leading to lower CPU usage and faster trigger execution.

  Data Integrity: Option B is a common anti-pattern that can result in a runtime error. In an Apex trigger, the Trigger.new list only contains the fields of the object itself. It does not include related fields (cross-object fields) like RecordType.Name. Accessing o.RecordType.Name directly would return null or cause a System.SObjectException: SObject row was retrieved via SOQL without querying the requested field.

  By using the Schema class, the developer ensures that the code is bulk-safe, performant, and does not hardcode IDs, which can vary between sandbox and production environments.

• Question 37:

  What is a best practice when unit testing a controller? (Choose two.)

  A. Simulate user interaction by leveraging Test.setMock()
  B. Verify correct references by using getURL()
  C. Access test data by using seeAIIData=true
  D. Set query parameters by using getParameters().put
  B. Verify correct references by using getURL()
  D. Set query parameters by using getParameters().put

• Question 38:

  A developer sees test failures in the sandbox but not in production. No code or metadata changes have been actively made to either environment since the sandbox was created.

  Which consideration should be checked to resolve the issue?

  A. Ensure the Apex classes are on the same API version.
  B. Ensure test classes are using SeeAllData = true.
  C. Ensure the sandbox is on the same release as production.
  D. Ensure that Disable Parallel Apex Testing is unchecked.
  C. Ensure the sandbox is on the same release as production.

  ---

  Explanation

  When code behavior differs between two environments that theoretically share the same codebase, the root cause is often the underlying platform version. Salesforce releases updates (e.g., Spring, Summer, Winter) on a staggered schedule. Sandbox instances are frequently updated to the "Preview" version of the upcoming release weeks before the Production environment.

  Option C , it may include changes to the Apex compiler, new platform If a sandbox is on a newer release governor limits, or modifications to how standard objects behave. If a test relies on a specific behavior that changed in the new release, it might fail in the sandbox while still passing in the older Production environment.

  Option B (SeeAllData=true) is a poor practice and would likely cause more issues rather than resolve them. Option A is unlikely because API versions are fixed in the metadata of the class and wouldn't change spontaneously. Option D relates to execution speed and resource contention but rarely causes a functional test to pass in one environment and fail in another unless there are significant race conditions. Checking the release version is the standard first step when diagnosing environment-specific discrepancies in the absence of code changes.

• Question 39:

  How can the DISTANCE and GEOLOCATION functions be used i|n SOQL queries? (Choose two.)

  A. To filter results based on distance from a latitude and longitude
  B. To get the distance results from a latitude and longitude
  C. To order results by distance from a latitude or longitude
  D. To group results in distance ranges from a latitude and longitude
  A. To filter results based on distance from a latitude and longitude
  C. To order results by distance from a latitude or longitude

• Question 40:

  A developer has created a Team Member sObject that has a Master-Detail relationship to a Project sObject and a Lookup relationship to the User sObject. The developer must ensure that a User listed on a Team Member record has Read- Write access to the parent Project record.

  How can the developer accomplish this if the Project sObject has a Private sharing model and thousands of Project records?

  A. Create a Controller that uses the Without Sharing keyword
  B. Create a Criteria-Based Sharing Rule on the Project sObject
  C. Create a Team Member Trigger that inserts Project_Share records
  D. Create a Project Sharing Rule that shares to the Team Member Group
  C. Create a Team Member Trigger that inserts Project_Share records