Explanation
When services use the ccServiceDao class to execute queries, variables are bound by string substitution. This means that the query string contains placeholders for variables that are replaced by their values at runtime. For example, ccrz.ccServiceDao.getQuery('SELECT Id FROM Account WHERE Name = :name') will replace :name with the value of the name variable.

Explanation
When creating a tax provider, three things that a developer should consider first are: steps to complete in the tax service, how to handle results, and what to implement. Steps to complete in the tax service are the actions that the developer needs to perform to connect to and use the third-party tax service provider's API or service.
These steps may include authentication, authorization, request formatting, response parsing, error handling, and logging. How to handle results are the actions that the developer needs to perform to process and apply the tax calculation results from the tax service to the cart or order. These actions may include creating or updating cart items with type of Charge and charge type of Tax, applying tax adjustments or exemptions, and displaying tax amounts and details on the storefront. What to implement are the methods that the developer needs to define in their custom Apex class that implements the sfdc_checkout.TaxCalculations interface. The interface provides methods for customizing the tax calculation logic for a cart or an order, such as getTaxRatesAndRules, applyTaxAmountsAndAdjustments, and handleTaxErrorsAndExceptions. Whether to use JSON or XML is not something that the developer should consider first, as it is not a critical or relevant factor for creating a tax provider. It may depend on the format that the tax service provider supports or prefers, but it does not affect the overall functionality or performance of the tax integration. What events to fire in the Lightning web component is not something that the developer should consider first either, as it is not related to creating a tax provider. It may be an optional feature that the developer can add to enhance the user interface or user experience of their storefront, but it does not affect the core logic or functionality of the tax integration.
Salesforce References: B2B Commerce Developer Guide: Tax Integration, [B2B Commerce Developer Guide:
Tax Calculations Interface]

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 References: B2B Commerce and D2C Commerce Developer Guide, Query Transformation