Valid AD0-E722 Practice Test Dumps with 100% Passing Guarantee [Mar-2024]
AD0-E722 PDF Dumps Are Helpful To produce Your Dreams Correct QA's
NEW QUESTION # 12
While developing a new functionality for a website in developer mode with all cache types enabled, an Adobe Commerce Developer needs to add \Magento\Sales\Model\Service\InvoiceService SinvoiceService as a new dependency to an existing page action controller in Vendor\CustomModule\Controller\Index\Index . This is accomplished as follows:
After cleaning the f ull_page cache and reloading the page, the developer encounters the following exception:
Recoverable Error: Argument 2 passed to Vendor\CustomModule\Controller\Index\Index::__construct() must be an instance of
\Magento\Sales\Model\Service\InvoiceService [...]
Which action should the Architect recommend to the developer to fix this error?
- A. Clean the block_html cache along with full_page cache.
- B. Add the new \Magento\sales\Model\service\invoiceService Sinvoiceservice dependency at the end of the constructor signature.
- C. Remove the generated Child ClaSS from generated/code/Vendor/CustomModule/Controller/Index/Index.
Answer: C
Explanation:
Explanation
The error is caused by the generated child class not being updated with the new dependency. Removing the generated child class will allow the system to generate a new child class with the correct dependency. The generated child class is a proxy class that extends the original controller class and overrides the constructor to inject the dependencies using the object manager. The generated child class is created when the system runs in developer mode with cache enabled, to avoid performance issues. However, when a new dependency is added to the original controller class, the generated child class does not reflect the change and causes a mismatch in the constructor arguments. Therefore, deleting the generated child class from the generated/code directory will solve the problem.
References:
Generated code | Adobe Commerce Developer Guide
Constructor signature change | Adobe Commerce Developer Guide
NEW QUESTION # 13
An Architect is investigating a merchant's Adobe Commerce production environment where all customer session data is randomly being lost. Customer session data has been configured to be persisted using Redis, as are all caches (except full page cache, which is handled via Varnish).
After an initial review, the Architect is able to replicate the loss of customer session data by flushing the Magento cache storage, either via the Adobe Commerce Admin Panel or running bin/magento cache: flush on the command line. Refreshing all the caches in the Adobe Commerce Admin Panel or running bin/magento cache: clean on the command line does not cause session data to be lost.
What should be the next step?
- A. Set the Stores > Configuration' option for Store Session Data Separately' to 'Yes' in the Adobe Commerce Admin Panel.
- B. Check app/etc/env.php and make sure that the Redis configuration for caches and session data use different database numbers.
- C. Educate the merchant to not flush cache storage and only refresh the caches in future.
Answer: B
Explanation:
Explanation
The issue here is that the customer session data is randomly being lost when flushing the Magento cache storage. This is because the Redis configuration for caches and session data might be using the same database number, which causes the session data to be deleted along with the caches. The solution is to check the app/etc/env.php file and make sure that the Redis configuration for caches and session data use different database numbers. This will prevent the session data from being affected by the cache operations. References:
https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/redis.html?lang=e
NEW QUESTION # 14
An Adobe Commerce Architect is reviewing API-functional test code. Some tests send errors to indicate that the customer address does not exist. The test codes show the following:
Which step should the Architect take to fix the test errors?
- A. Update the annotation to Specify addreSSjd EniagentoDataFixture Magento/Customer/_files/customer_one_address.php with:{Maddress_id":"$address.id$"}
- B. Change the annotation to Use@magentoApiDataFixture Magento/Customer/_files/ instead Or dmagentoDataFixture Magento/Customer/_files/customer_one_address.php
- C. Set the annotation to USe AmagentoPersistDataFixture Magento/Cu5tomer/_f iles/custcwer_one_address.php instead Of @magentoDataFixture Magento/Customer/_f iles/customer_one_address.php
Answer: C
Explanation:
Explanation
The issue is being caused by the use of @magentoDataFixture annotation, which creates a temporary data fixture that is rolled back after each test execution1. This means that the customer address created by the fixture is not persisted in the database and cannot be retrieved by subsequent tests. To fix this, the Architect should use @magentoPersistDataFixture annotation, which creates a permanent data fixture that is not rolled back after each test execution2. This way, the customer address created by the fixture will be persisted in the database and can be accessed by subsequent tests. Changing the annotation to use @magentoApiDataFixture or specifying address_id in the annotation will not solve the issue, as they are not related to the persistence of the data fixture3. References: Data fixtures, Persistent data fixtures, API-functional tests
NEW QUESTION # 15
An Adobe Commerce store owner sets up a custom customer attribute "my.attribute".
An Architect needs to display additional content on the home page, which should display only to Customers with "my.attribute" of a certain value and be the same content for all of them. The website is running Full Page Cache.
With simplicity in mind, which two steps should the Architect take to implement these requirements? (Choose two.)
- A. Add a dynamic block with the content to the Home Page
- B. Add a custom block and a pHTML template with the content to the cmsjndexjndex.xml layout
- C. Create a Customer Segment and use 'my.attribute' in the conditions
- D. Add a new context value of "my_attribute" to Magento\Framework\App\Http\Context
- E. Use customer-data JS library to retrieve "my.attribute" value
Answer: A,D
Explanation:
Explanation
To display additional content on the home page based on a custom customer attribute, the Architect needs to do the following steps:
Add a new context value of "my_attribute" to Magento\Framework\App\Http\Context. This will allow the Full Page Cache to generate different versions of the page for customers with different values of
"my.attribute". The context value can be set using a plugin on the Magento\Customer\Model\Context class.
Add a dynamic block with the content to the Home Page. A dynamic block is a type of content block that can be configured to display only to specific customer segments or conditions. The Architect can use the 'my.attribute' in the conditions of the dynamic block and assign it to the Home Page in the Content > Blocks section of the Admin Panel. References:
Private content | Magento 2 Developer Documentation
Dynamic Blocks | Adobe Commerce 2.3 User Guide - Magento
NEW QUESTION # 16
An Adobe Commerce Architect needs to log the result of a ServiceClass:: getData method execution after all plugins have executed. The method is public, and there are a few plugins declared for this method. Among those plugins are after and around types, and all have sortOrder specified.
Which solution should be used to meet this requirement?
- A. Declare a new plugin with the sortOrder value higher than the highest declared plugin sortOrder and implement afterGetData method.
- B. Declare a new plugin with the sortOrder value lower than the lowest declared plugin sortOrder and implement aroundGetData method.
- C. Declare a new plugin with the sortOrder value higher than the highest declared plugin sortOrder and implement aroundGetData method.
Answer: A
Explanation:
Explanation
This solution ensures that the new plugin will execute after all the existing plugins for the ServiceClass::getData method, and will be able to log the final result of the method execution. The afterGetData method of the new plugin will receive the result of the method as a parameter, and can use any logging mechanism to record it. The sortOrder value of the new plugin should be higher than the highest declared plugin sortOrder, so that it will run last in the sequence of plugins. The after type of plugin is preferred over the around type of plugin, because it is simpler and more efficient, and does not require calling the proceed() method.
References:
Plugins (Interceptors) | Adobe Commerce Developer Guide
Plugin best practices | Adobe Commerce Developer Guide
NEW QUESTION # 17
An Adobe Commerce Architect is supporting deployment and building tools for on-premises Adobe Commerce projects. The tool is executing build scripts on a centralized server and using an SSH connection to deploy to project servers.
A client reports that users cannot work with Admin Panel because the site breaks every time they change interface locale.
Considering maintainability, which solution should the Architect implement?
- A. Modify project config.php file, configure 'admin_locales_for_deploy' value, and specify all required locales
- B. Adjust the tools build script and specify required locales during *setup:static-content:deploy' command
- C. Edit project env.php file, configure 'adminJocales_for_build' value, and specify all required locales
Answer: B
Explanation:
Explanation
The issue here is that the site breaks every time the users change interface locale in the Admin Panel. This is because the static content for the different locales is not generated during the deployment process. The solution is to adjust the tools build script and specify required locales during *setup:static-content:deploy' command. This will ensure that the static content for all the needed locales is generated and deployed to the project servers. References:
https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/static-content.htm
NEW QUESTION # 18
A developer needs to uninstall two custom modules as well as the database data and schemas. The developer uses the following command: bin/magento module:uninstall Vendor_SampleMinimal Vendor_SampleModifyContent When the command is run from CLI, the developer fails to remove the database schema and data defined in the module Uninstall class. Which three requirements should the Architect recommend be checked to troubleshoot this issue? (Choose three.)
- A. invoked uninstall() and uninstallschema are defined in the Uninstall class
- B. --remove-schema and --remove-data options are specified as arguments for the CLI command
- C. invoked unlnstalK) method is implemented in the Uninstall class
- D. --remove-data option is specified as an argument for the CLI command
- E. composer.json file is present and defines the module as a composer package
- F. bin/magento maintenance:enable command should be run in CLI before
Answer: C,D,E
NEW QUESTION # 19
An Adobe Commerce Architect runs the PHP Mess Detector from the command-line interface using the coding standard provided with Adobe Commerce. The following output appears:
The Architect looks at the class and notices that the constructor has 15 parameters. Five of these parameters are scalars configuring the behavior of MyService. The class also contains three constants referencing one other class.
How should the Architect fix the code so that it complies with the coding standard rule?
- A. Introduce a new class accepting those five scalars and use it in the constructor and the remaining logic of MyService.
- B. Consolidate the constants referencing other classes into a string representation.
- C. Modify the code of MyService so that the number of different classes and interfaces referenced anywhere inside the class is fewer than 13.
Answer: A
Explanation:
Explanation
The issue is being caused by the high coupling between objects (CBO) value of the class MyService. CBO is a metric that measures the number of classes that are coupled to a given class, either by method calls, property or parameter references, inheritance, or constants1. A high CBO value indicates that the class is too tightly coupled with other classes, which makes it more difficult to maintain, test, and reuse2. To reduce the CBO value, the Architect should introduce a new class that encapsulates the five scalar parameters that configure the behavior of MyService. This way, the constructor of MyService will only have one parameter of the new class type, instead of five scalar parameters. This will also make the code more readable and maintainable, as the new class can provide methods to access and manipulate the configuration data. The constants referencing other classes should not be consolidated into a string representation, as this would not reduce the CBO value and would make the code less clear and type-safe3. The number of different classes and interfaces referenced anywhere inside the class is not relevant for the CBO metric, as it only counts the classes that are coupled to the given class1. References: CBO coupling between object, Coupling Between Object classes (CBO), Cohesion and coupling of an object in OO programming
NEW QUESTION # 20
An Adobe Commerce Architect is working on a scanner that will pull prices from multiple external product feeds. The Architect has a list of vendors and decides to create new config file marketplace.feeds.xml.
Which three steps can the Architect take to ensure validation of the configuration files with unique validation rules for the individual and merged files? (Choose three.)
- A. Implement validation rules in the Converter class for the Config Reader
- B. Create validation rules in marketplace.schema.xsd.
- C. Provide schema to validate an individual file.
- D. Create a class that implements \Magento\Framework\Config\Datainterface.
- E. Provide schema to validate a merged file.
- F. Add the Uniform Resource Name to the XSD file in the config XML file.
Answer: B,C,E
Explanation:
Explanation
The Architect can take the following steps to ensure validation of the configuration files with unique validation rules for the individual and merged files:
Create validation rules in marketplace.schema.xsd. This file defines the structure and constraints of the XML elements and attributes for the marketplace.feeds.xml configuration file. The Architect can use this file to specify the required and optional elements, data types, values, and patterns for the configuration file.
Provide schema to validate a merged file. This schema is used to validate the final configuration file that is generated after merging all the individual configuration files from different modules. The Architect can use this schema to check the consistency and completeness of the merged configuration file.
Provide schema to validate an individual file. This schema is used to validate each individual configuration file from each module before merging them. The Architect can use this schema to check the syntax and validity of each configuration file.
References:
https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/architecture/starter-architecture.htm
NEW QUESTION # 21
A merchant notices that product price changes do not update on the storefront.
The index management page in the Adobe Commerce Admin Panel shows the following:
* All indexes are set to 'update by schedule'
* Their status is 'ready'
* There are no items in the backlog
* The indexes were last updated 1 minute ago
A developer verifies that updating and saving product prices adds the relevant product IDs into the catalog_product_price_cl changelog table. Which two steps should the Architect recommend to the developer to resolve this issue? (Choose two.)
- A. Reduce the frequency of the cron job to 5 minutes so the items have more time to process.
- B. Manually reindex the catalog_product_price index from the command line: bin/magento indexer:reindex catalog_product_price.
- C. Make sure that no custom or third-party modules modify the changelog and indexing process.
- D. Invalidate the catalog_Product_price indexer in the Adobe Commerce Admin Panel so that it is fully reindexed next time the cron runs.
- E. Make sure that the version_id for the price indexer in the mview_state table is not higher than the last entry for the same column in the changelog table and re-synchronize.
Answer: C,E
Explanation:
Explanation
The issue here is that the product price changes are not reflected on the storefront, even though the indexes are set to update by schedule and there are no items in the backlog. This indicates that there might be some problem with the changelog and indexing process, which are responsible for tracking and applying the data changes to the index tables. Therefore, the Architect should recommend the developer to check if any custom or third-party modules interfere with the changelog and indexing process, and disable or fix them if needed.
Additionally, the Architect should recommend the developer to verify that the version_id for the price indexer in the mview_state table is consistent with the last entry for the same column in the changelog table, and re-synchronize them if they are out of sync. This will ensure that the indexer can process all the data changes correctly and update the index tables accordingly. References:
https://experienceleague.adobe.com/docs/commerce-admin/systems/tools/index-management.html?lang=en#cron
NEW QUESTION # 22
Due to a marketing campaign, a website is experiencing a very large number of simultaneously placed orders, which is affecting checkout performance. The website is in the production deploy mode.
Which two website settings can an Architect optimize to decrease the impact on checkout performance?
(Choose two.)
- A. A new database can be created and the Split Database feature can be automatically configured with the following command: bin/Magento setup:db-schema:spiit-sales -host"<checkout db host or ip>-
--dbnanie""<name>" --username"<checkout db username)" --password""<password>" - B. Asynchronous indexing admin panel Setting (Stores > Settings > Configuration > Advanced> Developer
> Grid Settings > Asynchronous indexing) can be enabled by executing the following CLI Command:
bin/Magento config:set dev/grid/async_indexing 1 - C. Asynchronous email notifications admin panel setting (stores > settings > configuration > sales > sales Emails > General settings > Asynchronous) can be enabled
- D. Multithreaded checkout processing admin panel setting (stores > settings > configuration > sales > checkout > General settings > Asynchronous) can be set to a higher value representing the number of PHP threads used exclusively for checkout
- E. The website deploy mode can be set to siege by executingthe following CLI command: bin/Magento deploy:mode:set siege, provided that it will be changed back to production as soon as the number of simultaneously placed orders decreases to acceptable levels
Answer: A,B
Explanation:
Explanation
Option A is correct because enabling asynchronous indexing can improve the checkout performance by reducing the database load and avoiding locking issues. Asynchronous indexing allows the indexers to run in the background without affecting the frontend operations. The command bin/magento config:set dev/grid/async_indexing 1 can be used to enable this option in the production mode1.
Option C is correct because creating a new database and splitting the sales tables can also improve the checkout performance by distributing the database load and avoiding contention. Splitting the database allows the checkout and order management operations to use a separate master database from the rest of the Magento application tables. The command bin/magento setup:db-schema:split-sales
--host="<checkout db host or ip>" --dbname="<name>" --username="<checkout db username>"
--password="<password>" can be used to configure this feature2.
Option B is incorrect because enabling asynchronous email notifications does not affect the checkout performance directly. Asynchronous email notifications allow the order confirmation emails to be sent in batches by a cron job instead of immediately after placing an order. This option can reduce the server load and improve the customer experience, but it does not impact the checkout process itself3.
Option D is incorrect because there is no such deploy mode as siege in Magento 2. The available deploy modes are default, developer, and production. Changing the deploy mode can affect the performance, caching, and error handling of the Magento application, but it does not directly affect the checkout performance4.
Option E is incorrect because there is no such admin panel setting as multithreaded checkout processing in Magento 2. The number of PHP threads used for checkout is determined by the web server configuration and the PHP-FPM settings, not by the Magento application settings. Increasing the number of PHP threads may improve thecheckout performance, but it also requires more server resources and may cause other issues5.
References:
1: Asynchronous indexing | Adobe Commerce Developer Guide
2: Split database performance solution | Adobe Commerce Developer Guide
3: Sales Emails | Adobe Commerce User Guide
4: Set up Magento modes | Adobe Commerce Developer Guide
5: PHP-FPM configuration settings | Adobe Commerce Developer Guide
NEW QUESTION # 23
An Architect wants to create an Integration Test that does the following:
* Adds a product using a data fixture
* Executes $this->someLogic->execute($product) on the product
* Checks if the result is true.
$this->someLogic has the correct object assigned in the setup() method.
Product creation and the tested logic must be executed in the context of two different store views with IDs of 3 and 4, which have been created and are available for the test.
How should the Architect meet these requirements?
- A. Create two test classes with one test method each. Use the @magentoExecuteinstoreContext 3 and
$MagentoExecuteinStoreContext 4 annotations on the class level. - B. Create one test class with one test method. Use the
\Magento\TestFramework\store\ExecuteinstoreContext class once in the fixture and another time in the test. - C. Create one test class with two test methods. Use the emagentostorecontext 3 annotation in one method and amagentostorecontext 4 in the other one.
Answer: B
Explanation:
Explanation
To create an integration test that executes different logic in different store views, the Architect needs to do the following steps:
Create one test class that extends \Magento\TestFramework\TestCase\AbstractController or
\Magento\TestFramework\TestCase\AbstractBackendController, depending on the type of controller being tested1.
Create one test method that uses the @magentoDataFixture annotation to specify the data fixture file that creates the product2.
Use the \Magento\TestFramework\Store\ExecuteInStoreContext class to execute the fixture and the tested logic in different store views. This class has a method called executeInStoreContext, which takes two parameters: the store ID and a callable function. The callable function will be executed in the context of the given store ID, and then the original store ID will be restored3. For example:
PHPAI-generated code. Review and use carefully. More info on FAQ.
public function testSomeLogic()
{
// Get the product from the fixture
$product = $this->getProduct();
// Get the ExecuteInStoreContext instance from the object manager
$executeInStoreContext =
$this->_objectManager->get(\Magento\TestFramework\Store\ExecuteInStoreContext::class);
// Execute the fixture in store view 3
$executeInStoreContext->executeInStoreContext(3, function () use ($product) {
// Do some operations on the product in store view 3
});
// Execute the tested logic in store view 4
$result = $executeInStoreContext->executeInStoreContext(4, function () use ($product) {
// Call the tested logic on the product in store view 4
return $this->someLogic->execute($product);
});
// Assert that the result is true
$this->assertTrue($result);
}
References:
Integration tests | Magento 2 Developer Documentation
Data fixtures | Magento 2 Developer Documentation
Magento\TestFramework\Store\ExecuteInStoreContext | Magento 2 Developer Documentation
NEW QUESTION # 24
An Architect working on a headless Adobe Commerce project creates a new customer attribute named my_attribute. Based on the attribute value of the customer, the results of GraphQI queries are modified using a plugin. The frontend application is communicating with Adobe Commerce through Varnish by Fastly. which is already caching the queries that will be modified. The Adobe Commerce Fastly extension is installed, and no other modifications are made to the application.
Which steps should the Architect take to make sure the vcl_hash function of Varnish also considers the newly created attribute?
- A. Createa new class inheriting from Magento\Framework\GraphQi\Query\Resolver\identityinterfaca and returning the value of my_attributefrom the getidentities function.
Then specify a ecache(cacheidentity: Path\\To\\identityclass) directive for each GraphQL query to include the newly created IdentityClass to each query that adds the cache tags for each customer. - B. Create a new ClaSS inheriting from
Magento\GraphQlCache\Model\CacheId\CacheIdFactorProvidftrInterface and returning the Value of my_attribute from the getFactorValuefunction and my_attribute from the getFactorName function. Then add this class through Dl to the idFactorProviders array ofMagento\GraphQlCache\Model\CacheId\CacheIdCalculator. - C. Create a new class inheriting from Magento\customer\customerData\stctionSourceinterface and returning the value of my_attributefrom the getSectionData function. Then add thisClaSS through the sectionSourceMap array Of Magento\Customer\CustomerData\SectionPoolInterface.
Answer: B
Explanation:
Explanation
To make sure the vcl_hash function of Varnish considers the newly created attribute, the Architect needs to do the following steps:
Create a new class that implements the
Magento\GraphQlCache\Model\CacheId\CacheIdFactorProviderInterface interface. This interface defines two methods: getFactorName and getFactorValue. The getFactorName method should return the name of the attribute, in this case, my_attribute. The getFactorValue method should return the value of the attribute for the current customer, which can be obtained from the customer session or customer repository1.
Add this class to the idFactorProviders array of
Magento\GraphQlCache\Model\CacheId\CacheIdCalculator through dependency injection. The CacheIdCalculator is responsible for generating a cache ID for each GraphQL request based on the factors provided by the idFactorProviders. By adding the new class to this array, the Architect ensures that the cache ID will include the value of my_attribute1.
The cache ID is then used by Varnish to hash and lookup the cached response for each request. By including my_attribute in the cache ID, the Architect ensures that Varnish will serve different responses based on the attribute value of the customer2.
Magento_GraphQlCache module | Magento 2 Developer Documentation
Varnish caching | Adobe Commerce 2.4 User Guide - Magento
NEW QUESTION # 25
An Adobe Commerce Architect needs to create a new customer segment condition to enable admins to specify an Average sales amount' condition for certain segments.
The Architect develops the custom condition under
Vendor\Module\Model\Segment\Condition\AverageSalesAmount with all of its requirements:
During testing, the following error appears:
What should the Architect do to fix the problem?
- A.
- B.
- C.
Answer: A
Explanation:
Explanation
The error is caused by the missing class declaration for the custom condition class. According to the Adobe Commerce documentation, to create a custom customer segment condition, the class must extend the
\Magento\CustomerSegment\Model\Condition\AbstractCondition class and implement the
\Magento\CustomerSegment\Model\Condition\Combine\Interface interface. The class must also declare its name, label, value type, and attribute code properties. Option B is the only option that correctly declares the class with the required properties and inheritance. Option A and Option C are incorrect because they do not extend the AbstractCondition class or implement the CombineInterface interface, and they do not declare the name, label, value type, or attribute code properties.
References:
Create a customer segment condition | Adobe Commerce Developer Guide
AbstractCondition | Adobe Commerce Developer Guide
NEW QUESTION # 26
An Adobe Commerce Architect creates a stopword for the Italian locale named stopwordsjtJT.csv and changes the stopword directory to the following: <magento_root>/app/code/Customvendor/Elasticsearch/etc/stopwords/ What is the correct approach to change the stopwords directory inside the custom module?
- A. Add a new ClaSS implementing \Magento\Framework\Setup\Patch\PatchInterface to modify the default Value Of elasticsearch\customer\stopwordspath in core.conf ig_data table.
- B. Add stopwords to the stopwordsDirectory parameter of the\Hagento\Elasticsearch\Model\Adapter\Document\DirectoryBuilder ClaSS Via stopwords/it.xml and Adobe Commerce will automatically detect the current module.
- C. Add stopwords to the stopwordsDirectory and CustomerVendor_Elasticsearch to the stopword sModule parameter Of the \Magento\Elasticsearch\SearchAdapter\Query\Preprocessor\Stopwords ClflSS Via di.xml
Answer: C
Explanation:
Explanation
According to the Adobe Commerce documentation, the correct approach to change the stopwords directory inside a custom module is to use dependency injection to override the default values of the stopwordsDirectory and stopwordsModule parameters of the
\Magento\Elasticsearch\SearchAdapter\Query\Preprocessor\Stopwords class. The stopwordsDirectory parameter specifies the relative path of the stopwords directory from the module directory, while the stopwordsModule parameter specifies the name of the module that contains the stopwords directory. By adding these parameters to the di.xml file of the custom module, the Architect can change the location of the stopwords files without modifying the core code or database.
References:
To change the directory from your module
Configure Elasticsearch stopwords
NEW QUESTION # 27
......
Adobe AD0-E722 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
Cover AD0-E722 Exam Questions Make Sure You 100% Pass: https://www.dumpsactual.com/AD0-E722-actualtests-dumps.html
New AD0-E722 exam Free Sample Questions to Practice: https://drive.google.com/open?id=1DMB6fShpqiRhWT21pUms7C32Qn3CoN8s
