[Apr-2024] B2B-Commerce-Developer Dumps Full Questions - Salesforce Developer Exam Study Guide
Exam Questions and Answers for B2B-Commerce-Developer Study Guide
Salesforce B2B-Commerce-Developer Certification Exam is a highly sought-after accreditation for developers working within the B2B Commerce space. It is recognized globally and demonstrates a candidate's ability to develop and implement solutions within the Salesforce B2B Commerce platform. Salesforce Accredited B2B Commerce Developer certification is an excellent way for developers to showcase their skills and knowledge and enhance their career prospects within the Salesforce ecosystem.
Candidates for the B2B-Commerce-Developer certification exam should have experience working on B2B Commerce projects using Salesforce's platform. They should have a strong understanding of Salesforce's data model, as well as experience with Apex, Visualforce, and other Salesforce development tools. Candidates should also have experience integrating Salesforce with other systems, such as ERP systems and payment gateways.
NEW QUESTION # 93
A developer has the task to bring some historical data into an org. The data must reside in the org, but cannot be populated in standard or custom objects. The customer is fine with developers building Ul components to surface this data on a case-by-case basis.
Which option allows a developer to meet all of these requirements?
- A. Lightning Out
- B. Lightning Canvas
- C. External objects
- D. Big objects
Answer: D
Explanation:
Explanation
To bring some historical data into an org, the data must reside in the org, but cannot be populated in standard or custom objects, and the customer is fine with developers building UI components to surface this data on a case-by-case basis, the option that allows a developer to meet all of these requirements isbig objects. Big objects are a type of object that can store and manage massive amounts of data on the Salesforce platform. Big objects can store up to billions of records and are accessible through a subset of SOQL or custom user interfaces. Big objects are not subject to the same storage limits or performance issues as standard or custom objects and are suitable for storing historical or archived data that does not need to be updated frequently. Big objects can be defined using Metadata API or declaratively in Setup. Lightning Canvas is not an option that allows a developer to meet all of these requirements, as it is a framework that allows developers to integrate third-party applications into Salesforce. Lightning Canvas does not store data in the org, but rather displays data from external sources using an iframe. External objects are not an option either, as they are a type of object that map to data stored outside Salesforce. External objects do not store data in the org, but rather access data from external systems using OData services. Lightning Out is not an option either, as it is a feature that allows developers to use Lightning components outside Salesforce. Lightning Out does not store data in the org, but rather renders components on external web pages or applications. Salesforce References: Salesforce Help: Define BigObjects, Salesforce Help: Lightning Canvas Developer's Guide, Salesforce Help: External Objects, Salesforce Developer Blog: Lightning Out
NEW QUESTION # 94
Numerous flags, when set, have a direct impact on the result set provided by the Global API's. What is the default Global API DataSizing convention flag that is used by theAPI's unless otherwise specified?
- A. CCRZ.ccPAI.SZ_M
- B. CCRZ.ccPAI.SZ_L
- C. CCRZ.ccPAI.SZ_S
- D. CCRZ.ccPAI.SZ_XL
Answer: A
Explanation:
The default Global API Data-Sizing convention flag that is used by the API's unless otherwise specified is CCRZ.ccAPI.SZ_M. This flag indicates that the medium sizing block should be used for retrieving data, which includes the most commonly used fields and related entities. For example, ccrz.ccServiceProduct.getProducts() will use the SZ_M sizing block by default, unless another sizing block is specified as a parameter. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Data Sizing Conventions
NEW QUESTION # 95
Which three statements are true regarding event handling in the Salesforce B2B Commerce managed package? (3 answers)
- A. Salesforce B2B Commerce relies on a series of Javascript click listener events.
- B. Salesforce B2B Commerce relies on a central event channel for communication across various Salesforce B2B Commerce Backbone Views and Models called CCRZ.pubSub.
- C. Writing directly to your own custom Backbone JS Views and Models automatically integrates that data into the Salesforce B2B Commerce Backbone Views and Models.
- D. CCRZ.pubSub extends the Backbone.Events JavaScript object.
- E. CCRZ.pubSub defines the following three functions which can be used for event handling: trigger, on, and once.
Answer: B,D,E
Explanation:
Three statements that are true regarding event handling in the Salesforce B2B Commerce managed package are:
Salesforce B2B Commerce relies on a central event channel for communication across various Salesforce B2B Commerce Backbone Views and Models called CCRZ.pubSub. This object allows different components to publish or subscribe to events without being coupled with each other. For example, CCRZ.pubSub.trigger('cartChange') will publish an event named cartChange that can be subscribed by any component that needs to react to it.
CCRZ.pubSub defines the following three functions which can be used for event handling: trigger, on, and once. The trigger function is used to publish an event with a name and optional arguments. The on function is used to subscribe to an event with a name and a callback function. The once function is similar to on, but it will only execute the callback function once for each event.
CCRZ.pubSub extends the Backbone.Events JavaScript object. This object provides methods for managing events in Backbone.js, which is a JavaScript framework that provides models, views, collections, and events for building single-page applications. CCRZ.pubSub inherits all the methods and properties of Backbone.Events and adds some custom ones. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Events, PubSub Class
NEW QUESTION # 96
How should data for Lightning web components be provided?
- A. One property that contains all data in one set (object)
- B. Independent properties that take simpler, primitive values (e.g. String, Number, Boolean, Array)
- C. A single property object that contains sets (objects) of data
- D. A few properties that contain sets (objects) of data
Answer: B
Explanation:
Explanation
Data for Lightning web components should be provided as independent properties that take simpler, primitive values (e.g. String, Number, Boolean, Array). Providing data as independent properties allows the developer to expose data as public or private properties of the Lightning web component and communicate data between components or services. Providing data as simpler, primitive values allows the developer to use data types that are supported by JavaScript and Lightning web components and avoid unnecessary or complex conversions or transformations. Providing data as a few properties that contain sets (objects) of data is not a good way to provide data for Lightning web components, as it can create confusion or inconsistency in data structure and access. Providing data as one property that contains all data in one set (object) is not a good way either, as it can create complexity or inefficiency in data management and manipulation. Providing data as a single property object that contains sets (objects) of data is not a good way either, as it can create redundancy or duplication in data storage and retrieval. Salesforce References: Lightning Web Components Developer Guide: Communicate with Properties, Lightning Web Components Developer Guide: Data Types
NEW QUESTION # 97
Which method signature is used in the Global API's?
- A. Changes based on API and Method name
- B. Map<String, Object>
- C. List<List<Object>>
- D. ccrz.cc_Output (ccrz:cc_Input input)
Answer: B
NEW QUESTION # 98
Which two aspects are applicable to Page Includes? (2 answers)
- A. Page Includes must be assigned to an OOTB Page, i.e. Home, Product Detail, etc., and enabled
- B. If a controller is used for an included page, then a merge variable must be present on the page.
- C. Standard Visualforce controls such as apex:form should not be used within a page include
- D. Page Includes can be configured as Body Includes Begin.
Answer: B,C
NEW QUESTION # 99
A developer is trying to troubleshoot why a field is not displaying on the Product Detail Page. What should be typed in the Developer Tools Console in the browser to view the fields available for the Product Detail Page?
- A. CCRZ.productDetailView
- B. CCRZ.productDetailModel
- C. CCRZ.cartView
- D. CCRZ.productSearchView
Answer: B
NEW QUESTION # 100
What is true about mapping custom fields from Cart to Order Summary?
- A. There is a limit of 25 custom fields on a Cart that can be mapped to Order.
- B. All data types are supported for custom fields to be mapped from Cart to Order.
- C. The automatic Cart to Order mapping of custom fields can be disabled.
- D. A custom field must exist in the Cart and Order Summary objects only to be mapped successfully.
Answer: C
Explanation:
Explanation
The correct answer for what is true about mapping custom fields from Cart to Order Summary is that the automatic Cart to Order mapping of custom fields can be disabled. A custom field is a field that is added by a developer or an administrator to an object to store additional information or data. A Cart is an object that represents a collection of products and charges that a customer intends to purchase in the storefront. An Order Summary is an object that represents a confirmed purchase of products and charges by a customer in the storefront. A Cart can be converted to an Order Summary when the customer completes the checkout process and confirms their order. By default, Salesforce B2B Commerce automatically maps custom fields from Cart to Order Summary when converting a Cart to an Order Summary. This means that any custom fields that exist on both Cart and Order Summary objects with identical API names and data types will have their values copied from Cart to Order Summary during the conversion. The automatic Cart to Order mapping of custom fields can be disabled by setting the B2BCommerce.CartToOrderMappingEnabled custom setting to false.
This will prevent any custom fields from being copied from Cart to Order Summary during the conversion. A custom field must exist in the Cart and Order Summary objects only to be mapped successfully is not true, as it is not the only requirement for mapping custom fields from Cart to Order Summary. The custom fields must also have identical API names and data types, and the automatic Cart to Order mapping of custom fields must be enabled. All data types are supported for custom fields to be mapped from Cart to Order is not true, as some data types are not supported for mapping custom fields from Cart to Order Summary. The supported data types are Boolean, Date, DateTime, Double, Integer, Long, Percent, String, and TextArea. There is a limit of 25 custom fields on a Cart that can be mapped to Order is not true, as there is no such limit for mapping custom fields from Cart to Order Summary. Any number of custom fields that meet the mapping requirements can be mapped from Cart to Order Summary. Salesforce References: [B2B Commerce Developer Guide: Custom Field Mapping], [B2B Commerce Developer Guide: Cart Object], [B2B Commerce Developer Guide: Order Summary Object]
NEW QUESTION # 101
Which three actions are applicable when modifying the number of steps required in the Salesforce Commerce Checkout flow? (3 answers)
- A. Set the value of the configuration setting defined as CO.useDef to TRUE
- B. Build and activate a new configuration cache setting via CC admin.
- C. Set the value of the configuration setting defined as CO.overrideFlow to TRUE.
- D. Perform a template override on the Checkout page.
- E. Add a page include to the checkout page.
Answer: B,C,E
NEW QUESTION # 102
Which two steps are necessary to enable Salesforce B2B Commerce
logging in the managed package?
- A. Set a cookie with the Id of the user accessing the storefront in CC Admin
- B. Ensure the value saved in the Logging token field is appended to the ccLog query parameter.
- C. Turn On the Checkbox "Cloudcraze Logging" in CC Admin.
- D. Ensure you save a value in the Logging Token input field in the Global Settings section of CC Admin.
Answer: B,D
NEW QUESTION # 103
Which three steps are necessary to have subscriberpage added to Salesforce B2B Commerce after creating a custom Visualforce page? (3 answers)
- A. Create a new Visualforce page, and manually import the Salesforce B2BCommerce JavaScript libraries. Run in Anonymous Apex ccrz.cc_util_Reflection.upsertPageUIKey([arg1],[arg2],[arg3]);
- B. Refresh the Page Keys Index in CC Admin.
- C. Enable the Subscriber Page in CC Admin.
- D. Create a new CC Subscriber Page record that points to your custom Visualforce page.
Answer: B,C,D
Explanation:
Three steps that are necessary to have a subscriber page added to Salesforce B2B Commerce after creating a custom Visualforce page are:
Create a new CC Subscriber Page record that points to your custom Visualforce page. This record will store information about the subscriber page, such as the name, description, URL, and Visualforce page. For example, you can create a new record named MySubscriberPage that points to your custom Visualforce page named MyPage.
Refresh the Page Keys Index in CC Admin. This action will update the page keys index, which is a cache that stores the mapping between the page keys and the subscriber pages. You need to do this whenever you create or modify a subscriber page record.
Enable the Subscriber Page in CC Admin. This action will allow you to select the subscriber page from the CC Page Settings configuration and assign it to a CC Page. For example, you can enable MySubscriberPage and assign it to the Home page. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Subscriber Pages
NEW QUESTION # 104
A query containing a subquery is executed. What is appended to the subquery name as part of its transformation by default in Salesforce B2B Commerce?
- A. The "*" symbol
- B. "__ccrz"
- C. A subscriber-supplied token
- D. The letter "S"
Answer: B
Explanation:
A query containing a subquery is executed. By default, in Salesforce B2B Commerce, "__ccrz" is appended to the subquery name as part of its transformation. This is done to avoid conflicts with the standard Salesforce fields and relationships. For example, SELECT Id, Name, (SELECT Id, Name FROM Contacts) FROM Account will be transformed to SELECT Id, Name, (SELECT Id, Name FROM Contacts__ccrz) FROM Account__ccrz. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Query Transformation
NEW QUESTION # 105
What is a method to resolve if the current storefront customer is a Salesforce B2B Commerce guest user in an apex class?
- A. ... UserType
- B. ccrz.cc_CallContext.isGuest
- C. UserInfo.getUserType()
- D. ccrz.cc_CallContext.currUser.isGuest
Answer: B
NEW QUESTION # 106
Which three pages should be enabled for the Guest user profile for a storefront to have anonymous checkout? (3 answers)
- A. OrderView
- B. Checkout
- C. CheckoutNew
- D. CCPaymentInfo
- E. OrderConfirmation
Answer: C,D,E
Explanation:
Three pages that should be enabled for the Guest user profile for a storefront to have anonymous checkout are:
CCPaymentInfo: This page allows the guest user to enter their payment information, such as credit card number, expiration date, and security code. The page also displays the order summary and total amount.
CheckoutNew: This page allows the guest user to enter their shipping and billing information, such as name, address, phone number, and email. The page also displays the cart items and shipping options.
OrderConfirmation: This page displays the confirmation message and order number after the guest user places their order. The page also provides a link to view the order details or print the invoice. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Anonymous Checkout
NEW QUESTION # 107
What is a best practice when passing query parameters from user interface to an apex controller?
- A. Query parameters should be passed only to Salesforce B2B Commerce classes that you are extending.
- B. Query parameters should be stored on a backbone model prior to passing them to the server
- C. String parameters should be trimmed using String.trim().
- D. Query parameters should be properly sanitized by using JSINHTMLENCODE within the VisualForce Page or Component.
Answer: D
NEW QUESTION # 108
Which three attributes are true regarding Subscriber pages? (3 answers)
- A. Subscriber pages allow customers to quickly create new custom pages for their storefront.
- B. Out of the Box, Subscriber Pages are completely blank HTML pages.
- C. Subscriber pages can include additional standard Salesforce B2B Commerce components such as featured products, category tree, and mini cart.
- D. All the user interface components must be createdmanually.
- E. Standard Salesforce B2B Commerce components are automatically included on the page e.g. Header links, images, menu items, containers, etc.
Answer: A,B,C
Explanation:
Explanation
Three attributes that are true regarding Subscriber Pages are:
* Subscriber Pages can include additional standard Salesforce B2B Commerce components such as featured products, category tree, and mini cart. These components can be added to the Subscriber Pages by using the CCRZ.pagevars.pageLabels and CCRZ.pagevars.pageSections objects, which contain the page labels and page sections that are defined in CCAdmin.
* Subscriber Pages allow customers to quickly create new custom pages for their storefront. These pages can be used to display any content or functionality that is not available in the default pages, such as FAQs, testimonials, or promotions.
* Out of the Box, Subscriber Pages are completely blank HTML pages. These pages do not have any predefined layout or content, so the user can customize them according to their requirements. The user can use Visualforce, HTML, CSS, JavaScript, or any other web technologies to create their own Subscriber Pages. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Subscriber Pages
NEW QUESTION # 109
What isthe difference between Gross Layout Overrides and Subscriber Templates?
- A. Gross Layout Overrides allow modification to CSS of a page, while Subscriber Templates allows for modification of the entire page including header and footer.
- B. Subscriber Templates allow for modification of the header and the footer, while Gross Layout Overrides allow for modification everything inside the header and footer.
- C. Gross Layout Overrides allow for the modification of the footer, while Subscriber Templates allow for modification of everything inside the header and footer.
- D. Subscriber Templates allows for modification of the header, the footer and the content in between them. Gross Layout Overrides only allow for modification of the header and footer.
Answer: B
Explanation:
The difference between Gross Layout Overrides and Subscriber Templates is that Subscriber Templates allow for modification of the header and the footer, while Gross Layout Overrides allow for modification everything inside the header and footer. Subscriber Templates are custom Visualforce pages that can replace the standard header and footer components on a page. Gross Layout Overrides are custom Visualforce pages that can replace the default layout of a page, such as the number of columns, the position of widgets, or the content of sections. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Subscriber Templates, Gross Layout Overrides
NEW QUESTION # 110
A developer is building a custom component in Lightning web components (LWC) that needs to fetch data from an API.
Which lifecycle hook should the developer use to make the API call?
- A. renderedCallback
- B. disconnectedCallback
- C. connectedCallback
- D. errorCallback
Answer: C
Explanation:
Explanation
To make an API call in a Lightning web component (LWC), a developer should use the connectedCallback lifecycle hook. The connectedCallback lifecycle hook is invoked when the component is inserted into the DOM. This is the ideal time to make an API call, as the component is ready to receive and display data. The developer can use the fetch API or a third-party library, such as axios, to make the API call and handle the response. The renderedCallback lifecycle hook is not a good choice for making an API call, as it is invoked every time the component is rendered or rerendered. This can cause unnecessary or repeated API calls and affect performance. The errorCallback lifecycle hook is not a good choice either, as it is invoked when an error occurs in the component or in one of its children. This is not related to making an API call, but rather to handling errors. The disconnectedCallback lifecycle hook is not a good choice either, as it is invoked when the component is removed from the DOM. This is not a suitable time to make an API call, as the component is no longer visible or active. Salesforce References: Lightning Web Components Developer Guide: Lifecycle Hooks, Lightning Web Components Developer Guide: Call an Apex Method Imperatively
NEW QUESTION # 111
In a B2B Commerce store, which three tasks must a developer complete to implement the use of a third-party service for either tax, shipping, or pricing calculation?
- A. Create an Apex class with an invocable method
- B. Create an Apex class implementing the appropriate interface.
- C. Create a named credential for authentication with an external service
- D. Create a flow to call the external service directly
- E. Register an Apex class as the integration in the store administration
Answer: B,C,E
Explanation:
Explanation
To implement the use of a third-party service for either tax, shipping, or pricing calculation in a B2B Commerce store, a developer must complete these three tasks:
* Create an Apex class that implements the appropriate interface for the calculation type. For example, for tax calculation, the developer must implement the sfdc_checkout.CartTax interface and define the getTax method. This method takes a Cart object as an input parameter and returns a list of CartTax objects with the calculated tax amounts.
* Create a named credential for authentication with the external service. A named credential specifies the URL of a callout endpoint and its required authentication parameters. The developer can use the named credential in the Apex class to make the callout to the external service and handle the response.
* Register the Apex class as the integration in the store administration. The developer must specify the Apex class name in the corresponding field for the calculation type. For example, for tax calculation, the developer must enter the Apex class name in the Tax Calculation Integration field. This way, the store can invoke the Apex class to perform the calculation for each cart.
The other options are not valid tasks for implementing the use of a third-party service. Creating a flow to call the external service directly is not supported for B2B Commerce, and creating an Apex class with an invocable method is not required for the calculation integration. References:
* Integrate with External Services
* CartTax Interface
* Named Credentials
* [Store Administration]
NEW QUESTION # 112
What is default behavior for how the Salesforce B2B Commerce Global APIs transform Salesforce data?
- A. Fields names can be mapped to any naming convention desired
- B. Fields names are returned with a lowercase first letter, camelcase convention
- C. Fields names are returned with "c." prepended in their name.
- D. Fields names are returned using the Salesforce naming convention.
Answer: B
NEW QUESTION # 113
Which two statements are true regarding the cc_CallContext class in Salesforce B2B Commerce? (2 answers)
- A. The current storefront is accessible via thisclass
- B. The Salesforce session is accessible via the getSession method
- C. The userLocale variable returns the current Locale for storefront.
- D. The class can be used internally within Salesforce B2B Commerce and in subscriber code to access context level parameters
Answer: A,D
Explanation:
Explanation
The cc_CallContext class is a utility class that provides access to various context level parameters, such as the current storefront, user, cart, price list, currency, locale, and session. The class can be used internally within Salesforce B2B Commerce and in subscriber code to access these parameters. The current storefront is accessible via this class by using the getStorefront method, which returns a cc_Storefront__c object. The userLocale variable returns the current Locale for storefront, but it is not part of the cc_CallContext class. It is a global variable that can be accessed from any Visualforce page or component by using {!userLocale}. The Salesforce session is accessible via the getSession method, but it is not part ofthe cc_CallContext class either.
It is a method of the cc_SessionUtil class, which is another utility class that provides methods for managing sessions. Salesforce References: [B2B Commerce Developer Guide: cc_CallContext Class], [B2B Commerce Developer Guide: cc_SessionUtil Class]
NEW QUESTION # 114
A dev at Northern Trail Outfitters (NTO) exported Order Summary records via Data Loader, but noticed that some orders were missing. What is the most likely cause?
- A. The user does not have rights to some of the records
- B. The export job did not fully complete
- C. The Status was still set to Draft
- D. Order Life Cycle Type was Managed
Answer: C
Explanation:
The most likely cause of why some orders were missing from the Data Loader export is that the Status was still set to Draft. The Status is a field on the Order Summary object that indicates the current state of the order. The Status can have values such as Draft, Submitted, Confirmed, or Cancelled. A Draft order is an order that has not been submitted or confirmed by the customer or the seller. A Draft order is not considered a completed or valid order and is not included in reports or exports. When using Data Loader to export data from an org, Data Loader will only include orders that have a Status other than Draft, such as Submitted or Confirmed. If an order has a Status of Draft, Data Loader will not include it in the CSV file, which may result in missing orders. The export job did not fully complete is not a likely cause of why some orders were missing from the Data Loader export, as it is not related to the order status or data filtering. Order Life Cycle Type was Managed is not a likely cause either, as it is not related to the order status or data filtering. The Order Life Cycle Type is a field on the Order Summary object that indicates whether the order is managed by Salesforce Order Management or by an external system. The user does not have rights to some of the records is not a likely cause either, as it contradicts the fact that some orders were exported successfully. If the user did not have rights to some of the records, Data Loader would not be able to access or export any orders at all. Salesforce Reference: B2B Commerce Developer Guide: Order Summary Object, B2B Commerce Developer Guide: Order Status Enum, Data Loader Guide: Export Data from Salesforce
NEW QUESTION # 115
Which Global JavaScript Object should be extended when
writing custom Remote Actions?
- A. CCRZ.
- B. CCRZ.cc
- C. CCRZ.cc_CallContext
- D. CCRZ.RemoteInvocation
Answer: B
Explanation:
The Global JavaScript Object that should be extended when writing custom Remote Actions is CCRZ.cc. This object contains all the Remote Actions that are defined in the cloudcraze managed package, which can be overridden or extended by subscriber code. The object also provides a mechanism for registering custom Remote Actions that can be invoked by the user interface components. For example, CCRZ.cc.customAction = function(params, callback){ // do something } will define a custom Remote Action named customAction that can be called by CCRZ.cc.customAction(params, callback). Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Remote Actions
NEW QUESTION # 116
The ccrz.cc_hk_UserInterface apex class, HTMLHead Include Begin and HTML Head Include End Cloudcraze Page Include sections allow additional content to be added to the HTML <head> tag. What are two reasons that is it preferred to use the ccrz.cc_hk_UserInterface extension over the Cloudcraze Page Include sections? (2 answers)
- A. Salesforce apex:include is wrapped in tags.
- B. HTML does not support <span> tags inside the <head>
- C. Salesforce apex:include is wrapped in <span> tags.
- D. HTML does not support <div> tags inside the <head>
Answer: B,C
Explanation:
The ccrz.cc_hk_UserInterface apex class is preferred over the HTMLHead Include Begin and HTML Head Include End Cloudcraze Page Include sections because Salesforce apex:include is wrapped in <span> tags, which are not valid inside the HTML <head> tag. This can cause rendering issues or unexpected behavior in some browsers. The ccrz.cc_hk_UserInterface extension allows adding content to the HTML <head> tag without using apex:include.
NEW QUESTION # 117
......
Salesforce Accredited B2B Commerce Developer Free Update With 100% Exam Passing Guarantee: https://www.torrentvce.com/B2B-Commerce-Developer-valid-vce-collection.html
Real Exam Questions and Answers - Salesforce B2B-Commerce-Developer Dump is Ready: https://drive.google.com/open?id=1QHx73Wt8M1DY6ocPJp3PomzjwkxnllHq