Universal Containers recently transitioned from Classic to Lightning Experience.
One of its business processes requires certain values from the Opportunity cbject 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
To send Opportunity values via an HTTP REST callout when a user presses a custom button in Lightning Experience:
Option B: Create a custom Visualforce quick action
A Visualforce page with a custom controller can perform the callout.
The Visualforce page can be added as a quick action on the Opportunity page.
A Lightning component can perform the callout when invoked.
The component can be added to the Opportunity page as a quick action.
'You can use Visualforce to create custom quick actions.' --- Salesforce Help: Quick Actions
Option C: Create a Lightning component quick action
Why Other Options Are Incorrect:
Option A:
Remote Actions are used in Visualforce for client-side calls and are not applicable here.
Performing the callout whenever the Opportunity is updated does not meet the requirement of initiating the action via a button click.
Option D:
An after-update trigger would execute on every update, not just when the user presses a button.
Using @future methods may not execute immediately and can't be invoked directly by the user action.
Which two are phases in the Aura application event propagation framework?
Choose 2 answers
In the Aura framework, application events propagate through the component hierarchy in specific phases. The two main phases are:
Option A: Bubble
Correct Phase.
In the bubble phase, the event propagates upward from the source component to the root component.
Components can handle the event during this phase by registering an event handler with phase='bubble'.
The default phase occurs after the capture and bubble phases.
It's used for default processing that occurs unless the event is stopped during the earlier phases.
Handlers registered without specifying a phase default to this phase.
There is no 'Control' phase in the Aura event propagation framework.
Option D: Emit
Not a Phase.
'Emit' refers to the action of firing or dispatching an event.
It is not a phase in the event propagation process.
Conclusion:
The two phases in the Aura application event propagation framework are Bubble (Option A) and Default (Option C).
Understanding these phases is essential for managing event handling in Aura components.
Option C: Default
Correct Phase.
Options Not Accurate:
Option B: Control
Incorrect.
Universal Containers has developed custom Apex code and Lightning Components in a Sandbox environment. They need to deploy the code and associated configurations to the Production environment.
What is the recommended process for deploying the code and configurations to Production?
The recommended process for deploying code and configurations from a Sandbox to Production is to use a change set.
Option C: Use a change set to deploy the Apex code and Lightning Components.
Why Other Options Are Less Preferred:
Option A: The Force.com IDE has been retired and is no longer the recommended tool.
Option B: The Ant Migration Tool is useful but requires more setup and is typically used for complex deployments or CI/CD processes.
Option D: Salesforce CLI is powerful but may not be necessary for straightforward deployments between connected orgs.
Universal Containers has a Visualforce page that displays a table of every Container___c being rented by a given Account. Recently this page is failing with a view state limit because some of the customers rent over 10,000 containers.
What should a developer change about the Visualforce page to help with the page load errors?
To address the view state limit error caused by loading over 10,000 records in a Visualforce page, the developer should implement pagination with a StandardSetController.
StandardSetController: This controller allows developers to easily paginate large sets of records in Visualforce pages.
Benefits:
Efficient Data Handling: It retrieves only a subset of records at a time, reducing the amount of data held in view state.
Built-in Pagination: Provides methods to navigate through pages of records (next, previous, etc.).
View State Limit: Visualforce pages have a view state limit of 170KB. Loading all records at once exceeds this limit.
Why Not Other Options:
A . Implement pagination with an OffsetController: There's no standard OffsetController in Visualforce. Implementing custom pagination with offsets is less efficient and can be complex.
B . Use JavaScript remoting with SOQL Offset: While JavaScript remoting can reduce view state size, using SOQL OFFSET is not efficient for large offsets (over 2,000 records).
D . Use lazy loading and a transient List variable: Lazy loading can help, but it doesn't solve the issue of handling large datasets efficiently. Transient variables reduce view state but do not manage data retrieval or pagination.
Conclusion: Implementing pagination with a StandardSetController is the recommended solution to handle large datasets efficiently in Visualforce pages and prevent view state limit errors.
Which code in a Visualforce page and/or controller might present a security vulnerability?
A)
B)
C)
D)
