Review Flashcards
We have added the customer layout handle adobe_ims_login to deal with all the design changes. This handle is added via ————
\Magento\AdminAdobeIms\Plugin\AddAdobeImsLayoutHandlePlugin::afterAddDefaultHandle.
how to rebuild minified css?
where do we check if token_last_check_time was updated 10 min ago?
\Magento\AdminAdobeIms\Plugin\BackendAuthSessionPlugin
the logout event for The logout from Adobe IMS Service
controller_action_predispatch_adminhtml_auth_logout
IMS
identity management service
what is Vault ?
(stored payment information)
Magento\Variable
Allows to create custom variables and then use them in email templates or in WYSIWYG editor for editing description of system entities.
set opcache.memory_consumption to at least—– to avoid performance degradation.
2GB
For Adobe Commerce 2.3.5 and higher, update your configuration to use the extended Redis cache implementation ………
\Magento\Framework\Cache\Backend\Redis.
.magento.env.yml
stage:
deploy:
REDIS_BACKEND: ‘\Magento\Framework\Cache\Backend\Redis’
For best performance, configure a maximum of —- product options per product.
100
Manage product information through an external …..
Product Management System (PMS).
Longer response time for most storefront scenarios related to products containing—— in attributes.
many options
For Adobe Commerce version 2.3.x and 2.4.0 to 2.4.1-p1, configure no more than —– attributes
For Adobe Commerce version 2.4.2 and later, configure up to —- product attributes
500
1500
Product attribute options–Configure up to —– attribute options for each attribute
Product attribute sets–Configure a maximum of —- attribute sets
100
1000
Configuring many attribute options can affect site performance in the following ways:
Long request and rendering times on product detail (PDP) and category pages containing complex products.
Admin product save operations response time increases above optimal performance targets.
Increase in Product Edit form rendering time.
Slow checkout.
Increases in product data and index sizes can affect site performance in the following ways:
Increased response time for most storefront scenarios related to catalog browsing, search (quick and advanced), and layered navigation.
Product management operations in the Admin slow significantly which can lead to timeouts.
Product Mass Actions functionality can be blocked.
Index re-build time for mid- and large-sized catalogs cannot be performed on a daily basis due to long execution times.
Configuring many product attributes increases the product template size for each product (EAV structure) and the amount of data that must be retrieved. This increase affects operations in the following ways:
Increase in SQL queries traffic related to EAV data retrieval and the amount of data processed which results in decreased DB throughput
Significant increase in the size of Adobe Commerce indexes and the full-text search index
Reaching hard MySQL limits when building a FLAT index for oversized product templates and inability to use it
For best performance, display a maximum of —- products per page.
48
If you have more than 48 products in any category, update the storefront catalog configuration to disable the option to ———–
Allow All Products per page.
For versions 2.3.x - 2.4.2, allow a maximum of —- products in a cart.
For versions 2.4.3 and later, enhancement to sales rules capabilities increased the cart maximum to —-.
100,750
For versions 2.3.x - 2.4.2, the expected performance based on cart item limits is:
Up to — products in a cart—the product works, meeting performance targets for response time.
Up to —- products in a cart—the product works, but response time increases above targets.
Above —– products in a cart—the cart and checkout flows are not guaranteed to work
100,300,500
Use the following strategies to manage the number of cart items
Split orders into several smaller orders with a smaller number of rows by using the Add Item by SKU feature.
Only add the custom logic and cart customization required to load a list of items.
Having more than the recommended maximum number of products in the cart can affect site performance in the following ways:
Increased response time for data retrieval operations, validation of cart items, checks for applying price rules, and tax and total calculations.
Increased response time for minicart rendering including rendering of cart views, checkout flow, and execution.
Increased time loading time for all site pages where the minicart is present.
If your project requires many sites, stores, or store views, you can use the following strategies to improve performance:
Restructure catalog by shifting logic to categories
Separate price lists from catalog data by using external price and a Price Management System (PMS).
Use an alternative noSQL data storage like Elasticsearch
Websites and stores are multipliers for catalog data, so having many websites and stores can negatively affect site performance in the following ways:
Larger index tables increase time required to complete indexing operations [Price index].
Increased time to retrieve application configuration degrades storefront response time for non-cached catalog pages.
Significant increases in the time required to complete Save operations in the Admin since the data is saved separately for each website.
If you do not use the Reports or dynamic customer segments, disable the Reports functionality.
From the Admin, navigate to Stores > Settings > Configuration > General > Reports.
Under General Options, set Enable Reports to No.
Flush cache by running php bin/magento cache:flush or in the Admin under System > Tools > Cache Management.
Adobe recommends using the—– database engine. In a default Adobe Commerce installation, all tables in the database are stored using the InnoDB engine. However, some third-party modules (extensions) can introduce tables in the——- format. After you install a third-party module, check the database to identify any tables in —– format and convert them to —- format.
InnoDB
MyISAM
myisam
innodb
run the following query to determine whether the database has any MyISAM tables:
SELECT table_schema, CONCAT(ROUND((index_length+data_length)/1024/1024),’MB’)
AS total_size FROM information_schema. TABLES WHERE engine=’myisam’ AND table_schema
NOT IN (‘mysql’, ‘information_schema’, ‘performance_schema’, ‘sys’);
Change the storage engine to InnoDB
In the db_schema.xml file declaring the table, set the engine attribute value for the corresponding table node to innodb
To determine which search engine is currently in use, run the following command:
./bin/magento config:show catalog/search/engine
For Adobe Commerce 2.4.4 and later, use the ———-for native MySQL search.
For earlier Adobe Commerce versions, use————
OpenSearch service
Elasticsearch
Triggers are used to log changes into —– tables. Adobe recommends configuring the application to write directly to the audit tables instead of using the —- functionality for these reasons:
audit, trigger
Triggers are interpreted as code and MySQL does not precompile them. Hooking onto your query’s transaction space, they add the—– to a parser and interpreter for each query performed with the table.
The triggers share the—– transaction space as the original queries, and while those queries compete for—- on the table, the triggers independently compete on locks on another table.
overhead, same, locks
To avoid potential issues with cron deadlocks, upgrade ECE-Tools to version ——
2002.0.21 or higher.
Switching indexers generates data definition language (DDL) statements to create—- which can cause —–. You can prevent this issue by putting your website in —— and disabling—— before changing the configuration.
triggers,database locks,maintenance mode, cron jobs
Avoid running—– in the Production environment to prevent conflicts (like table modifications and creations). The setup:upgrade process is an exception.
DDL statements
If you need to run a DDL statement, put the website in —– and ——-(see the instructions for switching indexes safely in the previous section).
maintenance mode,disable cron
Data definition language (DDL) statements let you to perform these tasks: …… schema objects. …..privileges and roles. Analyze information on a table, index, or cluster. Establish…. options.
Create, alter, and drop
Grant and revoke
auditing
Enable …..from the Admin to reduce the space required for Sales tables as your order data grows…… saves MySQL disk space and improves checkout performance.
order archiving , Archiving
If your business does not require reporting or dynamic customer segments functionality,…. the Reports functionality to improve store performance.
disable
One of the key principles in maintaining PCI compliance is …
having a strategy to properly process and store credit card payments.
Storing cardholder data in Adobe Commerce is ….
strictly prohibited and doing so could be a violation of your obligations as a merchant under the Payment Card Industry Data Security Standard (PCI-DSS).
how to make Makes continuous integration build faster?
by reusing unchanged code
what is a slug?
The result of the build phase is a read-only file system named slug, This phase creates an archive and places the slug in permanent storage. The next time you push code, if a service did not change, it uses the slug from the archive.
The slug includes all files and folders excluding the following mounts configured in magento.app.yaml:
“var”: “shared:files/var”
“app/etc”: “shared:files/etc”
“pub/media”: “shared:files/media”
“pub/static”: “shared:files/static”
what does build phase do?
This phase builds the codebase and runs hooks in the build section of .magento.app.yaml
what phase , compresses static files using GZIP, and deploys the files, which reduces downtime in the deployment phase?
build phase
