The below questions are more inclined towards Admin and configuration of the AEM instance. You might also be aware of these while giving an AEM profile based interview as this skill-set is basically an add-on to the developer and gives a good insight of your capability. I have written the specific answer which you need to say to the interviewer , for explicit details please go ahead and read the link given and explore more in details.
Q1 ) How will u give the privilege to user for uploading dam assets
Go to user admin console. Double click on the user/group name.
Give read, write , modify permissions on “/content/dam” node.
Q2) What is the process to upload jar (bundle) file through felix console
Go to felix console “http://localhost:4502/system/console“. It will automatically open the bundles page. On the same page there is an option to selct and upload a file (right side). From there we can upload the jar file.
Q3) What is the process to create a user / group
Go to user admin console. Click on the create user/group button in the left panel. A dialog box will open up.In this dialog bo enter the values for the fields. User/Group will be created. Now double click on the newly created user/group to assign permissions.
Q4 ) Is it possible to have user without any group
Yes ,this is possible but not advisable. If you do so you will have to manage permissions for each user at user level. But if you add multiple users to a same group then permissions can be managed at group level not user level.
Q5 )What is the process to give privilege to a user for creating more user(s)
Give read, write, create, modify permissions at /home/users node. This node is the place where all the users are stored.
Q6 )Can we restrict for certain users not to display some digital assets
Yes. Go to the user admin console. And deny read permissions for that particular user at the required dam path. E.g /content/dam/images/imageX.
Q7) What is the role of dispatcher and how you have to used rewrite URL?
What is it?
The Dispatcher is the Adobe caching and/or load balancing tool that helps realize a fast and dynamic Web authoring environment. It is a CQ5 tool for caching and load-balancing.
- For caching, the Dispatcher works as part of an HTTP server, such as Apache, with the aim of storing (or “caching”) as much of the static website content as possible and accessing the website’s layout engine as infrequently as possible.
- In a load balancing role, the Dispatcher distributes user requests (load) across different clustered CQ instances (renders).
- For caching, the Dispatcher module uses the Web server’s ability to serve static content. The Dispatcher places the cached documents in the document root of the Web server.
Dispatcher has 2 Responsibilities
- Caching – To cache as much content as possible, so that it doesn’t need to access layout engine frequently for generating content dynamically.
- Load-balancing – To increase the performance by load-balancing.
Dispatcher uses 2 main Strategies for Caching.
- Cache as much content as possible as static pages.
- Accessing layout engine (publish) as little as possible.
Note : The Dispatcher uses a Cache Directory for caching static content. The cached documents are created in the root of a web-server.
Q8)What is the purpose of farm file
The farm file contains a series of single-valued or multi-valued properties that control the behavior of Dispatcher. In farm files you can define “allow” and “deny” rules specific to your application, set client headers etc, path for vhost file. Each entry in
/farms describes a separate server that can provide content; requests are routed to the servers by the dispatcher.
Q9) How to achieve reverse replication & Where it is used frequently ?
Consider the scenario where your website is having a blog or a forum, and the users are posting comments in the blog. Then that comments will only be in publish instance. The content is moved from publish instance to author instance using reverse replication and the job is done by reverse replication agent.
The reverse replication agent places any content updates in an outbox configured in publish instance. The replication listeners in author environment keep listening to the publish outbox and whenever any content is placed in publish outbox, the listeners update the content in author instance.
Q10 )How do I synchronize LDAP and CQ users?
What is it?
LDAP (the Lightweight Directory Access Protocol) is used for accessing centralized directory services. This helps reduce the effort required to manage user accounts as they can be accessed by multiple applications. User accounts can be synchronized between the LDAP server and CRX, with LDAP account details being saved in the CRX repository. This allows the accounts to be assigned to CRX groups for allocating the required permissions and privileges.
CRX uses LDAP authentication to authenticate such users, with credentials being passed to the LDAP server for validation, which is required before allowing access to CRX. To improve performance, successfully validated credentials can be cached by CRX; with an expiry timeout to ensure that revalidation does occur after an appropriate period.
When an account is removed from the LDAP server validation is no longer granted and so access to CRX is denied. Details of LDAP accounts that are saved in CRX can also be purged from CRX.
Use of such accounts is transparent to your users, they see no difference between user and group accounts created from LDAP and those created solely in CRX.
Read More LDAP related FAQs
Q11 )How do I configure and connect to a JDBC DataSource?
This is very well explained in the link : http://helpx.adobe.com/cq/kb/HowToConfigureSlingDatasource.html
Q12 )What is clustering in CQ5? How to configure that ?
Clustering is basically used for synchronization of data. Clustering enables multiple repository instances running on separate machines to be joined together to act as a single repository. When a write operation updates the data in one cluster node, that change is immediately and automatically applied to all other nodes in the cluster. This guarantees that any subsequent read from any cluster node will return the same updated result.
Q13 ) How can you move content from one Server to another ?
There are multiple ways:
1. You can create package from source server and install it to target server.
2. You can configure replication agent to point to second server and then replicate the content.