1. What is MSM in AEM?
MSM stands for Multi Site Manager, and it helps manage multiple related websites by maintaining a common structure and content, from the blueprint, while allowing country-specific or language-specific changes.
Example:
A multinational company may have websites for different countries. These websites can share common content and structure, but have country-specific information.
For example:
- USA website displays prices in US Dollars.
- UK website displays prices in British Pounds.
- European website displays prices in Euros.
2. What is a Live Copy in AEM?
A Live Copy is a copy of a Blueprint or source website that maintains a relationship with the original content.
For example, a multinational company may have a master website as blueprint and create Live Copies for the USA, UK, and European websites.
The Live Copies share common content and structure from the Blueprint, but they can also contain country-specific or language-specific content.
If any changes are made to the Blueprint, those changes can be synchronized with the Live Copies using the Rollout process.
3. What is AEM Replication?
AEM Replication is the process of transferring content from one AEM instance/environment to another.
For example, an Author can replicate a page from the Author instance to the Publish instance. Replication can also be used to deactivate (unpublish) content from the Publish instance.
A QA validates and verifies the contents in the publish instance through replication when a page is published or unpublished.
4. What is Cache Invalidation?
Cache invalidation is the process of clearing or updating cached content so that users receive the latest contents on the webpage.
Example:
Suppose a product discount changes from 10% to 20%. If the Dispatcher cache is not invalidated, users might still see the old 10% discount.
Cache invalidation ensures that the outdated cached content is removed so that users can see the updated 20% discount.
5. What is the difference between Dispatcher Cache and Browser Cache?
Dispatcher Cache:
Dispatcher Cache is on the server side, ie, it is shored on the server side. It reduces requests to the AEM Publish instance by serving content directly from the Dispatcher cache whenever a valid cached response is available.
If the requested content is not available in the cache, the request is forwarded to the Publish instance. This cache can be cleared through Dispatcher cache invalidation.
Browser Cache:
Browser Cache is on the user's side, stored in the user's local browser. It stores resources such as images, CSS, JavaScript files, and other website resources.
It reduces repeated requests to the server by reusing cached resources whenever they are still valid. This cache can be cleared through the browser settings or developer tools and is specific to the user's browser.
6. What is Impersonation in AEM?
It is the process of one user acting as another user with the second user's permissions and access rights.
It is used when the first user needs to access the system from the second user's perspective for troubleshooting, debugging, or investigation.
Example: An Admin can impersonate an Author to see which pages, components, and features the Author can access, in order to investigate or troubleshoot issues.
7. What is a Sitemap in AEM?
A sitemap is an XML file that contains the important URLs of a website. It helps search engines like Google discover and crawl the website's pages.
Example:
https://example.com/sitemap.xml
This XML file might contain the following URLs:
- https://example.com/laptops
- https://example.com/mobiles
- https://example.com/monitors
When a search engine crawls the website, it can use the sitemap to discover these pages.
A QA might test:
- The site map is available or exists
- The sitemap contains the correct URLs.
- The URLs work as expected.
- The Unpublished or deleted pages are removed.
- No pages return 404 error.
- If any URL is changed and if the user enters the old URL, it should take to the new URL.
8. What is a Canonical URL?
A Canonical URL is the preferred URL of a webpage that tells search engines which URL to consider as the primary version when multiple URLs have similar or duplicate content.
Example:
The same Dell laptop page might be accessible through:
In this case, the website can specify https://example.com/laptops/dell as the Canonical URL.
This helps search engines avoid duplicate content issues and confusion.
Note: the Canonical URL is the recommended URL for the search engine. But the search engine might select the recommended URL or a different URL.
No comments:
Post a Comment