Adobe AD0-E134 Practice Test - Questions Answers

The /cacheroot property under /cache in the dispatcher.any file identifies the directory where cached files are stored. It is a relative or absolute path to the cache root directory. The dispatcher creates a subdirectory for each virtual host under this directory and stores the cached files there. Reference:

https://experienceleague.adobe.com/docs/experience-managerdispatcher/using/configuring/dispatcher-configuration.html?lang=en#cache

This syntax allows the developer to reference a secret variable that is stored in the Cloud Manager UI under Environment Details > Variables. The secret variable name must start with a lowercase letter and can contain alphanumeric characters and underscores. Reference:

https://experienceleague.adobe.com/docs/experience-manager-cloudservice/ implementing/deploying/configuring-osgi.html?lang=en#environment-specific-configuration

The Apache Sling Logging Logger Configuration and Apache Sling Logging Writer Configuration are the OSGi configurations that the developer should use to create a Logger and Writer pair for the company's application logging. The Logger Configuration defines the log level and the log file name for a given logger name or category. The Writer Configuration defines the file size, number of files, and file location for a given log file name. Reference:

https://experienceleague.adobe.com/docs/experience-manager- 65/deploying/configuring/configure-logging.html?lang=en#configuring-log-files

When multiple configurations for the same PID are applicable, the configuration with the highest number of matching runmodes is applied. This is because the runmodes act as a filter to select the most specific configuration for a given environment. If there is a tie between two or more configurations with the same number of matching runmodes, the one that occurs first in the repository is applied. Reference: https://experienceleague.adobe.com/docs/experience-manager- 65/deploying/configuring/configure-runmodes.html?lang=en#configuring-osgi-settings-perrunmode

The configuration in DNS (Domain Name System) should be used to resolve the domain name by dispatcher. The DNS resolves the domain names to the IP address of the web server that hosts the dispatcher. The dispatcher then matches the incoming request URL with the cached files or the AEM publish instances. Reference: https://experienceleague.adobe.com/docs/experience-managerdispatcher/ using/configuring/dispatcher-domains.html?lang=en#client-requests

The /enableTTL "1" configuration must be applied to enable re-fetching of cached items based on Cache Headers sent by AEM. This configuration enables the Time To Live (TTL) feature of dispatcher, which allows dispatcher to check the Cache-Control and Expires headers of the cached files and refetch them from AEM if they are expired. Reference:

https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/pageinvalidation.

html?lang=en#time-based-cache-invalidation

The ui.config project, (/config/…/config.<runmode>) folder is the location where the OSGi configuration should be created for a runmode-specific configuration for an AEM as a Cloud Service implementation. The ui.config project contains OSGi configurations that are deployed to /apps in the repository. The config.<runmode> folder specifies the runmode for which the configuration is applicable, such as author or publish. Reference:

https://experienceleague.adobe.com/docs/experience-manager-cloudservice/ implementing/deploying/configuring-osgi.html?lang=en#project-structure

The @Component(service = ConfigurationFactory.class) @Designate(ocd = ConfigurationFactorylmpl.Config.class,factory=true) option is recommended for creating a multitenancy configuration and binding multiple configurations to it. This option uses the OSGi R6 annotations to define a component that provides a service of type ConfigurationFactory and designates a class that contains the configuration properties. The factory=true attribute indicates that multiple configurations can be created for this component. Reference:

https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/osgiconfiguration- settings.html?lang=en#creating-factory-configurations

The Apache Jackrabbit Oak External Login Module and Apache Jackrabbit Oak Default Sync Handler are the two OSGi configurations that are required for LDAP integration in AEM. The External Login Module defines how AEM connects to the LDAP server and authenticates users against it. The Default Sync Handler defines how AEM synchronizes users and groups from the LDAP server to the repository. Reference: https://experienceleague.adobe.com/docs/experience-manager- 65/administering/security/ldap-config.html?lang=en#ldap-integration