Preparing for the Magento Developer Certificaton Exam
This website was a helpful guide to preparing for the Magento Developer certification exam. The content below is from the site's 2012-2013 archived pages.It offers just a small sample of what this site used to offer.
Magento Certified Developer Study Guide Posts
Both junior and senior developers, who work with Magento on a constant basis or just start learning this platform, think over the perspective to obtain Magento Developer Certificate some day. Benefits are innumerable, ranging from a catchy point in CV, worldwide job skills recognition to exciting career prospects on on a global scale.
BelVG can’t bypass the matter of many developers concern – Magento Certified Developer Exam, which contains of multiple-choice questions based on Magento Community Edition 1.5. Magento exam does not imply prerequisites. Find more information about Magento Developer Certification on Magento Commerce official website. Preparing themselves to exam, developers are offered to examine the Magento Certified Developer Study Guide.
We start a new section in our blog, dedicated to Magento Certified Developer Exam preparation, answering questions from above-mentioned Study Guide in series. Today we look through the first question Describe Magento codepools from the Basics chapter, High-level Magento architecture.
Describe Magento Codepools
Magento has three different codepools:
First of all, this folder stores all the code that makes Magento so powerful, flexible and lovely. The chief rule of Magento development is that you should never make any changes in it. In other words, this folder belongs to Magento core developers only and if you are going to edit anything in this pool, their evil spirit could punish you even through the display.
This folder belongs entirely to community developers. This is the right place for hundreds of 3rd party extensions, both free and paid, that can be found at MagentoConnect or available on extensions development store (for instance, http://store.belvg.com/). So basically, if you have installed any extension, it must be in app/code/community/ only.
If you have your own Magento-based store and want to make everything by yourself or you are a Magento developer and have a purpose to change the logic somehow, local pool is the place where everything should be done. If you want to override Magento extensions, blocks or methods, copy the necessary folders from the Core pool and do whatever you are inclined to do. Apply the same rule for custom extensions that are created specifically for the website – all code should be in local pool.
How does the framework interact with the various codepools?
To identify the proccess let’s take a look at app/Mage.php
* Set include path
$paths = BP . DS . 'app' . DS . 'code' . DS . 'local';
$paths = BP . DS . 'app' . DS . 'code' . DS . 'community';
$paths = BP . DS . 'app' . DS . 'code' . DS . 'core';
$paths = BP . DS . 'lib';
$appPath = implode(PS, $paths);
set_include_path($appPath . PS . Mage::registry('original_include_path'));
This code snippet illustrates the order Magento is using to include paths – firstly it includes Local code pool, than community and after that – core, which allow developers to override classes without changing core files.
Describe Magento templates and layout files location
A theme consists of the following elements:
Layout folder includes XML files that define the layout of the theme. Layout files work as a “glue” between the modules (which are found under the app/code directory), and the template files.
Because of Magento modularity, all XML files of the default theme are stored in separate folders with the name of the module to which they belong to. A non-default theme, contrariwise, should have a single layout file, named local.xml, where all layout updates are placed.
Template folder contains of .phtml files that have HTML and PHP code for each Magento blocks which will be displayed in the frontend.
Locale folder contains .of CSV files organized on a per language basis that provide translations in format of languagecode_COUNTRTYCODE (en_US or en_UK)/translate.csv. More detailed information about internationalization will come in the future articles
Typical Magento Module structure
Typical Magento Module structure has the following folders and is based on MVC architecture.
Let’s review all parts of module structure step by step.
This folder liability is View, if we use terms of classical MVC architecture. Blocks coordinate models with the template files. The files in the folder load the data from database and transfer it to the templates in your theme (.phtml files).
Controllers represent all business logic actions for the given request (dispatch(), preDispatch(), postDispatch() methods) and delegate commands to other parts of the system.
It contains all xml files that declare and configure behavior of all modules. Each module must have at least config.xml and it’s a right place to declare all models, routers, blocks, helpers, etc.
Optionally this folder could have adminhtml.xml (grant permissions for your tabs/sections in backend menus) and system.xml (creates this new section or specifies where it should be displayed in existing one).
Find more about xml structure here.
Here you can create methods that would be useful for your store in different ways. Helpers contain utility methods, which are commonly used in the whole system. Methods, declared in helpers, can be called from any template file or block, model, controller class by
Each Module has a default Data Helper class Modulename/Helper/Data.php and we can call it as
In classical MVC, Models are used to connect to the database and process the data from and to it. Magento has a different approach, which can be tricky at first look.
“Most Magento Models can categorized in one of two ways. There’s a basic, ActiveRecord-like/one-object-one-table Model, and there’s also an Entity Attribute Value (EAV) Model. Each Model also gets a Model Collection. Collections are PHP objects used to hold a number of individual Magento Model instances. The Magento team has implemented the PHP Standard Library interfaces of IteratorAggregate and Countable to allow each Model type to have it’s own collection type. If you’re not familiar with the PHP Standard Library, think of Model Collections as arrays that also have methods attached. Magento Models don’t contain any code for connecting to the database. Instead, each Model uses two modelResource classes, (one read, one write), that are used to communicate with the database server (via read and write adapter objects).”
Handles any custom database tables which will be used by the module and process all upgrades to the extension.
To tell Magento which modules should be used and where they are located, we need to create XML file in the folder, from which it takes all xml files – etc/modules/
You can indicate additional parameters such as depends, version and platform (can be defined in module’s config.xml as well):
Magento Certified Developer Study Guide
1- Basics - 6% of the exam.
High-level Magento architecture
- 1. Describe Magento codepools
- 2. Describe typical Magento module structure
- 3. Describe Magento templates and layout files location
- 5. Identify and explain the main Magento design areas (adminhtml and frontend)
- 6. Explain class naming conventions and their relationship with the autoloader
- 7. Describe methods for resolving module conflicts
- How does the framework interact with the various codepools?
- What constitutes a namespace and a module?
- What does the structure of a complete theme look like?
- 8. Explain how Magento loads and manipulates configuration information
- 9. Describe class group configuration and use in factory methods
- 10. Describe the process and configuration of class overrides in Magento
- 11. Register an Observer
- 12. Identify the function and proper use of automatically available events, including *_load_after, etc.
- 13. Set up a cron job
- How does the framework discover active modules and their configuration?
- What are the common methods with which the framework accesses its configuration values and areas?
- How are per-store configuration values established in the XML DOM?
- By what process do the factory methods and autoloader enable class instantiation?
- Which class types have configured prefixes, and how does this relate to class overrides?
- Which class types and files have explicit paths?
- What configuration parameters are available for event observers?
- What are the interface and configuration options for automatically fired events?
- What is the structure of event observers, and how are properties accessed therein?
- What configuration parameters are available for cron jobs?
- 14. Describe how to plan for internationalization of a Magento site
- 15. Describe the use of Magento translate classes and translate files
- 16. Describe the advantages and disadvantages of using subdomains and subdirectories in internationalization
- Which method is used for translating strings, and on which types of objects is it generally available?
- In what way does the developer mode influence how Magento handles translations?
- How many options exist to add a custom translation for any given string?
- What is the priority of translation options?
- How are translation conflicts (when two modules translate the same string) processed by Magento?
2- Request Flow - 7% of the exam.
- 17. Describe the steps for application initialization
- 18. Describe the role of the system entrypoint, index.php
- Starting with the index.php, including Mage.php, follow through the steps Magento takes to set up the run time environment.
- How and when is the include path set up and the auto loader registered?
- How and when does Magento load the base configuration, the module configuration, and the database configuration?
- How and when are the two main types of setup script executed?
- When does Magento decide which store view to use, and when is the current locale set?
- Which ways exist in Magento to specify the current store view?
- When are the request and response objects initialized?
- Mage_Core_Model_Config::loadBase() and init()
- 19. Describe the role of the Front Controller
- 20. Identify uses for events fired in the Front Controller
- Which ways exist in Magento to add router classes?
- What are the differences between the various ways to add routers?
- Think of possible uses for each of the events fired in the front controller
- Mage_Core_Controller_Varien_Front::init() and dispatch()
- 21. Describe URL structure/processing in Magento
- 22. Describe the URL rewrite process
- Focus on the internals of database-based URL rewrites.
- What is the purpose of each of the fields in the core_url_rewrite table?
- When does Magento created the rewrite records for categories and products?
- How and where does Magento find a matching record for the current request?
- 23. Describe request routing/request flow in Magento
- 24. Describe how Magento determines which controller to use and how to customize route-to-controller resolution
- Starting with the front controller delegating the process of mapping a request to a controller action, study the steps that occur until a controller action is dispatched.
- Which routers exist in a native Magento implementation?
- How does the standard router map a request to a controller class?
- How does the standard router build the filesystem path to a file that might contain a matching action controller?
- How does Magento process requests that cannot be mapped?
- After a matching action controller is found, what steps occur before the action method is executed?
- Mage_Core_Controller_Varien_Router_Standard::collectRoutes() and match()
- 25. Describe the steps needed to create and register a new module
- 26. Describe the effect of module dependencies
- 27. Describe different types of configuration files and the priorities of their loading
- What does "Magento loads modules" mean?
- In which order are Magento modules loaded?
- Which core class loads modules?
- Which core class loads modules?
- What are the consequences of one module depending on another module?
- During the initialization of Magento, when are modules loaded in?
- Why is the load order important?
- What is the difference regarding module loading between Mage::run() and Mage::app()?
- Mage::run() and Mage::app()
- Mage_Core_Model_App::run() and init()
Design and layout initialization
- 28. Identify the steps in the request flow in which:
- 1. Design data is populated
- 2. Layout configuration files are parsed
- 3. Layout is compiled
- 4. Output is rendered
- Which ways exist to specify the layout update handles that will be processed during a request?
- Which classes are responsible for the layout being loaded?
- How are layout xml directives processed?
- Which configuration adds a file containing layout xml updates to a module?
- Why is the load order of layout xml files important?
Flushing data (output)
- 29. Describe how and when Magento renders content to the browser
- 30. Describe how and when Magento flushes output variables using the Front Controller
- Which events are associated with sending output?
- Which class is responsible for sending output?
- What are possible issues when this output is not sent to the browser using the typical output mechanism, but is instead sent to the browser directly?
- How are redirects handled?
- Mage_Core_Controller_Response_Http and super classes
3- Rendering - 7% of the exam.
Themes in Magento
- 31. Define and describe the use of themes in Magento
- 32. Define and describe the use of design packages
- 33. Describe the process of defining template file paths
- (Ad.1) How you can use themes to customize core functionality?
- (Ad.1) How can you implement different designs for different stores using Magento themes?
- (Ad.1) In which two ways you can register custom theme?
- (Ad.2) What is the difference between package and theme?
- (Ad.2) What happens if the requested file is missed in your theme/package?
- (Ad.3) Which kind of paths (absolute or relative) does Magento use for templates and layout files?
- (Ad.3) How exactly can Magento define which physical file correspond to certain template/layout to use?
- (Ad.3) Which classes and methods need to be rewritten in order to add additional directories to the fallback list?
- (Ad.1,2) Mage_Core_Model_Layout
- (Ad.1,2) Mage_Core_Model_Layout_Update
- (Ad.1,2,3) Mage_Core_Model_Design
- (Ad.1,2,3) Mage_Core_Model_Design_Package
- (Ad.2,3) Mage_Core_Block_Template
- 34. Describe the programmatic structure of blocks
- 35. Describe the relationship between templates and blocks
- 36. Describe the stages in the lifecycle of a block
- 37. Describe events fired in blocks
- 38. Identify different types of blocks
- 39. Describe block instantiation
- 40. Explain different mechanisms for disabling block output
- 41. Describe how a typical block is rendered
- (Ad.1) What are blocks used for in Magento?
- (Ad.1) What is the parent block for all Magento blocks?
- (Ad.1) Which class does each block that uses a template extend?
- (Ad.1) In which way does a template block store information about its template file? Does it store an absolute or a relative path to the template?
- (Ad.1) What is the role of the Mage_Core_Block_Abstract class?
- (Ad.2) Can any block in Magento use a template file?
- (Ad.2) How does the $this variable work inside the template file?
- (Ad.2) Is it possible to render a template without a block in Magento?
- (Ad.2) Is it possible to have a block without a template in Magento?
- (Ad.3) Which class is responsible for creating an instance of the block?
- (Ad.3) Which class is responsible for figuring out which blocks should be created for certain pages?
- (Ad.3) How is the tree of blocks typically rendered?
- (Ad.3) Is it possible to create an instance of the block and render it on the page without using the Magento layout?
- (Ad.3) Is it possible to create an instance of the block and add it to the current layout manually?
- (Ad.3) How are a block's children rendered? Once you added a child to the block, can you expect it will be rendered automatically?
- (Ad.3) What is a difference in rendering process for different types of blocks?
- (Ad.4) How can block output be caught using an observer?
- (Ad.4) What events do Mage_Core_Block_Abstract and Mage_Core_Block_Template fire?
- (Ad.5) What is the purpose of each of the following block types:
- (Ad.36) Which block type renders its children automatically?
- (Ad.5) Which block type is usually used for a pages?
- (Ad.6) How can a template's block instance be accessed inside the template file, and how can other block instances be accessed?
- (Ad.6) How can block instances be accessed from the controller?
- (Ad.6) How can block instances be accessed inside install scripts or other model class instances?
- (Ad.7) In which ways can block output be disabled in Magento?
- (Ad.7) Which method can be overridden to control block output?
- (Ad.8) Which class performs rendering of the template?
- (Ad.8) Which classes are responsible for figuring out the absolute path for including the template file?
- (Ad.8) In which method are templates rendered?
- (Ad.8) How can output buffering be enabled/disabled when templates are rendered?
- (Ad.1,3,6,7,8) Mage_Core_Model_Layout
- (Ad.1,3,6,8) Mage_Core_Model_Layout_Update
- (Ad.1,2,3,5,8) Mage_Core_Block_Template
- (Ad.1,2,3,4,5,8) Mage_Core_Block_Abstract
- (Ad.1) Mage_Adminhtml_Block_Abstract
- (Ad.3,5) Mage_Core_Block_Text
- (Ad.3,5) Mage_Core_Block_Text_List
- (Ad.5) Mage/Core/Block/*
- (Ad.5) Mage_Page_Block_Html_Head
- (Ad.6) Mage_Core_Controller_Varien_Action
Design layout, XML schema, and CMS content directives
- 42. Describe the elements of Magento's layout XML schema, including the major layout directives
- 43. Register layout XML files
- 44. Create and add code to pages
- 45. Explain how variables can be passed to block instances via layout XML
- (Ad.1) How are
, , and used in Magento layout?
- (Ad.1) Which classes and methods determine which nodes from layout XML correspond to certain urls?
- (Ad.2) How can layout XML files be registered for the frontend and adminhtml areas?
- (Ad.3) How can code be modified or added to Magento pages using the following methods?
- - Template customizations
- - Layout customizations
- - Overriding block classes
- - Registering observers on general block events
- (Ad.3) In which circumstances are each of the above methods more or less appropriate than others?
- (Ad.4) How can variables be passed to the block using the following methods?
- - From layout xml file
- - From controller
- - From one block to another
- - From an arbitrary location (for example, install/upgrade scripts, models)
- (Ad.4) In which circumstances are each of the above methods more or less appropriate than others?
- (Ad.1,4) Mage_Core_Model_Layout
- (Ad.1) Mage_Core_Model_Layout_Update
- (Ad.1,3,4,5) Mage_Core_Block_Abstract
- (Ad.2) Mage_Core_Model_Layout_Update
- (Ad.3,4) Mage_Core_Controller_Varien_Action
- (Ad.3,4,5) Mage/Core/Block/*
- (Ad.3,4,5) Mage_Core_Block_Template
- (Ad.3,4,5) Mage_Core_Block_Text
- (Ad.3,4,5) Mage_Core_Block_Text_List
- (Ad.3,4,5) Mage_Page_Block_Html_Head
4. Working with Database in Magento - 13% of the exam.
Models, resource models, and collections
- 47. Describe the basic concepts of models, resource models, and collections, and the relationship they have to one another
- 48. Configure a database connection
- 49. Describe how Magento works with database tables
- 50. Describe the load-and-save process for a regular entity
- 51. Describe group save operations
- 52. Describe the role of Zend_Db_Select in Magento
- 53. Describe the collection interface (filtering/sorting/grouping)
- 54. Describe the hierarchy of database-related classes in Magento
- 55. Describe the role and hierarchy of setup objects in Magento
- Which methods exist to access the table of a resource model?
- Which methods exist to create joins between tables on collections and on select instances?
- How do table name lookups work, and what is the purpose of making table names configurable?
- Which events are fired automatically during CRUD operations?
- How does Magento figure out if a save() call needs to create an INSERT or an UPDATE query?
- How does Magento figure out if a save() call needs to create an INSERT or an UPDATE query?
- How many ways exist to specify filters on a flat table collection?
- Which methods exist to influence the ordering of the result set for flat table collections? How do the methods differ?
- Why and how does Magento differentiate between setup, read, and write database resources?
- 56. Describe the Install/Upgrade Workflow
- 57. Write install and upgrade scripts using set-up resources
- 58. Identify how to use the DDL class in setup scripts
- Under which circumstances are setup scripts executed?
- How and where does Magento differentiate between install, upgrade, and downgrade scripts?
- What is the difference between the different classes used to execute setup scripts?
- Which is the base setup class for flat table entities, and which one the base for EAV entities?
- Which methods are generally available in setup scripts to manipulate database tables and indexes?
- What is the difference between addAttribute() and updateAttribute() in EAV setup scripts?
- How can you implement a rollback in Magento?
- Mage_Core_Model_App::run() and _initModules()
- Mage_Core_Model_Resource_Setup::applyAllUpdates() and applyAllDataUpdates()
- Mage_Eav_Model_Entity_Setup::addAttribute() and updateAttribute()
5- Entity-Attribute-Value (EAV) Model - 10% of the exam.
EAV model concepts
- 59. Define basic EAV concepts and class hierarchy
- 60. Describe the database schema for EAV entities
- 61. Describe the EAV entity structure and its difference from the standard core resource model
- 62. Describe the EAV load-and-save process and its differences from the regular load- and-save process
This objective covers understanding how EAV entity values are stored in the database, how the involved tables relate, how the EAV resource models differ from the flat table resource models and how the EAV models process CRUD operations.
- Which classes in Mage_Eav are used as resource models and which are used as regular models?
- How do flat and EAV resource models differ?
- Which entities in a native Magento installation use EAV resource models and why?
- What are the advantages and disadvantages of EAV over flat table resource models?
- How are store and website scope attribute values implemented in the Magento EAV system?
- How does the model distinguish between insert and update operations?
- How do load and save processes for EAV entities differ from those for flat table entities? What parts are identical?
- Mage_Eav_Model_Entity_Abstract::load() andsave()
- Mage_Core_Model_Abstract::load() and save()
- 63. Identify the purpose of attribute frontend, source, and backend models
- 64. Describe how to implement the interface of attribute frontend, source, and backend models
- 65. Describe how to create and customize attributes
- (Ad.2) How do attribute models, attribute source models, attribute backend models and attribute frontend models relate to each other?
- (Ad.2) Which methods have to be implemented in a custom source model (or frontend model or backend model)?
- (Ad.2) Can adminhtml system configuration source models also be used for EAV attributes?
- (Ad.2) What is the default frontend model (and source and backend model) for EAV attributes?
- (Ad.2) Does every attribute use a source model?
- (Ad.2) Which classes and methods are related to updating the EAV attribute values in the flat catalog tables? What factors allow for attributes to be added to flat catalog tables?
- (Ad.2) How are store-scoped entity attribute values stored when catalog flat storage is enabled for that entity type?
- (Ad.2) Which frontend, source, and backend models are available in a stock Magento installation?
- (Ad.2) How do multi-lingual options for attributes work in Magento?
- (Ad.2) How do you get a list of all options for an attribute for a specified store view in addition to the admin scope?
- (Ad.3) Besides simply using the stock EAV attributes that come with Magento, one of the most common operations for developers is to modify or create attributes.
- (Ad.3) Which setup methods are available to work with EAV entities?
- (Ad.3) How can an EAV setup class be instantiated in a setup script if not specified in the XML configuration for a setup resource?
- (Ad.3) What is the difference between addAttribute() and updateAttribute()?
- (Ad.3) What are the advantages of using a custom setup class for manipulating EAV attributes in a custom module?
- (Ad.2) Mage_Eav_Model_Entity_Attribute_Abstract
- (Ad.2) Mage_Eav_Model_Entity_Attribute_Backend_Abstract
- (Ad.2) Mage_Eav_Model_Entity_Attribute_Frontend_Abstract
- (Ad.2) Mage_Eav_Model_Entity_Attribute_Source_Abstract
- (Ad.2) Mage_Eav_Model_Entity_Attribute_Source_Table
- (Ad.2) Mage_Eav_Model_Mysql4_Entity_Attribute_Option_Collection::load()
- (Ad.3) Mage_Eav_Model_Entity_Setup
6. Adminhtml - 7% of the exam.
- 66. Describe the similarities and differences between adminhtml and frontend interface and routing
- 67. Describe the components and types of cache clearing using the adminhtml interface
- (Ad.1) Which areas in configuration are only loaded for the admin area?
- (Ad.1) What is the difference between admin and frontend controllers?
- (Ad.1) When does Magento figure out which area to use on the current page?
- (Ad.1) How you can make your controller work under the /admin route?
- (Ad.2) At which moment does Magento check if a user is logged in or not
- (Ad.2) Which class do most Magento adminhtml blocks extend
- (Ad.2) What are the roles of adminhtml config
- (Ad.2) What are the differences between the different cache types on the admin cache cleaning page
- (Ad.2) What is the difference between “Flush storage” and “Flush Magento Cache”
- (Ad.2) How you can clear the cache without using the UI
- (Ad.1) Mage_Adminhtml_Controller_Action
- (Ad.1) Mage_Core_Model_Layout
- (Ad.1) Mage_Core_Model_Layout_Update
- (Ad.1) Mage_Core_Controller_Varien_Router_Standard
- (Ad.2) Mage_Adminhtml_Model_Config
- (Ad.2) Mage_Adminhtml_Model_Config_Data
- (Ad.2) Mage_Admin_Model_Observer
- (Ad.2) Mage_Core_Model_Cache
Forms in Magento
- 68. Define form structure, form templates, grids in Magento, and grid containers and elements
- Which block does a standard Magento form extend?
- What is the default template for a Magento form?
- Describe the role of a form container and its template.
- Describe the concept of Form elements, and list system elements implemented in Magento.
- Describe the concept of Fieldsets.
- How can you render an element with a custom template?
Grids in Magento
- 69. Create a simple form and grid for a custom entity
- Which block class do Magento grid classes typically extend
- What is the default template for Magento grid instances
- How can grid filters be customized
- How does Magento actually perform sorting/paging/filtering operations
- What protected methods are specific to adminhtml grids, and how are they used
- What is the standard column class in a grid, and what is its role
- What are column renderers used for in Magento
- What is the role of the grid container class and its template
- What is the programmatic structure of mass actions
- app/design/adminhtml/default/default/template/sales/widget/grid.phtml (no such file)
- app/design/adminhtml/default/default/template/sales/widget/grid/container.phtml (no such file)
- 71. Define the basic terms, elements, and structure of system configuration XML
- 72. Describe system configuration scopes
- (Ad.1) How can elements in system configuration be rendered with a custom template
- (Ad.1) How does the structure of system.xml relate to the rendered elements in the System Configuration view
- (Ad.1) How can the CSS class of system configuration elements be changed
- (Ad.1) What is the syntax for specifying the options in dropdowns and multiselects
- (Ad.1) Which classes are used to parse and render system configuration XML
- (Ad.1) What is the syntax to specify a custom renderer for a field in system configuration
- (Ad.1) How does Magento store data for system configuration
- (Ad.1) What is the difference between Mage::getStoreConfig(...) and Mage::getConfig()->getNode(...)?
- (Ad.2) How do different scopes (global, website, store) work in Magento system configuration?
- (Ad.2) How does Magento store information about option values and their scopes?
- (Ad.1) Mage/Adminhtml/Model/System/Config/*
- (Ad.1) Mage/Adminhtml/Block/System/Config/*
- (Ad.2) core_config_data table
- (Ad.2) Mage_Core_Model_Core_Config_Data?
- (Ad.2) Mage_Core_Model_Mysql4_Config_Data
- (Ad.2) Mage_Core_Model_Mysql4_Config_Data_Collection
Access Control Lists (ACL) and permissions in Magento
- 73. Define/identify basic terms and elements of ACL
- 74. Use ACL to:
- 1. Set up a menu item
- 2. Create appropriate permissions for users
- 3. Check for permissions in permissions management tree structures
- For what purpose is the _isAllowed() method used and which class types implement it
- What is the XML syntax for adding new menu element
- What is adminhtml.xml used for? Which class parses it, and which class applies it
- Where is the code located that processes the ACL XML and where is the code that applies it
- What is the relationship between Magento and Zend_Acl
- How is ACL information stored in the database
Working with extensions in Magento
- 75. Describe how to enable and configure extensions
- 76. Define Magento extensions and describe the different types of extension available (Community, Core, Commercial)
- In which folders are Magento extensions files located
- Which files are necessary to make custom modules work
- How can module dependencies be manipulated
- What is the role of the downloader
- How can modules be installed through Magento Connect
7- Catalog - 10% of the exam.
- 77. Identify and describe standard product types (simple, configurable, bundled, etc.)
- 78. Create custom product types from scratch or modify existing product types
- 79. Identify how custom product types interact with indexing, SQL, and underlying data structures.
- Which product types exist in Magento
- Which product types are implemented as part of the Mage_Catalog module, and which are not
- What steps need to be taken in order to implement a custom product type
- How do the different product types handle price calculation
- Which indexing processes does the product type influence
- Which product types implement a parent-child relationship between product entities
- Which database tables are shared between product types, and which ones are specific to one product type
- 80. Identify basic concepts of price generation in Magento
- 81. Modify and adjust price generation for products (for example, during integration of third-party software)
- Under what circumstances are product prices read from the index tables?
- From which modules do classes participate in price calculation?
- Which ways exist to specify custom prices during runtime?
- How do custom product options influence price calculation?
- How are product tier prices implemented and displayed?
- Mage_Catalog_Model_Product::getPrice() and getFinalPrice()
- Mage_Catalog_Model_Product_Type_Price ::getTierPrice()
- 82. Describe the Category Hierarchy Tree Structure implementation (the internal structure inside the database), including:
- 1. the meaning of parent_id 0
- 2. the construction of paths
- 3. the attributes required to display a new category in the store
- How is the category hierarchy reflected in the database? Does it differ when multiple root categories are present?
- How is a catalog tree read from the database tables, with and without flat catalog tables enabled?
- How does working with categories differ if the flat catalog is enabled on a model level?
- How is the category parent id path set on new categories?
- Which methods exist to read category children and how do they differ?
- 82. Describe the Category Hierarchy Tree Structure implementation (the internal structure inside the database), including:
Catalog Price Rules
- 83. Identify how catalog price rules are implemented in Magento
- How are the catalog price rules related to the product prices?
- How are the catalog price rules stored in the database?
- 84. Choose optimal catalog structure (EAV vs. Flat) for a given implementation
- 85. Implement, troubleshoot, and modify Magento tax rules
- 86. Modify, extend, and troubleshoot the Magento layered("filter") navigation
- 87. Troubleshoot and customize Magento indexes
- 88. Describe custom product options in Magento
- When and how are the catalog flat tables updated when a product is modified?
- Which factors are used by the Mage_Tax module to apply the correct tax rate (or rates) to a product price?
- How can attributes with custom source models be integrated into layered navigation filtering?
- Which classes are responsible for rendering the layered navigation?
- Which indexes are used for the layered navigation?
- Which steps are needed to integrate a custom indexer into the framework offered by the Mage_Index module?
- How are custom product options stored on quote and order items?
- How can you specify custom product options on-the-fly on quote items?
- How are custom product options copied from quote to order items?
- How are custom product options processed when a product is added to the cart?
8- Checkout - 16% of the exam.
- 89. Describe how to modify and effectively customize the quote object, the quote item object, and the address object
- 90. Explain the database schema for total models
- (Ad.1) What is the quote model used for in Magento?
- (Ad.1) What is the shopping cart model used for in Magento?
- (Ad.1) How does Magento store information about the shopping cart?
- (Ad.1) How are different product types processed when added to the cart?
- (Ad.1) What is the difference between shipping and billing address objects in Magento? How is each used in the quote object?
- (Ad.1) What is the difference in processing quote items for onepage and multishipping checkout in Magento?
- (Ad.1) How does Magento process additional information about products being added to the shopping cart (custom options, components of configurable products, etc.)?
- (Ad.1) How do products in the shopping cart affect the checkout process?
- (Ad.1) How can the billing and shipping addresses affect the checkout process?
- (Ad.1) When exactly does inventory decrementing occur?
- (Ad.1) When exactly does card authorization and capturing occur?
- (Ad.2) What are total models responsible for in Magento
- (Ad.2) How you can customize total models
- (Ad.2) How can the individual total models be identified for a given checkout process
- (Ad.2) How can the priority of total model execution be customized
- (Ad.2) To which objects do total models have access in Magento, and which objects do they usually manipulate
- (Ad.2) Which class runs total models processing
- (Ad.2) What is the flow of total model execution
- (Ad.2) At which moment(s) are total models executed
- (Ad.1) Mage_Sales_Model_Quote
- (Ad.1,2) Mage_Sales_Model_Quote_Address
- (Ad.1) Mage_Sales_Model_Quote_Item
- (Ad.1,2) Mage_Sales_Model_Quote_Address_Item
- (Ad.1) Mage_CatalogInventory/etc/config.xml
- (Ad.1) Mage_CatalogInventory_Model_Observer
- (Ad.2) Mage/Sales/etc/config.xml
- (Ad.2) Mage/Tax/etc/config.xml
- (Ad.2) Mage_Sales_Model_Quote_Address_Total_Abstract
- (Ad.2) Mage_Sales_Model_Quote_Address_Total_Collector
- (Ad.2) Mage/Sales/Model/Quote/Address/Total/*
- (Ad.2) Mage/SalesRule/etc/config.xml
- (Ad.2) Mage_SalesRule_Model_Validator
Shopping Cart price rules
- 91. Describe how shopping cart price rules work and how they can be customized
- Which module is responsible for shopping cart price rules?
- What is the difference between shopping cart and catalog price rules?
- What are the limitations of Magento shopping cart rules?
Shipping and payment methods in Magento
- 92. Describe the programmatic structure of shipping methods, how to customize existing methods, and how to implement new methods
- 93. Describe the shipping rates calculation process
- 94. Describe the programmatic structure of payment methods and how to implement new methods
- How does Magento calculate shipping rates?
- What is the hierarchy of shipping information in Magento?
- How does the TableRate shipping method work?
- How do US shipping methods (FedEX, UPS, USPS) work?
- (Ad.3) How can payment method behavior be customized (for example: whether to charge or authorize a credit card; controlling URL redirects; etc.)?
- (Ad.3) Which class is the basic class in the payment method hierarchy?
- (Ad.3) How can the stored data of payment methods be customized (credit card numbers, for example)?
- (Ad.3) What is the difference between payment method and payment classes (such as order_payment, quote_payment, etc.)?
- (Ad.3) What is the typical structure of the payment method module?
- (Ad.3) Mage_Payment_Model_Method_Abstract
- (Ad.3) Mage_Payment_Model_Method_Cc
- (Ad.3) Mage_Payment_Model_Info
- (Ad.3) Mage/Paypal/*
- (Ad.3) Mage/PaypalUk/*
Magento multishipping implementation
- 95. Describe how to extend the Magento multishipping implementation
- 96. Identify limitations of the multishipping implementation
- How does the storage of quotes for multishipping and onepage checkouts differ
- Which quotes in a multishipping checkout flow will be virtual
- What is the difference in the multishipping processing for a quote with virtual products in it
- How can different product types be split among multiple addresses when using multishipping in Magento
- How many times are total models executed on a multishipping checkout in Magento
- Which model is responsible for multishipping checkout in Magento
9- Sales and Customers - 11% of the exam.
- 97. Describe order creation in the admin
- 98. Describe the differences in order creation between the frontend and the admin
- 99. Card operations (capturing and authorization)
- 100. Describe the order shipment structure and process
- 101. Describe the architecture and processing of refunds
- 102. Describe the implementation of the three partial order operations (partial invoice, partial shipping, and partial refund)?
- 103. Describe cancel operations
- Which classes are involved in order creation in the admin? What are their roles (especially the role of adminhtml classes)
- How does Magento calculate price when an order is created from the admin
- Which steps are necessary in order to create an order from the admin
- What happens when existing orders are edited in the admin
- What is the difference between order status and order state
- (Ad.99) Which classes and methods are responsible for credit card operations (for example authorization or capturing)
- (Ad.99) What is the difference between "pay" and "capture" operations?
- (Ad.99) What are the roles of the order, order_payment, invoice, and payment methods in the process of charging a card
- (Ad.99) What are the roles of the total models in the context of the invoice object
- (Ad.99) How does Magento store information about invoices
- (Ad.100) How shipment templates be customized?
- (Ad.100) How can different items from a single order be shipped to multiple addresses? Is it possible at all?
- (Ad.100) How does Magento store shipping and tracking information?
- (Ad.101) Which classes are involved, and which tables are used to store refund information?
- (Ad.101) How does Magento process taxes when refunding an order?
- (Ad.101) How does Magento process shipping fees when refunding an order?
- (Ad.101) What is the difference between online and offline refunding?
- (Ad.101) What is the role of the credit memo total models in Magento?
- (Ad.102) How do partial order operations affect order state?
- (Ad.102) How is data for partial operations stored?
- (Ad.103) What cancel operations are available for the various order entities in Magento (order, order item, shipment, invoice, credit memo)? Do all of them support cancellation?
- (Ad.103) How are taxes processed during cancel operations?
- (Ad.99,102,103) Mage_Sales_Model_Order_Invoice
- (Ad.99) Mage/Sales/Model/Order/Invoice/*
- (Ad.99,102,103) Mage_Sales_Model_Order_Payment
- (Ad.99) Mage_Payment_Model_Method_Info (or Mage_Payment_Model_Info ?)
- (Ad.99,102) Mage_Payment_Model_Method_Abstract
- (Ad.100,102,103) Mage_Sales_Model_Order_Shipment
- (Ad.100) Mage/Sales/Model/Order/Shipment/*
- (Ad.101,102,103) Mage_Sales_Model_Order_Creditmemo
- (Ad.101) Mage_Sales_Model_Order_Creditmemo/*
- (Ad.103) Mage_Adminhtml_Sales_OrderController
- 104. Describe the architecture of the customer module
- 105. Describe the role of customer addresses
- 106. Describe how to add, modify, and display customer attributes
- What is the structure of tables in which customer information is stored?
- What is the customer resource model?
- How is customer information validated?
- How can customer-related email templates be manipulated?
- What is the difference between shipping and billing addresses for a customer?
- How does the number of shipping and billing address entities affect the frontend interface for customers?
- How does customer information affect prices and taxes?
- How can attributes be added to a customer address? How are custom address attributes you converted to an order address?
- Can a customer be added to two customer groups at the same time?
- Mage_Customer_Model_Customer_Address (or rather Mage_Customer_Model_Address)
10- Advanced features - 13% of the exam.
WidgetsThis topic comprises approximately 13% of the exam. Items are drawn randomly from the following topics and objectives:
- 107. Create frontend widgets and describe widget architecture
- What classes are typically involved in Magento widget architecture?
- How are admin-configurable parameters and their options specified?
- 108. Use the Magento API to implement third party integrations
- 109. Extend the existing Magento API to allow for deeper integrations into third party products
- 110. Describe the different Web Service APIs available within the Magento Core
- 111. Describe the advantages and disadvantages of the available Web Service APIs in Magento
- 112. Identify the configuration files used for the v2 SOAP API
- 113. Describe the purpose of the configuration files related to the API
- What are the syntactical differences between API versions?
- How is the final WSDL composed? How can it be customized?
- How are existing methods overwritten? How can additional methods be added?
- 114. Integrate Google features (Google Wallet, Checkout, Adwords, Analytics) into Magento implementation
11- Enterprise Edition - 9% of the exam.
- 115. Describe how to customize, extend, and troubleshoot Enterprise Edition catalog target rules
- What additional possibilities does the Enterprise target rule module provide over the Mage_CatalogRule?
- How does the module store the rules in the database?
- Which indexer processes the rules, and how is the index used to realize faster reads?
- 116. Describe how to customize, extend, and troubleshoot the Enterprise Edition reward point system
- How do the features offered by the reward point system hook into other Magento modules?
- Under which conditions may reward points be assigned?
- Which steps are required to add new custom options to assign reward points?
- Enterprise_Reward_Model_Reward_Rate::calculateToCurrency() and calculateToPoints()
- 117. Describe how to implement, customize, and troubleshoot Enterprise Edition website restrictions
- How does the website restrictions module determine which pages are accessible without authentication?
- How does the module prevent visitors from accessing restricted website content?
- 118. Identify the elements and functioning of Enterprise Edition Full Page Cache
- How does the full page cache module hook into the request flow and serve page requests from the cache?
- What is the difference between the applyWithoutApp() and applyInApp() methods of the abstract?
- What is the role of each node in the cache.xml configuration file?
- Which steps are necessary to implement a gynamically rendered block inside an otherwise fully cached page?
- 119. Describe the Payment Bridge
- How is the Payment Bridge implemented and configured?
12- Challenge Questions - 8% of the exam
- Approximately 8% of the Magento Certified Developer Plus exam consists of Challenge questions, randomly drawn from the objectives covered in the individual sections of this Study Guide. The Challenge questions go into more detail or cover move complex areas of the topic than the questions in the other sections of the Magento Certified Developer Plus exam.