Page: 1
/ 14
Total 50 questions
Adobe AD0-E134 Adobe Experience Manager Sites Developer Exam Practice Test
Question 1
A customer is having trouble with some search queries and provides the following information:
* The logs show the following warning occurs many time: WARN* Traversed 1000 nodes with filter Filter (query=select...)
* The client has more than 100,000 stored in their AEM instance
* The client uses a custom page property to help search for pages of a given type
What should the AEM Developer do to help resolve the client's issue?
Answer : A
The warning WARN* Traversed 1000 nodes with filter Filter (query=select...) indicates that the query is performing a traversal instead of using an index. This results in poor performance, especially when the client has a large number of nodes (e.g., more than 100,000).
To resolve this issue, you should create a custom Oak index for the custom page property. This ensures that the queries can leverage the index for efficient data retrieval.
Steps to create a custom Oak index:
Define the Oak Index:
Navigate to the /oak:index node in CRXDE Lite (http://localhost:4502/crx/de).
Create a new node of type oak:QueryIndexDefinition.
Configure the Index:
Set the properties of the new index node to define the indexing rules for the custom page property.
{
'jcr:primaryType': 'oak:QueryIndexDefinition',
'type': 'property',
'propertyNames': ['customPageProperty'],
'reindex': true,
'async': 'async'
}
Deploy and Reindex:
Save the changes and initiate a reindexing process.
Ensure that the reindex flag is set to true for the newly created index.
Validate the Index:
Use the Index Manager or the AEM Web Console to validate that the new index is enabled and functioning correctly.
By creating a custom Oak index for the custom page property, the queries will be optimized to use the index, significantly improving the search performance and resolving the client's issue.
Question 2
A developer is using sling context-aware configuration trying to get the configuration resource using:
This works as intended in author and in publish when logged in lo publish as admin. However this gives a null when run as anonymous. Which method is going to fix the issue?
Answer : A
The issue arises because the anonymous user does not have the necessary read permissions for the /content directory. When using Sling context-aware configurations, access to the configuration resource is required. If the anonymous user lacks read permissions, the configuration cannot be retrieved, resulting in a null value.
To fix this issue, you need to grant read permissions to the anonymous user for the /content directory.
Steps to apply read permissions:
Access CRXDE Lite: Log into your AEM instance and navigate to CRXDE Lite (http://localhost:4502/crx/de).
Navigate to the /content Directory: In the CRXDE Lite interface, browse to the /content directory.
Set Permissions:
Right-click on the /content directory and select 'Permissions'.
Add the anonymous user (if not already present).
Grant read permissions to the anonymous user.
Save Changes: Apply the changes and ensure that they are saved correctly.
Test the Configuration: Log out of the AEM instance and test the context-aware configuration as an anonymous user to ensure that the configuration resource can now be retrieved.
By granting read permissions to the anonymous user for the /content directory, you allow access to the necessary configuration resources, resolving the issue.
Question 3
A developer needs to create an OSGI service that is able to read a list of spoken languages from the configuration of the service. The configuration file tanguageServicelmplefgjson' already exisls:
Which snippet should the developer use lo read the OSGi configurations?
A)
B)
Answer : B
To read a list of spoken languages from the configuration of an OSGi service, the correct snippet to use is Option B. This snippet demonstrates how to define and read the configuration properties using the OSGi R7 annotations (@ObjectClassDefinition and @AttributeDefinition), which are the recommended way for defining OSGi configurations in modern AEM projects.
Here is the detailed explanation of the snippet:
Option B Snippet Explanation:
Component Definition:
@Component(
service = { LanguageService.class }
)
@Designate(ocd = LanguageServiceImpl.Config.class)
public class LanguageServiceImpl implements LanguageService {
This defines an OSGi component and designates a configuration class for it.
Configuration Interface:
@ObjectClassDefinition(
name = 'Sample - Language Service',
description = 'OSGi Service providing information about languages'
)
@interface Config {
@AttributeDefinition(
name = 'Sample Languages',
description = 'List of spoken languages'
)
String[] languages() default { 'English', 'Japanese' };
}
This defines the configuration interface with annotations to describe the configuration properties. The languages attribute is defined with a default value of {'English', 'Japanese'}.
Activate Method:
private String[] languages;
@Activate
protected void activate(Config config) {
this.languages = config.languages();
}
The activate method reads the configuration values and assigns them to the instance variable languages when the service is activated.
Here is the complete Option B code:
@Component(
service = { LanguageService.class }
)
@Designate(ocd = LanguageServiceImpl.Config.class)
public class LanguageServiceImpl implements LanguageService {
@ObjectClassDefinition(
name = 'Sample - Language Service',
description = 'OSGi Service providing information about languages'
)
@interface Config {
@AttributeDefinition(
name = 'Sample Languages',
description = 'List of spoken languages'
)
String[] languages() default { 'English', 'Japanese' };
}
private String[] languages;
@Activate
protected void activate(Config config) {
this.languages = config.languages();
}
// Additional methods to use the languages array
}
By using this approach, you ensure that your OSGi service can dynamically read and use the list of spoken languages specified in its configuration, making it adaptable to different environments and requirements.
OSGi R7 Annotations
Question 4
Where should an AEM Developer add a front end dependency?
Answer : C
An AEM Developer should add a front-end dependency in the package.json file. The package.json file is a standard configuration file for managing dependencies in JavaScript projects, including those using npm or Yarn as package managers.
Here's how to add a front-end dependency:
Open the package.json File: This file is typically located at the root of your project.
Add the Dependency: Add the required front-end dependency under the dependencies or devDependencies section. For example, to add lodash as a dependency:
{
'name': 'my-aem-project',
'version': '1.0.0',
'dependencies': {
'lodash': '^4.17.21'
}
}
Install the Dependency: Run the following command to install the new dependency:
npm install
Verify Installation: Ensure that the dependency has been added to the node_modules directory and is listed in the package-lock.json file.
The package.json file is the central place to manage all front-end dependencies, making it easy to track, update, and share dependencies across the development team.
Managing Dependencies in AEM Projects
These steps ensure that the front-end dependencies are managed efficiently and consistently within the AEM project.
Question 5
Which OSGi configuration values can be used in an AEM as a Cloud Service Implementation?
Answer : D
In AEM as a Cloud Service, the OSGi configuration values that can be used include Inline, secret, and environment-specific. These configurations provide flexibility and security for managing environment-specific settings and sensitive information.
Inline Configurations: Inline configurations are directly embedded within the code and are typically used for straightforward configurations.
Secret Configurations: Secret configurations are used to securely store sensitive information, such as passwords and API keys. These configurations are managed separately to ensure security.
Environment-Specific Configurations: Environment-specific configurations allow you to tailor settings for different environments (e.g., development, staging, production) without changing the underlying codebase.
Example of using these configurations:
Inline Configuration:
{
'service.url': 'https://api.example.com'
}
Secret Configuration: Managed through Adobe IMS and not directly embedded in the code.
Environment-Specific Configuration:
{
'runmode': 'dev',
'service.timeout': '30'
}
Question 6
What is the recommended path to override /libs standard functionality?
Question 7
A development team is starting a new AEM project that is going to integrate with the Adobe Commerce platform. The developer needs to create a new AEM project using the Maven command line interface.
How can the 'mvn -B archetype:generate' command help the developer with the integration between AEM and Adobe Commerce?
All Official Question Types