Magento MCQ Questions

Correct rewrite xpath in config.xml: <config><global><blocks><catalog><rewrite><product_view>Namespace_Module_Block_Product_View</product_view></rewrite></catalog></blocks>. Format: <module_group><rewrite><block_name>New_Class</block_name>. Replaces catalog/product_view block with custom class. Block rewrite system. Class name format matters. Config-based class replacement.

Category product assignment: Via category edit > Products in Category tab. Or product edit > Categories tab. Stored in catalog_category_product table. Many-to-many relationship. Position controls sort order. Category filter in layered navigation. Product categorization. Category-product link.

Magento helpers are created through Mage::helper(), which returns a singleton, so a helper keeps its state for the rest of the request.

Custom shipping carrier: Model extending Mage_Shipping_Model_Carrier_Abstract (M1) or CarrierInterface (M2). Implement collectRates(), getAllowedMethods(), isTrackingAvailable(). Configure in system.xml. Register in config. Calculate rates based on destination, weight, price. Shipping rate calculation. Carrier implementation.

XML-RPC is a remote procedure call protocol: it encodes each call in XML and sends it over HTTP. Magento 1 offered its web API over XML-RPC as well as SOAP.

Default cookie lifetime is 3600 seconds (1 hour). Configured in System > Configuration > Web > Session Cookie Management. 'Cookie Lifetime' setting controls duration. 0 means session cookies (expire when browser closes). Affects user sessions, shopping cart persistence. Security consideration - shorter more secure. Balance with user experience. Different from persistent shopping cart settings.

Magento cron functionality: Scheduled task execution. Configured in crontab.xml. Schedule expression format: * * * * * (minute hour day month weekday). Indexing, sitemap generation, emails, cleanup. Requires system cron calling cron.php. Job status tracking. Automated maintenance. Background processing.

Setting 'Manage Stock' to 'No' shuts off inventory management for specific products. Found in product edit under Inventory tab. When disabled, product always shows in stock. Quantity field ignored. Useful for services, digital products, or items with unlimited availability. Can set globally in System > Configuration > Inventory or per-product. Disables all inventory tracking features.

Best way to add XML settings for store frontend is creating local.xml file in app/design/frontend/[package]/[theme]/layout/local.xml. Override layout without modifying core files. All customizations in one file. Loads last, highest priority. Update-safe approach. Alternative: custom module layout XML. local.xml standard for theme-specific changes. Follows Magento best practices.

Module dependency declaration: In config.xml under <depends><Module_Name />. Controls loading order. Ensures dependencies load first. Required for class references, observers. Module interdependencies. Load sequence control. Proper initialization order.

EAV in Magento stands for Entity-Attribute-Value. Database design pattern for flexible attributes. Data spread across multiple tables. Entities (products, customers), Attributes (properties), Values (data). Enables custom attributes without schema changes. More complex queries. Used for products, categories, customers. Flexibility at cost of performance. Core of Magento's data model.

Flush Magento Cache clears Magento-specific cache (layouts, blocks, configuration, translations). Flush Cache Storage clears entire cache backend storage (all data including non-Magento if shared). Flush Magento Cache = selective. Flush Storage = complete wipe. Cache Storage affects full cache system. Different scope of clearing.

When creating new product, first choose Attribute Set. Determines which attributes apply to product. Default 'Default' set has standard attributes. Different sets for different product types (clothing, electronics, etc.). Affects available fields in product form. Must select before product type. Attribute set defines product data structure. Can change later but may lose data.

Rule for working with Magento's base package: Never modify base package directly. Always create custom theme/package. Base serves as fallback. Modifications lost during updates. Use local code pool for customizations. Extend rather than edit. Best practice for upgrade compatibility. Preserve core integrity. Create derivatives for customization.

Frontend Block is PHP class that prepares data for template rendering. Extends Mage_Core_Block_Template or Abstract. Located in [Module]/Block/. Methods provide data to .phtml templates. Accesses models, helpers. Template path configured in layout XML. Example: product block provides product data. Separates business logic from presentation. MVC view component.

In layout XML the head block's addJs action adds a file from the js/ folder, for example <action method="addJs"><script>jquery/jquery.js</script></action>.

Inject custom block via layout.xml: Within appropriate handle, use <reference name='container_name'><block type='module/block_class' name='unique_name' template='path/to/template.phtml' /></reference>. Reference targets existing container (content, left, right). Block type follows module/class naming. Template path relative to theme template directory. Layout XML block injection. Block placement method.

Best way to store session values: Use appropriate session singleton - Mage::getSingleton('core/session') for general, 'customer/session' for customer data, 'checkout/session' for cart/checkout. Methods: setData($key, $value), getData($key). Namespace prevents collisions. Persistent across requests. Use correct session context. Session best practices.

In <block type='A/B'>, A/B means module group alias and block class name. A = module identifier (e.g., 'catalog', 'cms'). B = block class within module (e.g., 'product_list'). Maps to class: Mage_A_Block_B. Config.xml defines block group under <blocks><a><class>. Example: 'catalog/product_list' = Mage_Catalog_Block_Product_List. Block class alias notation.

subtotal is in the currency the customer sees, and base_subtotal is in the store's base currency.

Observer classes need no base class or interface; Magento just calls the configured method and passes it a Varien_Event_Observer.

For order to progress from Pending to Processing state, create Invoice. Sales > Orders, select order, click Invoice button. Invoicing captures payment (if not already captured) and marks order as processing. Represents payment request or confirmation. Required step before shipment in many workflows. Automatic in some payment methods. Manual for offline payments. Triggers status change.

Setting 'Visibility' determines product display locations. Options: Not Visible Individually (shows in search but not catalog), Catalog (category only), Search (search only), Catalog/Search (both). Configure in product edit page under General tab. Search visibility controlled separately from catalog visibility. Allows products in cart/bundle but not browsable standalone.

Difference between Simple and Virtual Product: Simple products are physical items requiring shipping (books, clothing). Virtual products are non-physical, no shipping needed (services, downloads, warranties). Virtual products skip shipping steps in checkout. Both are base product types. Inventory and pricing work same way. Distinction affects fulfillment process.

Best way to create global variables: Use Mage::register('variable_name', $value) then Mage::registry('variable_name') for retrieval. Request-scoped storage. Alternative: static class property, helper singleton with properties. Avoid true globals. Registry for temporary data sharing. Mage::unregister() to clean up. Global data pattern.

Data upgrade scripts live in the module's data folder and are named data-upgrade-<from>-<to>.php, for example data-upgrade-0.0.1-0.0.2.php.

Layouts in Magento define page structure and content blocks. XML files in app/design/frontend/[package]/[theme]/layout/. Control which blocks appear where. Handle-based system matches pages. Add CSS/JS references. Set template files. Update types: add, remove, reference, block actions. Separate structure from presentation. Enable theme customization without PHP. Central configuration for page building.

Recommended way to override/extend Magento core: (1) Observers for events - least invasive. (2) Plugins/interceptors (Magento 2) or class rewrites (Magento 1). (3) Preference/DI for class substitution. Never edit core files directly. Use local code pool or custom modules. Preserve upgradeability. Event system preferred. Extension best practices.

Make frontend changes in your own package and theme (frontend/[package]/default), not in base/default, so upgrades don't overwrite them.

Product attribute frontend input types: text, textarea, date, boolean, multiselect, select, price, weight, media_image, gallery, etc. Each type has specific behavior. Dropdown uses select. Multiple choice uses multiselect. Determines admin interface and frontend display. Attribute configuration. Input type options.

Purpose of Grouped Product is to display multiple related simple products together as a set. Customers buy products separately from group. Each has own add-to-cart. Quantity controlled per item. Example: matching furniture set, computer components. Presents products together while maintaining separate inventory. Related item presentation. Items can be purchased individually or together.

The setting 'Visible on Product View Page on Front-end' determines that attribute value shows on product page. Configure in: Catalog > Attributes > Manage Attributes. Edit attribute, set frontend properties. Controls attribute display. Can be visible to customer or hidden. Label and formatting options. Display configuration per attribute.

Correct way to add CSS and JS in Magento is through layout XML files using <action> tags with addCss and addJs methods, or in theme's local.xml. Avoids hardcoding in templates. Maintains separation of concerns. Example: <action method='addJs'><script>script.js</script></action>. Best practice for asset management. Theme-specific customization without core modifications.

After adding new store via System > Manage Store, add to .htaccess: SetEnvIf Host ^www\.newdomain\.com$ MAGE_RUN_CODE=new_store_code followed by SetEnvIf Host ^www\.newdomain\.com$ MAGE_RUN_TYPE=store. Alternatively for website: MAGE_RUN_TYPE=website. Place before RewriteRule. Enables multi-store from single codebase. Domain-based store switching. Apache server configuration method.

Invoice capture() method captures payment from gateway and creates transaction. Updates invoice state to 'paid'. Processes actual payment collection. Invoice pay() method only changes invoice state to 'paid' without gateway communication. Used for offline payments or when payment already captured. capture() includes financial transaction; pay() is state change only. Different use cases.

PCI DSS compliance means your systems meet the card industry's rules for keeping cardholder data secure.

Cart items made from recurring-profile products are called nominal items, and Magento handles them separately from normal items.

A SOAP message is an XML envelope containing an optional header and a body, sent in an HTTP POST.

CRUD stands for create, read, update and delete.

base_grand_total is in the store's base currency, while grand_total is in the currency the order was placed in.

Newsletter template variables: {{var subscriber.email}}, {{var subscriber.name}}, {{store url=''}}, {{var logo_url}}. Custom variables via insert variable dropdown. HTML email formatting. Personalization tokens. Email template system.

Composite products (configurable, grouped and bundle) are built from existing products that the shopper configures before buying.