Which service is used in AEM to control how AEM instances interact with a topology, while running on instances?
The service used in AEM to control how AEM instances interact with a topology while running on instances is the Apache Sling Resource-Based service. This service helps in managing the resources and how they're resolved and accessed within the AEM topology. It's part of the Apache Sling framework, which is an integral part of AEM's architecture.
Option A, 'Web Console Service,' is more for administration and management of OSGi components, not specifically for topology interaction.
Option C, 'Offloading Service,' is generally related to processing tasks outside of the AEM instances and does not directly control instance interactions within a topology.
Which offloading-related service is used by each AEM instance to connect to AEM Topology Connector?
The Discovery Service is an offloading-related service used by each AEM instance to connect to AEM Topology Connector. The Discovery Service is part of the Sling Discovery framework, which is responsible for detecting and managing the topology of AEM instances. It enables instances to discover each other and establish a clustered topology, which is essential for load-balancing, failover, and other distributed operations.
Option A, 'Cluster Service,' is not a standard term used in AEM for connecting to the Topology Connector.
Option C, 'Topology Connector Service,' is a slightly misleading term; the correct term is Discovery Service, which performs the role described.
A front-end developer working on an AEM SPA project cannot see the property that should be exposed in the JSON of the new component added to the homepage.
Which option would give information if the required property is exposed by the Sling Model?
In an AEM Single Page Application (SPA) project, the .model.json endpoint is used to expose the properties of a Sling Model as JSON. This is useful for SPAs that need to access component properties dynamically. The front-end developer should check the URL [homepage-path]/model.json to see the JSON output of the Sling Model for the new component. This endpoint provides a tree of the page content as JSON, which includes the Sling Model's exported properties for components included on the page.
A developer would like to view page transaction response times. Which log file would they use?
The request log in AEM records details about requests processed by the AEM instance, including transaction response times. This log is useful for developers when they need to analyze the performance of page requests, including how long each page takes to load. The request log can typically be found in the logs directory of the AEM installation and may be named request.log.
stdout.log typically contains the standard output of the AEM process and is not specific to request transactions.
audit.log is used to log user actions for auditing purposes and does not include transaction response times.
Which datastore is useful when the datastore is on Network File System (NFS}?
When using a Network File System (NFS) for AEM, CachingFileDataStore is recommended because it caches binary data on the file system and stores only references to the binaries in the repository. This can be beneficial for performance, as it reduces the latency associated with reading binaries over the network, especially when NFS is being used. The caching layer helps in optimizing read operations by keeping a local cache of frequently accessed data.
S3DataStore is used when integrating with Amazon S3 for storage.
FileDataStore does not provide caching capabilities and would not be as efficient as CachingFileDataStore when using NFS.
