Salesforce PDII Online Practice Questions and Exam Preparation

Salesforce PDII Online Questions & Answers

• Question 401:

  A company uses Opportunism to track sales to their customers and their org has millions of Opportunities. They want to begging to track revenue over time through a related Revenue object. As part of their initial implementation, they want to perform a one-time seeding of their data by automatically creating and populating Revenue records for Opportunities, based on complex logic. They estimate that roughly 100,000 Opportunities will have revenue records and populated.

  What is the optimal way to automate this?

  A. Use System.enqueueJob>() to Invoke a Queueable class.
  B. Use System.scheduleJob() to schedule a Database.Scheduleable class.
  C. Use Database.executeBatch() to invoke a Queueable dass.
  D. Use Database.executeBatch() to invoke a Database.Batchable class.
  D. Use Database.executeBatch() to invoke a Database.Batchable class.

  ---

  Explanation

  For high-volume data processing (such as seeding 100,000 records) involving complex logic, Batch Apex (Option D) is the standard and most robust solution. Batch Apex is designed to handle up to 50 million records by breaking the total set into smaller, manageable chunks (defaulting to 200 records per batch).

  Each batch execution gets its own set of governor limits. This is crucial for "complex logic," as it prevents the transaction from hitting CPU time or heap size limits that would occur if one tried to process all 100,000 records in a single synchronous transaction. Batch Apex also provides built-in state management and error handling (via Database.RaisesPlatformEvents or the finish method). Option A (Queueable) is better suited for smaller, chained tasks; while it can handle some volume, it is not optimized for 100,000 records in the same way the QueryLocator in Batch Apex is. Option C is a syntactical impossibility as executeBatch only accepts Batchable classes. Option B (Schedulable) is used for timing, but the actual heavy lifting for 100,000 records would still need to be handed off to a Batch class to avoid timeout errors. Therefore, Database.Batchable is the optimal tool for large-scale data seeding.

• Question 402:

  Which is a valid Apex REST Annotation? (Choose two.)

  A. @Http Patch
  B. @HttpDelete
  C. ttpUpsert
  D. @HttpAction
  A. @Http Patch
  B. @HttpDelete

• Question 403:

  A developer is working on code that requires a call to an external web service from a batch. How should the developer enable this functionality?

  A. Implement a custom System.CalloutException class
  B. Include Database.AllowCallout() in the class definition
  C. Implement an @future method for the callout, and invoke it from the batch
  D. Specify "callout=true" in the batch implementation
  B. Include Database.AllowCallout() in the class definition

• Question 404:

  What is the transaction limit on the number of callouts?

  A. 100
  B. 150
  C. 50
  D. 200
  E. There is no limit
  C. 50

• Question 405:

  A developer is building a Lightning web component that retrieves data from Salesforce and assigns it to the record property.

  

  What must be done in the component to get the data from Salesforce?

  A. Add @api(getRecord, { recordId: '$recordId' }) above record.
  B. Add @wire(getRecord, { recordId: '$recordId' }) above record.
  C. Add @api(getRecord, { recordId: '$recordId', fields: '$fields' }) above record.
  D. Add @wire(getRecord, { recordId: '$recordId', fields: '$fields' }) above record.
  D. Add @wire(getRecord, { recordId: '$recordId', fields: '$fields' }) above record.

  ---

  Explanation

  To retrieve record data in a Lightning Web Component using the Lightning Data Service (LDS), the developer must use the @wire decorator with the getRecord wire adapter .

  Option D provides the correct syntax. The @wire decorator requires the adapter name (getRecord) and a configuration object. The configuration must include the recordId and either the fields or layoutTypes to be retrieved. By using the $ prefix (e.g., '$recordId'), the developer makes the property "reactive." This means that whenever the value of recordId or fields changes, the wire service automatically re-provisions the data from Salesforce.

  Options A and C are incorrect because @api is used to expose public properties, not for wiring data. Option B is incorrect because getRecord requires a field list or layout type to know which data points to fetch from the server. Using the reactive $fields ensures that the component remains flexible and can load different field sets as defined by its parent component.

• Question 406:

  Universal Containers is using a custom Salesforce application to manage customer support cases. The support team needs to collaborate with external partners to resolve certain cases. However, they want to control the visibility and access to the cases shared with the external partners.

  Which Salesforce feature can help achieve this requirement?

  A. Apex managed sharing
  B. Sharing sets
  C. Role hierarchy
  D. Criteria-based sharing rules
  B. Sharing sets

  ---

  Explanation

  When dealing with External Users (Community/Experience Cloud users), standard sharing mechanisms like Role Hierarchies often do not apply, especially for high-volume Customer Community licenses which do not use the Role Hierarchy at all.

  Sharing Sets (Option B) are specifically designed to grant external users access to records associated with their Account or Contact. A Sharing Set allows an administrator to define a simple mapping: for example, "Grant access to Cases where the Case's Account matches the User's Account." This is the most efficient and scalable way to provide external partners visibility into records relevant to them without using complex Apex code.

  While Apex managed sharing (Option A) could technically work, it is much more complex to maintain and is only available for "Customer Community Plus" or "Partner" licenses. Criteria-based sharing rules (Option D) are typically used for internal users or broad groups, not for granular, account-specific access for individual external partners. Sharing Sets provide a high-performance, declarative solution for controlling external record visibility.

• Question 407:

  A managed package uses a list of country ISO codes and country names as reference data in many different places from within the managed package Apex code.

  What is the optimal way to store and retrieve the list?

  A. Store the information in Custom Metadata and query it with SOQL.
  B. Store the information in Custom Metadata and access it with the getAll() method.
  C. Store the information in a List Custom Setting and query it with SOQL.
  D. Store the information in a List Custom Setting and access it with the getAll() method
  D. Store the information in a List Custom Setting and access it with the getAll() method

  ---

  Explanation

  https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_customsettings.htm

• Question 408:

  A Lightning Component functions in preview mode and needs to be used inside a Lightning App Builder page, but it is not available. What change should be applied to the component?

  A. Refresh the sandbox and upgrade it to the latest API version.
  B. Delete the component, metadata, and Apex controller and recreate them.
  C. Expose it in the markup using the implements and access attributes.
  D. Look for errors in the logic in the JavaScript controller.
  C. Expose it in the markup using the implements and access attributes.

• Question 409:

  A lead developer is creating tests for a Lightning web component. The component re-renders when a property called bypassSelection changes its value.

  What should the developer use to test that the component re-renders successfully when the property changes?

  A. Window.setInterval()
  B. Window.setState()
  C. dispatchEvent (new CustomEvent(`bypassSelection'))
  D. Promise.resolve()
  A. Window.setInterval()

• Question 410:

  A developer is writing code that requires making callouts to an external web service. Which scenario necessitates that the callout be made in an @future method?

  A. The callouts will be made using the REST API.
  B. The callouts will be made in an Apex Trigger.
  C. The callout could take longer than 60 seconds to complete.
  D. Over 10 callouts will be made in a single transaction.
  B. The callouts will be made in an Apex Trigger.

  ---

  Explanation

  In Salesforce, a callout cannot be made directly from an Apex trigger (Option B) . This is a fundamental architectural restriction of the platform. Triggers execute as part of a database transaction. If a trigger were allowed to make a synchronous callout, the database transaction--along with all its associated row locks-- would remain open while waiting for a response from the external system. This could lead to severe performance bottlenecks and transaction timeouts.

  To perform a callout based on a trigger event, the developer must move the callout logic into an asynchronous context, such as a @future(callout=true) method, a Queueable class, or by publishing a Platform Event.

  Option C is incorrect because while asynchronous methods allow for higher CPU time, they do not extend the maximum individual callout timeout (120 seconds). Option A is incorrect because REST is simply a protocol and does not dictate synchronicity. Option D is incorrect because the limit for callouts in a single transaction is 100, so 10 callouts would still be permissible in a synchronous context (assuming they aren't in a trigger). Consequently, the presence of a trigger is the only factor listed that programmatically mandates an asynchronous approach.