Exactprep PDI Questions

 A lookup field creates a relationship that links one object to another object. The relationship field allows users to click a lookup icon to select a value from a popup list. The other object is the source of the values in the list1. In this case, the developer should add a lookup field on the Account object to the Global Address object, so that multiple Accounts can share the same Global Address as their default pickup address. This way, the Global Address object can store the common address information for different Accounts, and the Account object can reference the Global Address object via the lookup field. A master-detail field creates a parent-child relationship between two objects, where the master object controls certain behaviors of the detail object. The detail object inherits the sharing and security settings of its master object2. In this case, a master-detail field is not suitable, because the Global Address object should not be dependent on the Account object, or vice versa. The Global Address object should be able to exist independently of the Account object, and the Account object should be able to have multiple Global Address records associated with it. References:

• Object Relationships Overview | Salesforce Help
• Relationships Among Objects | Salesforce Help

Flow Builder is a powerful tool that lets you automate business processes by building flows. Flows are applications that can execute logic, interact with Salesforce, and guide users through screens for collecting and updating data. Flow Builder is ideal for creating guided call scripts that can branch based on user input and data values. Flow Builder can also leverage standard and custom objects, fields, and relationships to access and update data. Flow Builder does not require coding skills and can be used declaratively by admins and developers alike. References: The use of Flow Builder for creating call scripts can be referenced in Salesforce’s official documentation and learning modules, specifically under the section that covers business process automation with flows (Business Process Automation with Flows).

The approach that can be used to make a custom Lightning Web Component available in the Salesforce Classic user interface is to use the Lightning Out JavaScript library to embed the Lightning Web Component in a Visualforce page and add to the page layout. Lightning Out is a feature that allows developers to use Lightning web components and Aura components outside the Lightning Experience and Salesforce app, such as in Visualforce pages, standalone apps, or external websites. By using Lightning Out, developers can leverage the benefits of Lightning Web Components, such as performance, interoperability, and modern web standards, in the Salesforce Classic user interface. To use Lightning Out, developers need to create a Lightning dependency app, which is a special type of Aura app that acts as a bridge between the Lightning web component and the Visualforce page. Then, developers need to use the $Lightning.use() and $Lightning.createComponent() methods in the Visualforce page to load the dependency app and create an instance of the Lightning web component. Finally, developers need to add the Visualforce page to the page layout of the object where they want to display the Lightning web component. References: Use Lightning Web Components in Visualforce Pages, Lightning Out, Free Salesforce Platform Developer 1 Practice Exam (With Answers)

To effectively test a custom controller that works with a Visualforce wizard, the unit test should do the following:

• Set the current page to the first page of the wizard using Test.setCurrentPage(pageRef), where pageRef is a PageReference object that points to the page URL. This allows the test to access the page parameters and controller methods for that page1.
• Set the page parameter that the wizard expects using ApexPages.CurrentPage().getParameters().put(‘input’, ‘TestValue’), where ‘input’ is the name of the parameter and ‘TestValue’ is the value to be passed. This allows the test to simulate the user input or the initial URL parameter that the wizard uses1.
• Verify the navigation logic of the wizard by checking the URL of the next page after invoking the controller action using String nextPage = controller.save().getUrl(), where controller is an instance of the custom controller class and save() is the action method that returns a PageReference object. This allows the test to assert that the wizard redirects to the correct page based on the input and logic2.

The other options are not useful for testing the custom controller. Option A is incorrect because insert pageRef is not a valid Apex statement. Option C is incorrect because public ExtendedController(ApexPages StandardController cntrl) { } is a constructor for a controller extension, not a custom controller3. References:

• Testing Custom Controllers and Controller Extensions | Visualforce Developer Guide | Salesforce Developers
• Testing Navigation Logic | Visualforce Developer Guide | Salesforce Developers
• Build a Controller Extension | Visualforce Developer Guide | Salesforce Developers