Online Access Free PDI Exam Questions

No.# C is correct, you need to define the External ID field at the end of the upsert.
"upsert orders Order_Number__c;"

No.# C is correct. Ignore the typos.
There is no "IN CompanyName FIELDS".
You can use these values in SOSL after IN: "ALL FIELDS, NAME FIELDS, EMAIL FIELDS, PHONE FIELDS, SIDEBAR FIELDS, etc."

No.# Answer: A, B and E

E. Test.setCurrentPage(pageRef): This sets which Visualforce page the test is running on. It is the starting point for a wizard test, because ApexPages.currentPage() doesn’t exist until you set one.
B. ApexPages.currentPage().getParameters().put('input', 'TestValue'): The wizard reads a parameter from the initial URL, so the test has to supply that parameter. (The option’s text is garbled by OCR, and I’m reading it as this statement.)
A. String nextPage = controller.save().getUrl(): This calls a controller action and checks the PageReference it returns. In a wizard, the next page is the thing to assert on at each step.
apex
@isTest
private class WizardControllerTest {
@isTest
static void testWizardStep() {
PageReference pageRef = Page.WizardStep1;
Test.setCurrentPage(pageRef); // E
ApexPages.currentPage().getParameters().put('input', 'TestValue'); // B

WizardController controller = new WizardController();
controller.name = 'Test'; // simulate user input

String nextPage = controller.save().getUrl(); // A
System.assert(nextPage.contains('wizardstep2'));
}
}

The other options don’t fit:

C. insert pageRef;: A PageReference isn’t an sObject, so you can’t insert it. The statement doesn’t compile.
D. public ExtendedController(ApexPages.StandardController ctrl) {}: This is a constructor declaration for a controller extension. It belongs in the controller class, not in a test, and the question is about a custom controller, not an extension....

No.# Answer: A

lightning:layout uses a 12-column grid. size="12" is the default for every screen, so each item takes a full row, which gives three rows on mobile. The device-size attributes override size from that breakpoint upward, and a value set for one breakpoint carries up to larger screens unless a larger attribute overrides it.

In option A, mediumDeviceSize="4" on all three items makes each one 4 of 12 columns on tablets and up. Large screens inherit it. The three items together fill 12 columns, so they sit in a single row on tablets and desktops, and stay at 12 columns (three rows) on mobile.

xml
<lightning:layout multipleRows="true">
<lightning:layoutItem size="12" mediumDeviceSize="4">{!v.account.Name}</lightning:layoutItem>
<lightning:layoutItem size="12" mediumDeviceSize="4">{!v.account.AccountNumber}</lightning:layoutItem>
<lightning:layoutItem size="12" mediumDeviceSize="4">{!v.account.Industry}</lightning:layoutItem>
</lightning:layout>

The other options fail:

B: Only the first item has mediumDeviceSize. The other two set largeDeviceSize only, so on tablets they stay at 12 columns and wrap onto new rows.
C: mediumDeviceSize="6" fits only two items per row, so tablets and desktops show two rows, with the third item on its own.
D: On desktops, largeDeviceSize="4" gives a single row. On tablets, it uses mediumDeviceSize="6", so you get two rows. The requirement covers tablets as well....

No.# Answer: A. <apex:page standardController="Notice__c" extensions="myControllerExtension">

This is the same question you asked last Tuesday, with the same options. The page uses the custom object’s standard controller (standardController) and attaches the extension class with extensions. For a custom object, the standard controller name is its API name, ending in __c. Your option shows Notice_c, which is an OCR slip for Notice__c.

xml
<apex:page standardController="Notice__c" extensions="myControllerExtension">
<apex:form>
<apex:inputField value="{!Notice__c.Name}"/>
<apex:commandButton action="{!save}" value="Save"/>
</apex:form>
</apex:page>

As we discussed after that question, “standard” in standardController means the controller is provided by Salesforce, not that the object has to be a standard object. Every custom object gets one automatically.

The other options don’t fit:

B. controllers="...": There is no controllers attribute on <apex:page>.
C. apex:pege=Notice extends=...: This isn’t valid Visualforce syntax. The attribute is extensions, not extends, and attributes use name="value" pairs.
D. controller="Notice__c": The controller attribute names a custom Apex controller class. Notice__c is an object, so it needs standardController....

No.# Answer: A, B and E

The steps are the same ones used for any static resource in an LWC:

B. Upload the SVG as a static resource: In Setup, go to Static Resources and upload the file.
A. Import the static resource and provide a JavaScript property for it: The component’s JavaScript imports it from @salesforce/resourceUrl and exposes it as a property.
E. Reference the property in the HTML template: The template uses the property, for example as an image src.
javascript
import { LightningElement } from 'lwc';
import MY_ICON from '@salesforce/resourceUrl/companyIcon';

export default class IconDisplay extends LightningElement {
iconUrl = MY_ICON; // property exposed to the template
}
html
<template>
<img src={iconUrl} alt="Company icon" />
</template>

The other options don’t fit:

C. Reference the import in the HTML template: A template can’t reference the import directly. It can only bind to a property defined on the component class, which is why A comes before E.
D. Import the SVG as a content asset file: Content assets can be imported with @salesforce/contentAssetUrl, so this is a real way to use files in an LWC. It is a different method from the static resource steps in A, B and E, and the question asks for the three steps of one workflow....

No.# Answer: D. An invocable method

This is the same question you asked on Tuesday, with the same options. A screen flow can call Apex through an Apex action, which runs a method annotated with @InvocableMethod. The method makes the callout to the external order management system in real time and returns the order numbers and dates. The flow then shows them on a screen, for example in a data table or a choice list.

apex
public class GetExternalOrders {
public class Request { @InvocableVariable public String customerId; }
public class OrderInfo {
@InvocableVariable public String orderNumber;
@InvocableVariable public Date orderDate;
}

@InvocableMethod(label='Get external orders' callout=true)
public static List<List<OrderInfo>> getOrders(List<Request> requests) {
// HTTP callout to the order system, then build and return the results
}
}

The callout=true setting is needed so the flow can make the callout.

The other options don’t fit:

A. Outbound message: It pushes data from Salesforce to an external system when a workflow rule fires. It can’t retrieve data on demand.
B. Apex REST class: It exposes Salesforce as a web service that external systems call into. It is for inbound requests, not for calling out to another system.
C. Apex controller: It backs Visualforce pages and Lightning components. A flow can’t call it directly, and only methods exposed as invocable actions are available in Flow....

No.# Answer: A. Enforced unit testing and code coverage best practices

Your question is cut off after “developing applications”. I’m assuming it continues “in a multi-tenant environment”, which is the standard version of this question.

Salesforce is multitenant, so many customers share the same infrastructure. To protect everyone, the platform enforces rules on developers:

Governor limits force efficient, bulkified code.
Test coverage requirements (75% overall, plus some coverage on every trigger) must be met before code can be deployed to production.

Together these push developers toward good practices, which is the benefit.

The other options are wrong:

B. Access to predefined computing resources: Resources are shared and limited, not predefined for each developer.
C. Preconfigured storage for big data: Salesforce isn’t a big-data store, and storage is limited by edition and license.
D. Unlimited processing power and memory: The opposite is true. Governor limits cap CPU time, heap size, queries and DML, because the resources are shared....

No.# Answer: C. Lightning component

In Lightning Experience, you override a standard button in Setup (Object Manager > Account > Buttons, Links, and Actions > Edit). One of the override options is a Lightning component. For Aura, the component implements lightning:actionOverride, and an LWC can also be set up as an action override. This is the same override setup as in the earlier Contact Edit button question.

The other options don’t fit:

A. Lightning action: Actions are buttons you add to a page layout, such as quick actions. They aren’t an override target for a standard button.
B. Lightning page: A Lightning page (FlexiPage) controls how a record page or tab is laid out. It can’t replace what the Edit button does.
D. Lightning flow: This is the closest rival. Some releases let you assign a flow as an override for certain standard actions, but I’m not certain it applies to Edit in your org’s release. The expected exam answer is the Lightning component.

No.# Answer: C and D (Apex Jobs and Apex Flex Queue)

C. Apex Jobs: In Setup, this page lists asynchronous Apex jobs, including batch jobs and future methods, with their status (Queued, Processing, Completed, Failed), submission time and any error details.
D. Apex Flex Queue: Batch jobs that are submitted but waiting for a free slot sit here in the Holding status. You can see them and reorder them.

The two pages complement each other. Apex Jobs covers both kinds of async work, while the Flex Queue shows batch jobs that haven’t started yet. Future methods never appear in the Flex Queue.

The other options:

A. Paused Flow Interviews component: It shows flow interviews that were paused, such as flows waiting on an event. It has nothing to do with batch or future jobs.
B. Developer Console: This is the closest rival, since you can query AsyncApexJob in its Query Editor and get the same status information. It isn’t a dedicated place for job status, though, and the expected answer is the two Setup pages....

No.# BS question.

C for Fast Field, B for standard record triggered flow

Thanks for sending me the latest PDI exam questions.

I passed the PDI exam recently. I admire freecram, this study site considers a lot about the future of the students and help the students achieve a career of their dreams. Big thanks!

No.# For an autolaunched Flow, shouldn't you open its Flow Properties page to review test coverage before deploying it in a change set? So not B?

No.# The correct answers are not A and D?

I passed PDI exam easily. Well, I would like to recommend freecram to other candidates. Thanks for your good exam materials and good service.

PDI Dumps PDF is still valid. I took the exam this week and passed in the first attempt.

No.# Correct answer is B. Access to predefined computing resources

No.# Correct answer is B. An Apex REST class

No.# Correct answer is D. An invocable method