Salesforce PDII Online Practice Questions and Exam Preparation

Salesforce PDII Online Questions & Answers

• Question 261:

  The progress of an apex job queued is using the System.enqueueJob method and needs to be monitored. Which options are valid? (Choose two.)

  A. Use the Apex Jobs page in setup
  B. Query the Queueable Apex record
  C. Query the AsyncApexJob record
  D. Use the Scheduled Jobs page in setup
  A. Use the Apex Jobs page in setup
  C. Query the AsyncApexJob record

• Question 262:

  Consider the above trigger intended to assign the Account to the manager of the Account''s region.

  

  Which two changes should a developer make in this trigger to adhere to best practices? (Choose Two)

  A. Use a Map accountMap instead of List accountList.
  B. Use a Map to cache the results of the Region__c query by Id.
  C. Move the Region__c query to outside the loop.
  D. Remove the last line updating accountList as it is not needed.
  C. Move the Region__c query to outside the loop.
  D. Remove the last line updating accountList as it is not needed.

  ---

  Explanation

  The provided trigger contains two major violations of Salesforce Apex best practices.

  SOQL inside a Loop (Option C): The query for Region__c is located inside the for loop. If 200 accounts are updated at once, the trigger will attempt to run 200 queries, immediately hitting the governor limit of 100 SOQL queries per t35ransaction. To fix this, the developer must "bulkify" the trigger by collecting all the Region_Name__c values into a Set, performing a single query outside the loop, and storing the results in a Map for quick access.

  Redundant DML in a Before Trigger (Option D): This is a before insert and before update trigger. In the "before" context, changes made to Trigger.new records are automatically committed to the database when the trigger finishes. Adding an explicit update accountList; is not only unnecessary but will cause the trigger to re-fire (recursion), leading to performance issues and potential "Maximum stack depth" errors.

  By removing the redundant DML and moving the query outside the loop, the trigger becomes efficient, scalable, and follows the platform's execution model correctly.

• Question 263:

  A company has a Request__c object that has a lookup to the Opportunity object and a custom field, Status__c, with values of Open, Closed, and Invalid. An Opportunity should not be allowed to be deleted if there are any Request__c records related to it that have a Status__c value of Open or Closed.

  What is the optimal way to enforce the requirement to prevent deletion?

  A. A Process on Request__c
  B. A Process on Opportunity
  C. An Apex Trigger on Opportunity
  D. An Apex Trigger on Request__c
  C. An Apex Trigger on Opportunity

• Question 264:

  What is the transaction limit for the number of records per DML statement?

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

• Question 265:

  How should a developer reference a third-party JavaScript library from a Lightning component?

  A. From an asset file
  B. From a document
  C. From a static resource
  D. From a third-party URL
  C. From a static resource

• Question 266:

  A developer needs to design a custom object that will be integrated into a back-end system. What should the developer do to ensure good data quality and to ensure that data imports, integrations, and searches perform well? (Choose two.)

  A. Configure a custom field as unique
  B. Configure a custom field as indexed
  C. Configure a custom field as external ID
  D. Configure a custom field as Salesforce ID
  A. Configure a custom field as unique
  C. Configure a custom field as external ID

• Question 267:

  A developer has created a Visualforce page that uses a third-party JavaScript framework. The developer has decided to supply data to the JavaScript functions using JavaScript Remoting for Apex Controllers.

  What is the correct syntax to declare a remote method in Apex? (Choose two.)

  A. @RemoteAction global static String getTable()
  B. @RemoteAction global String getTable()
  C. @RemoteAction public static String getTable()
  D. @RemoteObject global static String getTable()
  A. @RemoteAction global static String getTable()
  C. @RemoteAction public static String getTable()

• Question 268:

  Which statement is true regarding savepoints?

  A. Savepoints are not limited by DML statement governor limits
  B. You can roll back to any savepoint variable created In any order
  C. Static variables are not reverted during a rollback.
  D. Reference to savepoints can cross trigger invocations.
  C. Static variables are not reverted during a rollback.

  ---

  Explanation

  In Salesforce Apex, a Database.Savepoint allows a developer to define a point in a transaction that can be returned to if an error occurs, effectively undoing database changes. However, it is critical to understand what is--and is not--affected by a rollback. According to the platform specifications, while database records (DML operations) are reverted to their state at the time the savepoint was set, static variables are not reverted (Option C) . Static variables persist across the entire transaction regardless of rollbacks, which is why they are commonly used as "recursion guards" to track if a trigger has already fired.

  Other options are incorrect due to the strict "stack" nature of savepoints. Savepoints must be rolled back in reverse chronological order; rolling back to an earlier savepoint invalidates any savepoints created after it (Option B). Furthermore, a savepoint variable is only valid within the specific execution context in which it was created. You cannot pass a savepoint reference across different trigger invocations or asynchronous boundaries (Option D). Finally, while the rollback itself isn't a DML statement, the operations performed between setting a savepoint and rolling back still count toward DML and CPU governor limits (Option A). Understanding that memory state (static variables) remains unchanged during a database rollback is essential for debugging complex transactional logic.

• Question 269:

  A developer needs to send Account records to an external system for backup purposes. The process must take a snapshot of Accounts as they are saved and then make a callout to a RESTful web service. The web service can only receive, at most, one record per call.

  Which feature should be used to implement these requirements?

  A. Implement platform events.
  B. Create a future method.
  C. Implement the Queueable interface.
  D. Expose an Apex class as a web service.
  D. Expose an Apex class as a web service.

  ---

  Explanation

  This requirement involves two specific constraints: performing a callout after a database change (DML) and handling high-volume processing where the external service only accepts one record at a time. In Salesforce, you cannot perform a callout in the same transaction after a DML operation; you must use asynchronous processing.

  The Queueable interface is the superior choice here over @future methods. Queueable Apex allows for chaining jobs. Since the external web service only accepts one record per call, a developer can write a Queueable class that processes the first record, makes the callout, and then checks if there are remaining records. If more records exist, the class can enqueue a new instance of itself to process the next record. This creates a controlled, sequential execution path that respects the external system's limits.

  While @future methods can perform callouts, they cannot be chained and have no built-in way to handle a sequential one-by-one requirement for an unknown number of records efficiently. Platform events (Option A) are used for event-driven architectures but would still require an asynchronous consumer to handle the callout limits. Exposing a web service (Option D) is for receiving data, not sending it. Therefore, the Queueable interface provides the necessary flexibility and transaction control to manage the snapshot and individual callout requirements effectively.

• Question 270:

  Which of the following exceptions cannot be caught and will force an error? (Choose three.)

  A. LimitException
  B. AssertException
  C. SObjectExceptions
  D. DMLException
  E. License exceptions
  F. ListException
  A. LimitException
  B. AssertException
  E. License exceptions

  ---

  Explanation

  SObjectException occurs when accessing a field not queried, or you try to change a field during the wrong dml statement (i.e. an edit-only field being set on insert) Custom exceptions must extend the "Exception" class