B2B-Commerce-Developer Exam Dumps : B2B Commerce for Developers Accredited Professional AP-202

To create an event listener on a parent component programmatically, the developer should use the following line of code:

this.template.addEventListener(‘notification’, this.handleNotification);

This line of code adds an event listener to the template element of the parent component, which is the root element that contains all the child elements. The event listener listens for an event named ‘notification’, which is a custom event that can be dispatched by any child component. The event listener invokes a method named handleNotification, which is an arrow function defined in the parent component class. The handleNotification method receives the event object as a parameter and can perform any logic based on the event data. The other lines of code are either incorrect or incomplete. Salesforce References: Lightning Web Components Developer Guide: Communicate with Events, Lightning Web Components Developer Guide: Create and Dispatch Events

 Executing dynamic SOQL inside a without sharing class with a bind variable from PageReference.getParameters(), PageReference.getCookies(), or cc_RemoteActionContext class will open up a major security hole because these sources of input are not sanitized and can be manipulated by malicious users to inject SOQL queries that bypass the sharing rules and access data that they are not supposed to see. For example, a user can modify the URL parameters or cookies to include a SOQL query that returns sensitive data from the database. To prevent this, it is recommended to use static SOQL or escape the bind variables before executing dynamic SOQL.

The format that the custom Salesforce relationship with the API name, My_Relationship_Name__r.My_Name__c is queried and transformed into by default in Salesforce B2B Commerce is myRelationshipName.myName: value. This is done to follow the JavaScript naming convention and to avoid conflicts with the standard Salesforce fields and relationships. The transformation rules are as follows:

• Remove any namespace prefix from the field name, such as ccrz__ or cloudcraze__.
• Remove any underscores from the field name and capitalize the first letter of each word after an underscore, such as MyRelationshipName and MyName.
• Lowercase the first letter of the field name, such as myRelationshipName and myName.
• Use a dot (.) to separate the relationship name and the field name, such as myRelationshipName.myName.
• Use a colon (:) to separate the field name and the field value, such as myRelationshipName.myName: value. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Query Transformation