To prevent Cross Site Scripting (XSS) attacks, Magento templates use different methods to escape the output on the website before displaying it to the user. What three methods does Magento use to prevent this kind of attack?

Consider below example of etc/di.xml: Magento\Filesystem\Adapter\Local Please select correct statement based on shared="false" attribute in the example:

You have created a new gateway payment method. You configured the command pool in a di. xml file and added the MyCompany\MyModule\Gateway\Command\Sale command with the name sale to it. Your Sale command extends the Magento\Payment\Gateway\Command\GatewayCommand class.
You have also created a payment_action option in the system configuration and set the value to authorize_capture.
You found the sale command is never called when placing an order.
Which action will fix the problem?

You are working on a project with a large database with many products, sales rules and CMS pages. The merchant is going to use Magento_Staging for scheduled updates, but they were told that use of Staging will modify all SQL queries and slow down website performance.
What modification does Magento_Staging make to existing SQL queries?

Suppose you are working on a specific uicomponet form where front-end customers can update their name and phone number only when the admin user sets the editable_field_flag to 1 for his submitted data from the backend. According to this flag, when loading the data in the form for front-end users, how would you check and customize to enable/disable the name and phone number fields?