Salesforce PDI Online Practice Questions and Exam Preparation

Salesforce PDI Online Questions & Answers

• Question 231:

  When the code executes, a DML exception is thrown.

  

  How should a developer modify the code to ensure exceptions are handled gracefully?

  A. Implement the upset DML statement.
  B. Implement Change Data Capture.
  C. Implement a try/catch block for the DML.
  D. Remove null items from the list of Accounts.
  C. Implement a try/catch block for the DML.

  ---

  Explanation

  Why a try/catch block is required

  In Salesforce, DML operations such as insert, update, delete, and upsert can throw exceptions due to validation rules, field constraints, or sharing restrictions.

  Using a try/catch block allows these exceptions to be caught and handled gracefully, preventing the entire transaction from failing.

  How to modify the code

  Wrap the DML statement in a try/catch block to handle DML exceptions.

  

  Why not the other options

  A. Implement the upsert DML statement

  upsert does not prevent or handle DML exceptions.

  B. Implement Change Data Capture

  Change Data Capture is unrelated to DML exception handling.

  D. Remove null items from the list of Accounts

  Data cleanup does not replace proper exception handling.

  References:

  Apex Error Handling DML Operations in Apex

• Question 232:

  While working in a sandbox, an Apex test fails when run in the Test Runner. However, executing the Apex logic in the Execute Anonymous window succeeds with no exceptions or errors.

  Why did the method fail in the sandbox test framework but succeed in the Developer Console?

  A. The test method does not use system. runAs to execute as a specific user.
  B. The test method is calling an @future method.
  C. The test method relies on existing data in the sandbox.
  D. The test method has a syntax error in the code.
  C. The test method relies on existing data in the sandbox.

  ---

  Explanation

  Test Isolation Principle:

  Apex test methods run in a sandboxed environment without access to existing org data unless seeAllData=true is used.

  The test fails if it relies on data not created within the test itself.

  Why Not Other Options?

  A: runAs simulates user context but does not affect test isolation.

  B: @future methods do not cause failures if handled correctly.

  D: Syntax errors would prevent code compilation.

  Test Data Isolation: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode /apex_testing_data.htm

• Question 233:

  A developer needs to store a value that is shared across multiple trigger executions within the same transaction. The value must reset between transactions.

  How should the variable be declared?

  A. As a non-static variable in the trigger
  B. As a static variable in a helper class
  C. As a custom setting
  D. As a custom metadata record
  B. As a static variable in a helper class

  ---

  Explanation

  Static variables in Apex are initialized once per transaction and persist for the duration of that transaction. This makes them ideal for sharing state across multiple trigger executions caused by recursive updates or complex logic. By placing the static variable in a helper class, the developer follows best practices that keep trigger logic clean and maintainable. Non-static variables are reinitialized each time the trigger executes, while custom settings and custom metadata persist beyond a single transaction and are not suitable for transaction-scoped state management.

• Question 234:

  Which two statements are true about using the @testSetup annotation in an Apex test class? Choose 2 answers

  A. Records created in the test setup method cannot be updated in individual test methods.
  B. In a test setup method, test data is inserted once and made available for all test methods In the test class.
  C. A method defined with the @testSetup annotation executes once for each test method in the test class and counts towards system limits.
  D. The @testSetup annotation is not supported when the @isTest(SeeAllData=True) annotation is used .
  B. In a test setup method, test data is inserted once and made available for all test methods In the test class.
  D. The @testSetup annotation is not supported when the @isTest(SeeAllData=True) annotation is used .

  ---

  Explanation

  B: @testSetup inserts data once and shares it across all test methods in the class, saving system resources.

  D: @isTest(SeeAllData=true) is incompatible with @testSetup due to their differing purposes for managing test data.

• Question 235:

  A developer must write an Apex method that is called from a Lightning component. The method may delete an Account stored in the accountRec variable.

  Which approach should the developer use to ensure that only users with permission to delete Account records can successfully perform the deletion?

  A. accountRec, isDeletable()
  B. Schema,sObjectType,Account, isDeletable ()
  C. accuntRec, sObjectType,isDeletable()
  D. Account,isDeleteable
  B. Schema,sObjectType,Account, isDeletable ()

  ---

  Explanation

  Option B: Using Schema.sObjectType.Account.isDeletable() checks if the current user has permission to delete records of the Account object. This approach adheres to Salesforce's security model.

  Not Suitable:

  Option A: accountRec.isDeletable() is not a valid method.

  Option C: Incorrect syntax for checking permissions.

  Option D: Account.isDeletable does not exist.

• Question 236:

  Universal Containers wants to assess the advantages of declarative development versus programmatic customization for specific use cases in its Salesforce implementation.

  What are two characteristics of declarative development over programmatic customization? Choose 2 answers

  A. Declarative development does not require Apex test classes.
  B. Declarative development has higher design limits and query limits,
  C. Declarative development can be done using the Setup menu.
  D. Declarative code logic does not require maintenance or review.
  A. Declarative development does not require Apex test classes.
  C. Declarative development can be done using the Setup menu.

  ---

  Explanation

  A: Declarative development does not require Apex test classes since it leverages built-in Salesforce features such as flows, process builders, and validation rules.

  C: Declarative development can be done using the Setup menu, which includes point-and-click tools like page layouts, workflows, and Lightning App Builder.

  Why not other options?

  B: Declarative development has strict limits (e.g., process builders and flows have governor limits that are lower than programmatic approaches like Apex).

  D: Declarative logic still requires maintenance, especially as business needs evolve.

  References: Declarative vs Programmatic Development

• Question 237:

  A credit card company needs to implement the functionality for a service agent to process damaged or stolen credit cards.

  When the customers call in, the service agent must gather many pieces of information. A developer is tasked to implement this functionality.

  What should the developer use to satisfy this requirement in the most efficient manner?

  A. Screen-based flow
  B. Approval process
  C. Apex trigger
  D. Lightning Component
  A. Screen-based flow

  ---

  Explanation

  Option A: A screen-based flow is ideal for gathering multiple pieces of information from the user interactively. It provides a declarative way to guide the service agent through the process step-by-step.

  Not Suitable:

  Option B: An approval process is for routing records for approval, not for gathering user input.

  Option C: Apex triggers are for automation, not for interactive user input.

  Option D: A Lightning Component could work but requires custom development, which is less efficient than using flows.

• Question 238:

  Cloud Kicks Fitness, an ISV Salesforce partner, is developing a managed package application.

  One application module allows users to calculate body fat using the Apex class Bodyfat and its method calculateBodyFat().

  The product owner wants to ensure this method is accessible to consumers of the application when developing customizations outside the ISV package namespace.

  Which approach should a developer take to ensure calculateBodyFat() is accessible outside the package namespace?

  A. Declare the class and method using the global access modifier.
  B. Declare the class and method using the public access modifier.
  C. Declare the class as public and use the global access modifier on the method.
  D. Declare the class as global and use the public access modifier on the method.
  A. Declare the class and method using the global access modifier.

  ---

  Explanation

  Global Access Modifier:

  When building managed packages, methods and classes that need to be accessible outside the package namespace must be declared global.

  Public restricts access to within the namespace.

  Why Not Other Options?

  B: Public limits access to within the namespace.

  C and D: Mixing public and global incorrectly doesn't meet the requirement for external accessibility.

  Managed Packages and Global Access: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta /apexcode/apex_classes_access_modifiers.htm

• Question 239:

  A developer needs to create a baseline set of data (Accounts, Contacts, Products, Assets) for an entire suite of Apex tests allowing them to test isolated requirements for various types of Salesforce cases.

  Which approach can efficiently generate the required data for each unit test?

  A. Create a mock using the HttpcalloutMock interface.
  B. Use @TestSetup with a void method.
  C. Add @IsTest (seeAllData=true) at the start of the unit test class.
  D. Create test data before Test .startTest() in the unit test.
  B. Use @TestSetup with a void method.

  ---

  Explanation

  A method annotated with @TestSetup creates test data once per test class and makes it available to all test methods in that class, which is the most efficient way to generate a shared baseline dataset for multiple Apex tests. HttpCalloutMock is only for mocking callouts, seeAllData=true breaks test isolation and is discouraged, and creating data before Test.startTest() must be repeated in each test method and is less efficient.

• Question 240:

  A company has a custom object, Sales, }_Help_Request__c, that has a Lookup relationship to Opportunity. The Seles Help Request__c has a mumber field, Number_ct_Hours__c, that represents the amount of time spent on the Sales_Help Request__C.

  A developer is tasked with creating a field, total_Hour2__c, on Opportunity that should be the sum of all of the Number_of_Hours_c values for the Sales_Help_Request__c records related to that Opportunity.

  What should the developer use to implement this?

  A. A roll-up summary field on the sales Help_Request__c object
  B. A trigger on the Opportunity object
  C. A roll-up summary field on the Opportunity object
  D. A record-triggered flow on the Sales Help Request__c object
  B. A trigger on the Opportunity object

  ---

  Explanation