AEM Interview Questions

1. Explain AEM Architecture.

Platform JAVA
Because Adobe Experience Manager (AEM) is a Java web application, it requires a Java Runtime Environment on the server (JRE). JRE 1.6 is required, although JRE 1.7 is highly recommended.
Granite Worktop

Adobe's open web stack is called Granite. It is the technical foundation upon which AEM is constructed.

FRAMEWORK FOR OSGI

OSGi is a Java-based dynamic software component system. An application on an OSGi-based system is made up of a collection of components, referred to as bundles in OSGi, that may be dynamically installed, started, paused, and uninstalled during runtime without having to restart the entire application. Bundle administration is available in a running AEM instance via the AEM Web Console at http://:/system/console/bundles.

ENGINE FOR SERVLETS

The built-in CQSE servlet engine runs as a service in a quickstart installation.

a bundle that is part of the OSGi framework The handling of servlets in a war file installation is assigned to a third-party application server. When AEM is deployed via the standalone quickstart jar file, it comes with a built-in servlet engine (CQSE), which operates as a bundle within the OSGi framework.

REPOSITORY OF JCR CONTENT

The built-in CRX content repository, which is an implementation of the Java Content Repository Specification, stores all data in AEM (JCR).

AEM's built-in content repository stores all of the data.

CRX is the name of the AEM repository.

Adobe's implementation of the Content Repository Specification for Java Technology 2.0, also known as JSR-238, is an official standard released by the Java Community Process (version 1.0 was known as JSR-170)

DELIVERY OF SLING CONTENT

AEM is an acronym for

developed with Sling, a REST-based Web application framework that makes developing content-oriented apps simple. Sling's data is stored in a JCR repository, such as Apache Jackrabbit or, in the case of AEM, the CRX Content Repository. The Apache Software Foundation has accepted Sling as a contribution.

Modules for AEM

Adobe Experience Manager is built on the Granite platform and runs on top of the OSGi framework. WCM, DAM, Workflow, and other AEM modules are examples.

2. What is the difference between CQ5 and AEM?

AEM 6.1/6.0's significant tech stack updates.

1. Jackrabbit Oak: Oak outperforms JCR in terms of performance and scalability. To allow clustering and user-generated data situations, you can alternatively use a NoSQL database like MongoDB as the persistence layer.

2. Attractive: A new templating language that makes markup seem nice, enforces the separation of markup and logic, and by default protects against XSS.

3. Touch UI: CQ5's ExtJS-based Classic UI has been upgraded to Touch UI, which supports touch-enabled devices and is created with the Coral UI framework.

4. Search - Apache Solr: Lucene was the default search engine in CQ5, however, it has been replaced by Solr. The Solr server can now be used as the search engine for your AEM application.

3. What is new in AEM 6.2?

Adobe Experience Manager 6.2 is an upgrade to the code base of Adobe Experience Manager 6.1. It adds new and improved features, as well as critical customer fixes, high-priority customer enhancements, and general bug fixes geared toward product stability. It also includes all feature packs, hotfixes, and service packs for Adobe Experience Manager 6.1.

An overview is provided in the table below.

Features of Security

Support for password history has been added.

Authentication token expiration can be customized.

Continual effort: Sling login administrative API usage has been switched to Service Users in many places of the product.

The following are the main enhancements to the repository:

MongoDB Enterprise 3.2 is supported.

Enhancements to TarMK's cold standby to provide a procedural failover for high availability.

Faceted Search, Suggestions, Spellchecker, and other Oak search innovations

In terms of performance, scalability, and resilience, general.

Support for Revision Cleanup (Offline revision cleanup is the recommended way of performing revision cleanup)

The 2016 Adobe Marketing Cloud UI design is implemented in AEM 6.2. (also known as Shell 3). Furthermore, the user interface is transitioning from Coral UI 2 to the Coral 3 UI framework, which is based on Web Components.

"Explain Query" on the Operations Dashboard provides insight into the mechanics of your queries to aid diagnosis and optimization.

In the Tools/Operations section, specific repository features can be monitored using a configurable timeline view.

The Status.zip file in the Tools/Operations/Diagnosis section now contains a configurable series of Java thread dumps.

User Sync Diagnostics are used to ensure that users and groups are consistent across AEM instances.

Distribution of Content:

Replication of packages to support extra-large activation volumes

Configure priority-queuing to Allow for a divide between urgent and backlog activations.

The Status.zip file in the Tools/Operations/Diagnosis section now contains a configurable series of Java thread dumps.

Advanced notifications and auto-unlocking of stalled replication queues.

4. What is new in AEM 6.3?

Adobe Experience Manager 6.3 is a patch for Adobe Experience Manager 6.2. It adds new and improved features, as well as critical customer fixes, high-priority customer enhancements, and general bug fixes aimed at product stability. All feature packs, hotfixes, and service packs for Adobe Experience Manager 6.2 are included.

Cleaning Up Your Revisions on the Internet

Section of Oak TarMK is a new Tar file format that optimizes runtime and maintenance. It claims to be faster than TarMK and to fully allow online revision cleanups. Anyone who has worked with AEM to automate cloud processes will appreciate this last point. There will be no need to shut down an instance to perform repository compaction and cleanup.

As part of the maintenance chores, it is now scheduled to run regularly.

Maps of activities

The AEM Sites Activity Map interface, which was introduced in AEM 6.3, allows the Adobe Analytics Activity Map to display analytics data directly on the AEM Sites page, allowing AEM Authors to see how their pages are used down to the link level. more

Workflow in bulk

Faster workflow-related tasks and the capacity to handle numerous things with one click have increased productivity.

Export Sling Models

In Sling Models v1.3.0, the Sling Model Exporter was introduced. This new feature allows users to add new annotations to Sling Models that specify how the model should be exported as JSON.

Define a resource Type using the @Model annotation to tie the exporter framework to a Sling model.

and provide the Jackson exporter as well as the Sling extension using the @Exporter annotation (and optionally the selectors). It's also possible to utilize Jackson annotations to change the model's JSON representation.
Integration with Livefyre

Adobe purchased Livefyre in May 2016 and has now incorporated it as a set of components, as well as a user-generated content ingestion and moderation panel, into Adobe Experience Manager. Once a Livefyre cloud service configuration is set up, content creators can use components (found in /libs/social/integrations/livefyre/components) to surface user-generated content from social networking sites like Twitter and Instagram on a page. Traditional branded experiences combined with social media content will show to be an efficient strategy to increase client engagement. The usage of A separate Assets and Livefyre license is required for Livefyre, however, a Communities license is not required.