Complete PDI Salesforce Materials

The with sharing keyword on the class declaration enforces the sharing rules that apply to the current user. This means that the user can only see and modify the records that they have access to based on the organization-wide defaults, role hierarchy, sharing rules, manual sharing, teams, and territories. The without sharing keyword, on the other hand, ignores the sharing rules and allows the user to access all records, regardless of ownership or sharing settings. This can pose a security risk and should be used with caution. The schema describe calls and the UserInfo Apex class do not directly affect the sharing rules, but rather provide information about the object and field permissions, and the user’s profile and role, respectively. These can be used to check the user’s access level, but not to enforce the sharing rules on the custom search tool. References:

• Apex Developer Guide: Using the with sharing, without sharing, and inherited sharing Keywords, pages 13-14
• Trailhead: Platform Developer I Certification Study Guide: Apex Basics and Database, unit 3

Lightning Web Components use the standard web component model, which includes the concept of Shadow DOM. Shadow DOM is a mechanism that isolates the component’s internal DOM from the rest of the page, creating a boundary that prevents the component from accessing or being affected by the elements outside of its own subtree. However, this also means that events that are fired from within the component’s shadow DOM do not propagate to the parent or ancestor components by default, unless they are configured to do so.

To configure how an event propagates, the component that dispatches the event can set two properties on the custom event object: bubbles and composed. The bubbles property determines whether the event can bubble up the containment hierarchy, which is the tree of components that contains the event source. The composed property determines whether the event can cross the shadow boundary, which is the boundary between the component’s shadow DOM and the light DOM of its parent component.

The possible values and effects of these properties are:

• bubbles: true, composed: true: The event can bubble up the containment hierarchy and cross the shadow boundary. This means that the event can be handled by any component that is an ancestor of the event source, regardless of whether it is in the same shadow DOM or not. This is the most common setting for custom events that need to communicate with other components in the page.
• bubbles: true, composed: false: The event can bubble up the containment hierarchy, but cannot cross the shadow boundary. This means that the event can be handled by any component that is an ancestor of the event source, as long as it is in the same shadow DOM. This is useful for custom events that need to communicate with other components within the same shadow tree, but not outside of it.
• bubbles: false, composed: true: The event cannot bubble up the containment hierarchy, but can cross the shadow boundary. This means that the event can be handled only by the component that dispatched the event, or by the component that contains the event source in its light DOM. This is useful for custom events that need to communicate with the direct parent component, but not with any other ancestor components.
• bubbles: false, composed: false: The event cannot bubble up the containment hierarchy, nor can it cross the shadow boundary. This means that the event can be handled only by the component that dispatched the event. This is useful for custom events that do not need to communicate with any other components, but only with the event source itself.

Therefore, the correct answer is B. bubbles: true, composed: true, as this is the only setting that enables the event to bubble up the containment hierarchy and cross the shadow boundary.

References:

• Configure Event Propagation
• Handle Events

In Salesforce, a controller and extension for a custom object on a Visualforce page can be specified using the  tag. The standardController attribute is used to associate the page with a standard or custom object, and the extensions attribute is used to specify an Apex class that extends the functionality of the standard or custom controller. The code snippet in option C, , correctly demonstrates this by associating the Visualforce page with a custom object named “Notice” and specifying an extension named “myControllerExtension”. References: You can find more information about controllers and extensions in the Visualforce Developer Guide and the [Apex Developer Guide] on Salesforce’s official website.

• Controllers, helpers, and renderers are three resources in an Aura Component that can contain JavaScript functions. They are used to implement the client-side logic and behavior of the component12.
• Controllers are the primary resource for handling user interactions and events. They define the actions that are executed on the client or sent to the server12.
• Helpers are the secondary resource for sharing common code and logic across controllers and other helpers. They can also access component attributes and call server-side actions12.
• Renderers are the optional resource for customizing the rendering lifecycle of the component. They can override the default rendering, rerendering, and unrendering methods of the component12.
• Design and style are two other resources in an Aura Component, but they do not contain JavaScript functions. They are used to define the design-time attributes and the CSS styles of the component12.

References:

• 1: Aura Components Basics
• 2: Cert Prep: Platform Developer I: User Interface