Developers Changed PDI Questions

Page: 2 / 14

Question 8

Universal Containers (UC) uses a custom object called Vendor. The Vendor custom object has a master-detail relationship with the standard Account object.

Based on some internal discussions, the UC administrator tried to change the master-detail relationship to a lookup relationship, but was not able to do so.

What is a possible reason that this change was not permitted?

Options:

Some of the Vendor records have null for the Account field.

The Account object has a roll up summary field on the Vendor object.

The Account object does not allow changing a field type for a custom field.

The organization wide default for the Vendor object is Public Read/Write.

Question 9

What should a developer use to fix a Lightning web component bug in a sandbox?

Options:

Developer Console

Force.com IDE

Execute Anonymous

VS Code

Question 10

A developer is creating an app that contains multiple Lightning web components.

One of the child components is used for navigation purposes. When a user clicks a button called Next in the child component, the parent component must be alerted so it can navigate to the next page.

How should this be accomplished?

Options:

Update a property on the parent.

Call a method in the Apex controller.

Fire a notification.

Create a custom event.

Question 11

Universal Containers recently transitioned from Classic to Lightning Experience.

One of its business processes requires certain values from the Opportunity object to be sent via an HTTP REST callout to its external order management system when the user presses a custom button on the Opportunity detail page. Example values are as follows:

* Name

*Amount

* Account

Which two methods should the developer implement to fulfill the business requirement?

Choose 2 answers

Options:

Create a custom Visualforce quick action that performs the HTTP REST callout, and use a Visualforce quick action to expose the component on the Opportunity detail page.

Create a Remote Action on the Opportunity object that executes an Apex immediate action to perform the HTTP REST callout whenever the Opportunity is updated.

Create a Lightning component quick action that performs the HTTP REST callout, and use a Lightning Action to expose the component on the Opportunity detail page.

Create an after update trigger on the Opportunity object that calls a helper method using @future (Callout=true) to perform the HTTP REST callout.