Online Access Free PDI Practice Test

Cloud Kicks Fitness, an ISV Salesforce partner, is developing a managed package application. One of the application modules allows the user to calculate body fat using the Apex class, Bodyfat, and its method, calculateBodyFat (). The product owner wants to ensure this method is accessible by the consumer of the application when developing customizations outside the ISV's package namespace.
Which approach should a developer take to ensure calculateBodyFat () is accessible outside the package namespace?

• A.Declare the class and method using the public access modifier.
• B.Declare the class as public and use the global access modifier on the method.
• C.Declare the class and method using the global access modifier.
• D.Declare the class as global and use the public access modifier on the method.

Refer to the component code requirements below:
<lightning:layout multipleRows="true">
<lightning:layoutItem size="12">{!v.account.Name}</lightning:layoutItem>
<lightning:layoutItem size="12">{!v.account.AccountNumber}</lightning:layoutItem>
<lightning:layoutItem size="12">{!v.account.Industry}</lightning:layoutItem>
</lightning:layout>
Requirements:
* For mobile devices, the information should display in three rows.
* For desktops and tablets, the information should display in a single row.
Requirement 2 is not displaying as desired.
Which option has the correct component code to meet the requirements for desktops and tablets?

• A.<lightning:layout multipleRows="true">
  <lightning:layoutItem size="12" mediumDeviceSize="6">{!v.account.Name}</lightning:layoutItem>
  <lightning:layoutItem size="12" mediumDeviceSize="6">{!v.account.AccountNumber}</lightning:
  layoutItem>
  <lightning:layoutItem size="12" mediumDeviceSize="6">{!v.account.Industry}</lightning:layoutItem>
  </lightning:layout>
• B.<lightning:layout multipleRows="true">
  <lightning:layoutItem size="12" mediumDeviceSize="6" largeDeviceSize="4">{!v.account.Name}<
  /lightning:layoutItem>
  <lightning:layoutItem size="12" mediumDeviceSize="6" largeDeviceSize="4">{!v.account.
  AccountNumber}</lightning:layoutItem>
  <lightning:layoutItem size="12" mediumDeviceSize="6" largeDeviceSize="4">{!v.account.Industry}<
  /lightning:layoutItem>
  </lightning:layout>
• C.<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>
• D.<lightning:layout multipleRows="true">
  <lightning:layoutItem size="12" mediumDeviceSize="4">{!v.account.Name}</lightning:layoutItem>
  <lightning:layoutItem size="12" largeDeviceSize="4">{!v.account.AccountNumber}</lightning:
  layoutItem>
  <lightning:layoutItem size="12" largeDeviceSize="4">{!v.account.Industry}</lightning:layoutItem>
  </lightning:layout>

Universal Containers wants to automatically assign new cases to the appropriate support representative based on the case origin. They have created a custom field on the Case object to store the support representative name.
What is the best solution to assign the case to the appropriate support representative?

• A.Use a validation rule on the Case object.
• B.Use an Assignment Flow element.
• C.Use a formula field on the Case object.
• D.Use a trigger on the Case object.

What does the Lightning Component framework provide to developers?

• A.Extended governor limits for applications
• B.Support for Classic and Lightning UIs
• C.Prebuilt components that can be reused
• D.Templates to create custom components

Which two settings must be defined In order to update a record of a junction object?
Choose 2 answers

• A.Read/Write access on the primary relationship
• B.Read/Write access on the secondary relationship
• C.Read/Write access on the junction object
• D.Read access on the primary relationship