A developer identifies that some requests for the page /content/sampleproject/page.html take longer that other requests for the same page. Refer to the
$DOCROOT/content/sampleproject directory below.
The dispatcher.log file contains the following lines:
How should the developer make sure that the page is always cached?
To ensure that the page is always cached, the developer should modify the dispatcher.any file to allow caching even when there are query string parameters present in the request. Option D shows the correct modification where the property /ignoreUrlParams is set to [*]. This tells the dispatcher to ignore all query string parameters when deciding whether to cache the page, thereby ensuring that the page is always cached.
A developer creates a Sling Servlet. The Sling Servlet is bound to a path (/service/sling/sample). Refer to the resulting code below.
What should the developer do to make the servlet access controlled using the default ACLs?
To make the Sling Servlet access controlled using the default ACLs, a developer should use @SlingServletResourceTypes instead of @SlingServletPaths. Using @SlingServletPaths bypasses the default ACL security checks on content resources, while @SlingServletResourceTypes ensures that the servlet adheres to the access control defined in the repository, making it aligned with the default ACL permissions.
A developer wants to extend AEM Core Components to create a custom Carousel Component.
How should the developer extend the Core Components?
To extend AEM Core Components and create a custom Carousel Component, developers should use the sling:resourceSuperType property to point to the core component. This approach allows for the inheritance of functionalities from the core components while still enabling customization. Making changes to the original component, copying it, or using sling:resourceType are not appropriate methods for extending core components in AEM.
A developer wants to change the log level for a custom API.
Which OSGi configuration should the developer modify?
To change the log level for a custom API in an OSGi environment, the appropriate configuration to modify is the Apache Sling Logging Configuration. This configuration allows developers to adjust the log levels for specific packages or classes, providing the necessary control over logging output. The other options, such as Apache Sling Log Tracker Service, Apache Sling Logging Writer Configuration, and Adobe Granite Log Analysis Service, do not directly relate to setting log levels for a custom API.
Refer to the following four Client Library Folders.
A developer uses the following:
What is the resulting HTML?
A.
B.
C.
D.
When the developer uses <data-sly-call="${clientlib.css @ categories='library.one'}"/>, it will include the CSS files for 'library.one' and its dependencies. 'library.one' has dependencies 'library.three' and 'library.four', which means their CSS files will also be included. The order in which libraries are included is based on their dependencies. Hence, 'library.four' (being a dependency of 'library.three') will be included first, then 'library.three', and finally 'library.one'. Therefore, the resulting HTML will be: <link rel="stylesheet" href="/library.four.css"/><link rel="stylesheet" href="/library.three.css"/><link rel="stylesheet" href="/library.one.css"/>. So, the correct answer is C.