PDI Practice Test Questions

Explanation:

- Callouts to external systems are not executed when debugging a flow because the debug mode runs in a controlled environment where external interactions are prevented.
- DML operations (such as inserts, updates, and deletes) are rolled back when debugging ends, ensuring that test runs do not affect actual data.

Explanation:

Standard list controllers are used when you need to display a list of records (like Contacts). Since the requirement is to list contacts owned by the current user, and there's no mention of custom logic, a standard list controller for the Contact object is the most efficient and appropriate choice.

It provides built-in pagination, filtering, and sorting without the need for custom Apex code. This is ideal for use cases where basic list display is enough, especially when embedding into a Lightning page.

Other options:

B. Standard controller: Used for a single record, not a list.
C. Lightning controller: This is not a standard Visualforce option—confusing terminology.
D. Custom controller: Unnecessary unless you need custom logic, which this question does not require.

Explanation:
- @AuraEnabled is required to expose an Apex method to Lightning Web Components (LWC). Without it, the method cannot be accessed from LWC.
- cacheable=true is necessary if the method is used with the @wire decorator in LWC, allowing efficient data retrieval and caching.
- The method cannot mutate the result set retrieved from the database because cacheable=true requires the method to be read-only, meaning it cannot modify data.

Explanation:
- External IDs help integrate Salesforce with external systems by allowing records to be referenced using an identifier from another system rather than the Salesforce record ID.
- External IDs are indexed, which improves query performance when searching for records using SOQL.

Explanation:

force:data:bulk:upsert (A)
Bulk upserts data from a CSV file into a Developer sandbox.
Ideal for large datasets (uses Bulk API for efficiency).
force:data:tree:import (C)
Imports hierarchical data (e.g., parent-child records) from a JSON file.
Maintains relationships between records during insertion.

Explanation:

- A Lookup relationship is the best choice when multiple Accounts need to reference a single Global Address.
- This allows many Accounts to share the same default pickup address, ensuring efficiency in shipping operations.
- A Master-Detail relationship would not be ideal because it enforces strict ownership and deletion dependencies, which are unnecessary for this use case.
- The Lookup field should be placed on the Account object, linking it to the Global Address object, so each Account can reference a shared address.

Explanation:
- When using a custom controller, validation rule errors do not automatically display like they do with standard controllers.
- To ensure validation errors appear on the Visualforce page, the developer should use Database.upsert() instead of DML operations like insert or update.
- The Database.upsert() method returns a Database.SaveResult object, which allows the developer to capture errors and display them using ApexPages.addMessages().

Explanation:
- A before-save Apex trigger is the most efficient way to enforce additional validation beyond standard validation rules.
- It allows the developer to check the email format using regular expressions or other logic before the record is committed to the database.
- If the email is invalid, the trigger can prevent the record from being saved and display an error message to the user.
trigger LeadTrigger on Lead (before insert, before update) {
for (Lead l : Trigger.new) {
if (l.Email != null && !Pattern.matches('^[A-Z0-9._%+-]+@[A-Z0-9.-]+\\.[A-Z]{2,}$',
l.Email.toUpperCase())) {
l.Email.addError('Please enter a valid email address.');
}
}
}

Explanation:

Purpose: To use a Lightning component (c:accountList) in a Visualforce page, you must declare it in a Lightning Out dependency app.
Key Requirements:
: The container for Lightning Out apps (not ).
extends="ltng:outApp": Required to enable Lightning components in Visualforce.
: Lists the components (e.g., c:accountList) to be exposed.
access="GLOBAL": Ensures the app is accessible to Visualforce.

Explanation:

- Since the order numbers and dates need to be retrieved in real time from an external system, an Apex REST class is the best approach.
- Apex REST classes allow Salesforce to make callouts to external APIs, fetching data dynamically when needed.
- The retrieved data can then be displayed in the multi-screen flow, ensuring agents see the most up-to-date information.