A developer is building a custom component in Lightning web components (LWC) that has a grandchild component that needs to pass information to the grandparent component. What is the correct way to demonstrate the passingof a message from the grandchild component to the grandparent component?
Correct Answer: B
The correct way to demonstrate the passing of a message from the grandchild component to the grandparentcomponent in LWC is to use the PubSub library. The PubSub library is a utility that enables Lightning web components to communicate across the DOM tree without using intermediaries. The grandchild component can publish a message to a channel, and the grandparent component can subscribe to that channel and receive the message. This way, the communication is decoupled and does not depend on the component hierarchy. Option B shows the correct syntax for using the PubSub library to pass a message from the grandchild component to the grandparent component. Option A is incorrect because it uses the @api decorator to expose a property on the grandchild component, which is not a valid way to communicate with the grandparent component. Option C is incorrect becauseit uses the @wire decorator to wire a property on the grandchild component to a function on the grandparent component, which is also not a valid way to communicate with the grandparent component. Option D is incorrect because it uses the @track decorator to track a property on the grandchild component, which is not a valid way to communicate with the grandparent component. References: Communicate Across the DOM |Lightning Web Components Developer Guide, Child to grandparent communication in LWC, PubSub Library for Lightning Web Components
Question 162
Which wire adapter should a developer use to retrieve metadata about a specific picklist?
Correct Answer: C
Explanation To retrieve metadata about a specific picklist, a developer should use the getPicklistValues wire adapter. The getPicklistValues wire adapter imports data from the @salesforce/ui-api module and returns an object that contains information such as the picklist's label, value, default value, validity, and controlling field values. The getPicklistMetadataValues wire adapter does not exist. The getPicklistMetadata wire adapter does not exist either. The getPicklist wire adapter does not exist either. Salesforce References: [Lightning Web Components Developer Guide: getPicklistValues], [Lightning Web Components Developer Guide: Import User Interface API]
Question 163
A developer attempts to export data from an org by launching Data Loader, selecting a standard entity, clickingthe " Select All Fields " button and clicking the Finish button. The developer finds that the CustomField_c field they added to the entity has no values under the header in the CSV file output. What is the root cause?
Correct Answer: D
The root cause of why the CustomField__c field they added to the entity has no values under the header in the CSV file output is that the user does not have rights to the custom field. A user's access to a field is determined by their profile andpermission sets, which define their field-level security settings. Field-level security settings control whether a user can see, edit, or delete the value for a particular field on an object. If a user does not have access to a field, they will not be able to view or modify its value in any interface, including Data Loader. Data Loader is a tool that allows users to import or export data between Salesforce and CSV files. When using Data Loader to export data from an org, Data Loader will only include fields that are accessible to the user based on their field-level security settings. If a user does not have access to a field, Data Loader will not include that field in the CSV file, neither as a column header nor as a value. The developer does not have the correct JDK that is recommended by Salesforce and this is known to cause issues with exporting custom attributes is not the root cause of why CustomField__c has no values under the header in the CSV file output, as it is not related to field access or DataLoader functionality. Thedeveloper does not have access to the object's metadata is not the root cause either, as it is not related to field access or Data Loader functionality. The object's metadata defines its structure and properties, such as fields, relationships, and layouts. The field is not populated is not the root cause either, as it contradicts the fact that CustomField__c has no column header in the CSV file output. If the field was not populated but accessible to the user, Data Loader would still include CustomField__c as a column header in the CSV file, but leave its values blank. Salesforce References: Data Loader Guide: Export Data from Salesforce, [Data Loader Guide: Field Mapping], [Salesforce Help: Set Field-Level Security]
Question 164
Which event should be triggered when user facing info, warning or error messages need to be displayed on a Visualforce page?
Correct Answer: D
The event that should be triggered when user facing info, warning or error messages need to be displayed on a Visualforce page is pageMessage. This event is triggered by the displayPageMessage method of the CCRZ.util class, which is a utility class that provides various helper methods for common tasks. The event can be used to display a message on the page with a specified type, title, and text. For example, CCRZ.util.displayPageMessage('error', 'Oops!', 'Something went wrong.') will trigger the pageMessage event and display an error message on the page. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Events, Util Class
Question 165
A developer has made some changes to the products of an existing storefront, but they are unable to see the changes in the products from the store. Which action did the developer forget to take?
Correct Answer: B
The developer forgot to publish the storefront after making changes to the products. Publishing the storefront is a necessary step to make the changes visible to the store visitors. Publishing the storefront updates the site's metadata and content, and also triggers the site index and search index rebuilds. If the developer does not publish the storefront, the changes will not be reflected on the live site. The following actions are not required or relevant for the scenario: * Activate the product list. This action is only needed when creating a new product list or modifying an existing one. It does not affect the visibility of the products on the storefront. * Rebuild the search index. This action is automatically performed when the developer publishes the storefront. It is not a separate step that the developer needs to takemanually. * Publish the catalog. This action is not applicable for Salesforce B2B Commerce for Visualforce, which does not use catalogs. Catalogs are only used by Salesforce B2B Commerce for Lightning Experience. References: Finalize and Publish Your Storefront Customize the D2C Store Template Configure Public Pages for a Storefront
