Salesforce PDII Online Practice Questions and Exam Preparation

Salesforce PDII Online Questions & Answers

• Question 81:

  What is the transaction limit for the number of records for SOQL queries?

  A. 5,000
  B. 20,000
  C. 50,000
  D. 10,000
  E. There is no limit
  C. 50,000

• Question 82:

  Which statement is considered a best practice for writing bulk safe Apex Triggers?

  A. Perform all DML operations from within a Future Method.
  B. Use the Database methods with allOrNone set to false instead of DML statements.
  C. Add records to collections and perform DML operations against these collections.
  D. Add LIMIT 50000 to every SOQL statement
  C. Add records to collections and perform DML operations against these collections.

  ---

  Explanation

  The most fundamental best practice for writing bulk-safe (scalable) Apex triggers is to avoid performing DML operations or SOQL queries inside of loops . Salesforce enforces a limit of 150 DML statements per transaction. If a trigger iterates through a list of 200 records and performs a delete or update inside that loop, the code will fail with a governor limit exception after the 150th record.

  To make a trigger bulk-safe, developers must collect all records that need to be processed into a collection (such as a List or Map) and then perform a single DML operation on that entire collection outside of the loop ( Option C ). This consumes only one DML statement regardless of the number of records (up to the 10,000 row limit).

  Option D is incorrect because LIMIT 50000 does not help with bulk safety; it just prevents a query from exceeding the SOQL row limit. Option B (using allOrNone=false) allows for partial success of a DML operation but does not inherently make a trigger bulk-safe if the calls are still made inside a loop. Option A is incorrect because moving DML to a future method is a way to handle callouts or long-running processes, but it is not a general requirement for trigger bulkification and can lead to reaching asynchronous limits if used incorrectly.

• Question 83:

  Which are relevant practices while analyzing the timeline of different types of transactions in the execution overview panel? (Choose two.)

  A. Log lines in the execution log panel can be analyzed for details about specific events
  B. The performance tree should be use to analyze events further starting from the one that take the least amount of time
  C. The execution tree can be used with the execution log to filter and get specific information about events
  D. Multiple short bursts of Apex events should be analyzed since they can add up to a significant amount of time
  A. Log lines in the execution log panel can be analyzed for details about specific events
  D. Multiple short bursts of Apex events should be analyzed since they can add up to a significant amount of time

• Question 84:

  What is a benefit of JavaScript remoting over Visualforce Remote Objects?

  A. Supports complex server-side application logic
  B. Does not require any JavaScript code
  C. Does not require any Apex code
  D. Allows for specified re-render targets
  A. Supports complex server-side application logic

  ---

  Explanation

  Visualforce provides two primary ways to perform AJAX-style operations: JavaScript Remoting and Remote Objects. The primary benefit of JavaScript Remoting (Option A) is its ability to execute complex server- side logic .

  JavaScript Remoting works by calling an Apex method annotated with @RemoteAction. Because this is a standard Apex method, it can perform advanced calculations, complex SOQL queries with multi-object joins, DML operations across various objects, and even call out to external web services.

  In contrast, Remote Objects are purely declarative. They allow you to perform basic CRUD operations (Create, Read, Update, Delete) on a single object directly from JavaScript without writing any Apex. While Remote Objects are easier to set up for simple data entry, they cannot handle "business logic" (like calculating a discount based on customer history) during the data retrieval process.

  Option B and C describe Remote Objects, not Remoting. Option D is a feature of standard Visualforce tags like <apex:commandButton>, but not a specific differentiator for Remoting. Therefore, when your application needs "brains" on the server, JavaScript Remoting is the superior choice.

• Question 85:

  A developer has generated Apex code from a WSDL for an external web service. The web service requires Basic authentication.

  What code should the developer use to authenticate?

  A. Http.setHeader('Authorization', 'Basic QthZGprjpchVulHNchFtZQ')
  B. stub.inputHttpHeaders_x.put('Authorization', 'Basic QthZGprjpchVulHNchFtZQ')
  C. Http.setAuthentication('Basic QthZGprjpchVulHNchFtZQ')
  D. stub.authentication.put('Authorization', 'Basic QthZGprjpchVulHNchFtZQ')
  B. stub.inputHttpHeaders_x.put('Authorization', 'Basic QthZGprjpchVulHNchFtZQ')

• Question 86:

  How should a developer verify that a specific Account record is being tested in a test class for a Visualforce controller?

  A. Insert the Account in the test class, instantiate the page reference, then use ApexPages.currentPage().getParameters().put() to set the Account ID.
  B. Instantiate the page reference, insert the Account in the test class, then use seeAllData=true to view the Account.
  C. Insert the Account into Salesforce, then use System.setParentRecordId().get() to set the Account ID.
  D. Instantiate the page reference, insert the Account in the test class, then use System.setParentRecordId().get() to set the Account ID.
  A. Insert the Account in the test class, instantiate the page reference, then use ApexPages.currentPage().getParameters().put() to set the Account ID.

  ---

  Explanation

  When testing a Visualforce controller--especially one that uses a StandardController or relies on URL parameters (like ?id=001...)--the test class must simulate the browser environment.

  The correct process (Option A) involves three steps:

  Data Setup: Create and insert a test Account record. This generates a valid Salesforce ID.

  Page Context: Instantiate the PageReference for the Visualforce page being tested.

  Parameter Injection: Use Test.setCurrentPage(pageRef) and then access the parameters map via ApexPages.currentPage().getParameters().put('id', account.Id).

  This simulates the user navigating to the page with a specific record ID in the query string. When the controller's constructor or action methods run during the test, they will be able to retrieve this ID using ApexPages.currentPage ().getParameters().get('id'), allowing the logic to operate on the intended record. Options C and D use non-existent methods (setParentRecordId). Option B incorrectly suggests using seeAllData=true, which should be avoided in favor of creating isolated test data.

• Question 87:

  What are three benefits of using declarative customizations over code? (Choose Three)

  A. Declarative customizations generally require less maintenance.
  B. Declarative customizations do not require user testing.
  C. Declarative customizations cannot generate run time errors.
  D. Declarative customizations will automatically update with each Salesforce release.
  E. Declarative customizations are not subject to governor limits.
  B. Declarative customizations do not require user testing.
  D. Declarative customizations will automatically update with each Salesforce release.
  E. Declarative customizations are not subject to governor limits.

• Question 88:

  Universal Containers analyzes a Lightning web component and its Apex controller. Based on the code snippets, what change should be made to display the contacts' mailing addresses in the Lightning web component?

  Apex controller class:

  Java

  public with sharing class AccountContactsController {

  @AuraEnabled

  public static List<Contact> getAccountContacts(String accountId) {

  return [SELECT Id, Name, Email, Phone FROM Contact WHERE AccountId = :accountId];

  }

  }

  A. Add a new method in the Apex controller class to retrieve the mailing addresses separately.
  B. Modify the SOQL query in the getAccountContacts method to include the MailingAddress field.
  C. Extend the lightning-datatable component to include a column for the MailingAddress field.
  D. Modify the SOQL query in the getAccountContacts method to include the MailingAddress field and update the columns attribute in the javascript file to add Mailing address fields.
  D. Modify the SOQL query in the getAccountContacts method to include the MailingAddress field and update the columns attribute in the javascript file to add Mailing address fields.

  ---

  Explanation

  To display new data in a lightning-datatable, changes are required at both the Data Retrieval (Apex) layer and the UI Definition (JavaScript) layer. First, the SOQL query in the Apex controller must be updated to include the address fields. While MailingAddress is a compound field in Salesforce, in a SOQL query intended for a datatable, it is often best to retrieve the individual components (e.g., MailingStreet, MailingCity, MailingState).

  Second, the JavaScript controller for the LWC must be updated. The columns array in the JS file defines which data properties the lightning-datatable looks for. Even if the Apex method returns the address data, the datatable will not render it unless there is a corresponding column definition with the correct fieldName property.

  Option D correctly identifies this two-step process. Option B is incomplete because the UI wouldn't know to show the new data. Option C is incorrect because you don't "extend" the component to add columns; you simply pass a configuration array. Option A is inefficient as it creates extra server round-trips for data that should be fetched in a single query. By aligning the SOQL fields with the datatable column definitions, the mailing address can be displayed seamlessly.

• Question 89:

  Universal Containers (UC) has custom Order and Order Line objects that represent orders placed by its customers.

  A developer has a new requirement that UC's external enterprise resource planning (ERP) system must be able to integrate with Salesforce to create orders for existing customers in Salesforce whenever an order is placed in the ERP system.

  What should the developer use to create the orders in Salesforce7

  A. Connect API
  B. Change Data Capture API
  C. SObject Tree API
  D. Event Monitoring API
  A. Connect API

• Question 90:

  As part of a custom interface, a developer team creates various new Lightning web components. Each of the components handles errors using toast messages. During acceptance testing, users complain about the long chain of toast messages that display when errors occur loading the components.

  Which two techniques should the developer implement to improve the user experience? (Choose two)

  A. Use a Lightning web component to aggregate and display all errors.
  B. Use the window.alert() method to display the error messages.
  C. Use a <template> tag to display in-place error messages.
  D. Use public properties on each component to display the error messages.
  A. Use a Lightning web component to aggregate and display all errors.
  C. Use a <template> tag to display in-place error messages.

  ---

  Explanation

  When multiple components on a single page all fail simultaneously (for example, due to a shared service failure), individual toast messages stack up, creating a poor user experience. To resolve this, developers should shift away from "ephemeral" notifications like toasts toward more structured error handling.

  Option A involves creating a dedicated error-handling component. This component can act as a listener or a central repository for errors across the page. Instead of each component firing its own toast, they can communicate their error state to this central component, which aggregates the messages into a single, clean display. This reduces visual clutter and allows the user to read all errors in one place.

  Option C refers to "in-place" error handling. Using conditional rendering (the lwc:if or template if:true directives), a component can hide its normal UI and display an error message exactly where the component which specific part of the page failed would have been. This provides immediate context to the user about without interrupting the overall flow with pop-ups.

  Option B (window.alert) is considered a legacy practice that blocks the browser thread and is generally avoided in modern web development.

  Option D (public properties) is a mechanism for component communication but doesn't solve the display problem itself. Combining A and C provides a modern, professional, and less intrusive error-handling strategy.