Salesforce PDI Online Practice Questions and Exam Preparation

Salesforce PDI Online Questions & Answers

• Question 161:

  Which annotation should a developer use on an Apex method to make it available to be wired to a property in a Lightning web component?

  A. @AuraEnabled(cacneable=true)
  B. @RemoteAction (cacheable-true)
  C. @RemoteAction
  D. @AuraEnabled
  A. @AuraEnabled(cacneable=true)

  ---

  Explanation

  The @AuraEnabled(cacheable=true) annotation makes an Apex method available to Lightning Web Components and allows it to be wired to a property while enabling client-side caching for improved performance.

• Question 162:

  A developer is tasked with building a custom Lightning web component to collect Contact information. The form will be shared among many different types of users in the org. There are security requirements that only certain fields should be edited and viewed by certain groups of users.

  What should the developer use in their Lightning Web Component to support the security requirements?

  A. aura-input-failed
  B. force-input-failed
  C. ui-input-failed
  D. lightning-input-failed
  D. lightning-input-failed

  ---

  Explanation

  When building a Lightning Web Component (LWC) to collect and manage data, developers must ensure compliance with Salesforce's security model, including field-level security (FLS) and object-level security (OLS). To meet the requirement of respecting security controls, lightning-input-field is the correct choice.

  Why lightning-input-field?

  Field-Level Security (FLS):lightning-input-field respects the user's field-level security settings. This means users can only view or edit fields that they have permissions for, ensuring compliance with the organization's security model.

  Object-Level Security (OLS):It respects object-level security, ensuring users cannot access objects they are restricted from accessing.

  Simplified Development:It is part of the Lightning Data Service (LDS), which eliminates the need to write custom Apex or SOQL queries for CRUD operations, reducing the potential for security gaps.

  Dynamic Rendering:Since the component dynamically renders fields based on the user's permissions, developers can share the component across various user groups without additional customization.

  Declarative Syntax:lightning-input-field simplifies form creation in LWC by using declarative syntax to bind to record fields directly.

  Example Code Implementation:

  

  References:

  LWC Documentation for lightning-input-field Field-Level Security and Object-Level Security Best Practices for Lightning Data Service

  By using lightning-input-field, the developer ensures adherence to Salesforce's security standards while providing a reusable and secure solution for capturing and displaying Contact information.

• Question 163:

  A developer created a trigger on the Account object and wants to test if the trigger is properly bulkified. The developer team decided that the trigger should be tested with 200 account records with unique names.

  What two things should be done to create the test data within the unit test with the least amount of code? Choose 2 answers

  A. Use the @isTest (seeAllData=true) annotation in the test class.
  B. Use the @isTest (isParallel=true) annotation in the test class.
  C. Create a static resource containing test data.
  D. Use Test, loadData to populate data in your test methods.
  C. Create a static resource containing test data.
  D. Use Test, loadData to populate data in your test methods.

  ---

  Explanation

  Why Use Static Resources and Test.loadData ?

  C: Static resources allow you to define reusable test data (e.g., in a CSV file).

  D: Test.loadData simplifies loading bulk test data into test classes from static resources.

  Why Not Other Options?

  A: Using @isTest(seeAllData=true) violates test isolation principles and is discouraged.

  B: @isTest(isParallel=true) is used for parallel execution, not for creating test data.

  Test.loadData: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode /apex_testing_tools_load_data.htm

• Question 164:

  What can be used to override the Account's standard Edit button for Lightning Experience?

  A. Lightning action
  B. Lightning page
  C. Lightning component
  D. Lightning flow
  A. Lightning action

  ---

  Explanation

  To override the Account's standard Edit button in Lightning Experience, a Lightning action can be created and associated with the object. This action can include custom logic or a Lightning component.

• Question 165:

  What is an example of a polymorphic lookup field in Salesforce?

  A. The Parentid field on the standard Account object
  B. A custom field, Link__c, on the standard Contact object that looks up to an Account or a Campaign
  C. The Whatld field on the standard Event object
  D. The LeadId and Contactid fields on the standard Campaign Member object
  C. The Whatld field on the standard Event object

  ---

  Explanation

  Polymorphic Lookup Fields:

  These fields can reference multiple object types.

  Example: The WhatId field on Event can reference any object that is related to the Event, such as Account or Opportunity.

  Why Not Other Options?

  A: ParentId on Account is not polymorphic; it only points to other Accounts.

  B: Custom fields cannot be polymorphic.

  D: LeadId and ContactId are specific fields, not polymorphic.

  Polymorphic Lookups: https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta /object_reference/field_types.htm

• Question 166:

  Universal Containers (UC) processes orders in Salesforce in a custom object, Order__c. They also allow sales reps to upload CSV files with thousands of orders at a time.

  A developer is tasked with integrating orders placed in Salesforce with UC's enterprise resource planning (ERP) system.

  After the status for an Order__c is first set to 'Placed', the order information must be sent to a REST endpoint in the ERP system that can process one order at a time.

  What should the developer implement to accomplish this?

  A. Callout from a Queueable class called from a trigger
  B. Callout from a Batchable class called from a scheduled job
  C. Flow with a callout from an invocable method
  D. Callout from an @future method called from a trigger
  A. Callout from a Queueable class called from a trigger

  ---

  Explanation

  Why Queueable Class?

  Queueable Apex supports callouts and allows chaining to process one record at a time efficiently.

  The trigger detects when the Order__c status changes to "Placed" and enqueues the Queueable class to perform the callout.

  Why Not Other Options?

  B. Batchable class: Batch jobs are ideal for bulk processing but not suited for single REST callouts.

  C. Flow with invocable method: Flows are less efficient and limited in handling callouts for large- scale operations.

  D. @future method: While it supports asynchronous callouts, it does not allow chaining, making Queueable more suitable.

  Queueable Apex: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_queueing_jobs.htm

• Question 167:

  When importing and exporting data into Salesforce, which two statements are true? Choose 2 answers

  A. Bulk API can be used to bypass the storage limits when importing large data volumes in development environments.
  B. Data import wizard is an application that is installed on your computer
  C. Bulk APL can be used to import large data volumes in development environments without bypassing the storage limits.
  D. Developer and Developer Pro sandboxes have different storage limits.
  C. Bulk APL can be used to import large data volumes in development environments without bypassing the storage limits.
  D. Developer and Developer Pro sandboxes have different storage limits.

  ---

  Explanation

  C: The Bulk API is designed for importing or exporting large volumes of data and works efficiently in development environments, but it respects storage limits.

  D: Developer and Developer Pro sandboxes have different storage limits. Developer Pro has a larger storage limit compared to a Developer sandbox.

  Why not other options?

  A: Bulk API does not bypass storage limits.

  B: The Data Import Wizard is a web-based tool, not an application installed on your computer.

  References:

  Salesforce Data Import and Export Salesforce Bulk API

• Question 168:

  Which code displays the contents of a Visualforce page as a PDF?

  C

  ---

  Explanation

  Rendering as PDF:

  The renderAs="pdf" attribute in the tag renders the page content as a PDF.

  Why Not Other Options?

  A and B: contentType is not used to render PDFs.

  D: Incorrect syntax.

  Visualforce PDF Rendering: https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages /pages_output_pdf.htm

• Question 169:

  What should be used to create scratch orgs?

  A. Salesforce CLI
  B. Sandbox refresh
  C. Developer Console
  D. Workbench
  A. Salesforce CLI

  ---

  Explanation

  Scratch orgs are created using the Salesforce CLI (sfdx force:org:create) as part of Salesforce DX. It is specifically designed for development and testing purposes.

  Why not other options?

  B: Sandbox refresh is used for creating sandboxes, not scratch orgs.

  C: Developer Console is used for debugging and code development but cannot create scratch orgs.

  D: Workbench is a tool for API testing and data manipulation, not for scratch org creation.

  References: Salesforce CLI and Scratch Orgs

• Question 170:

  A developer creates a batch Apex job to update a large number of records, and receives reports of the job timing out and not completing.

  What is the first step towards troubleshooting the issue?

  A. Check the asynchronous job monitoring page to view the job status and logs.
  B. Check the debug logs for the batch job.
  C. Disable the batch job and recreate it with a smaller number of records.
  D. Decrease the batch size to reduce the load on the system.
  A. Check the asynchronous job monitoring page to view the job status and logs.

  ---

  Explanation

  When troubleshooting batch Apex jobs:

  Asynchronous Job Monitoring:

  Navigate to Setup > Apex Jobs to view the status of the batch job.

  Provides information such as success, errors, and total execution time.

  This step is crucial to diagnose whether the issue is with system limits, batch size, or specific records.

  Debug Logs:

  After identifying the issue in the job monitoring page, use debug logs to pinpoint specific errors or bottlenecks.

  B. Check the debug logs for the batch job: Debug logs are a secondary step after checking the job status.

  C. Disable and recreate with fewer records: Premature without investigating the root cause.

  D. Decrease the batch size: Adjusting batch size is a solution but only after identifying the cause of the timeout.

  Asynchronous Job Monitoring: https://help.salesforce.com/s/articleView?id=000331217andtype=1

  Debugging Apex: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode /apex_debugging.htm