QUESTION: 9

<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>

Refer to the component code above. The information displays as expected (in three rows) on a mobile device. However, the information is not displaying as desired (in a single row) on a desktop or tablet.
Which option has the correct component changes to display correctly on desktops and tablets?

<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>
<lightning:layout multipleRows="true">
<lightning:layoutItem size="12" largeDeviceSize="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 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>
<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>

Answer(s): C

Reveal Solution Next Question

QUESTION: 10

A company's support process dictates that any time a Case is closed with a Status of 'Could not fix', an Engineering Review custom object record should be created and populated with information from the Case, the Contact, and any of the Products associated with the Case.
What is the correct way to automate this using an Apex trigger?

An after update trigger that creates the Engineering Review record and inserts it
A before update trigger that creates the Engineering Review record and inserts it
An after upsert trigger that creates the Engineering Review record and inserts it
A before upsert trigger that creates the Engineering Review record and inserts it

Answer(s): A

Reveal Solution Next Question

QUESTION: 11

A company processes Orders within their Salesforce instance.
When an Order’s status changes to 'Paid' it must notify the company’s order management system (OMS). The OMS exposes SOAP web service endpoints to listen for when to retrieve the data from Salesforce.
What is the optimal method to implement this?