AEM Sites Developer Professional flashcards
AEM Sites Developer Professional · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Author and publish instances
- Author instances are used to create and manage content; publish instances serve public traffic and normally sit behind a Dispatcher that caches responses.
- TarMK segment store
- TarMK is Oak's default file-based segment store for a single AEM instance; it supports cold standby but not shared concurrent writes across nodes.
- MongoMK repository
- MongoMK stores Oak content in MongoDB and allows multiple AEM nodes to share one repository, which is required for clustered author or publish topologies.
- Replication agent
- A replication agent on an author instance sends content to a publish instance over HTTP(S), where a receiver endpoint applies the content.
- Dispatcher flush agent
- A flush agent on publish sends cache invalidation requests to the Dispatcher when activated content changes, removing stale cached responses.
- Context-aware configuration
- Context-aware configurations live under /conf and can be bound to sites or tenants, allowing different settings without changing product code under /libs.
- Cloud Manager pipeline
- Cloud Manager pipelines build and deploy AEM as a Cloud Service code and configuration; production deployments do not use the package manager directly.
- HTL data-sly-use
- The data-sly-use attribute in HTL binds a Java model or JavaScript object to the template, exposing its methods and properties to subsequent expressions.
- Editable template
- An editable template is stored as content under /conf, defines structure and policies, and can be modified by authors with the required permissions.
- Proxy component
- A proxy component sets sling:resourceSuperType to another component, inheriting its scripts and dialog while allowing project-specific overrides.
- cq:dialog
- The cq:dialog node defines a Touch UI component dialog; Granite UI field names map directly to JCR properties written on the component node.
- Sling Model annotation
- A Sling Model uses @Model to declare adaptable classes and @Inject or @ValueMapValue to map resource properties into Java fields.
- Client library category
- A client library category groups CSS and JavaScript; templates include the category, and dependencies and embeds control load order and bundling.
- Component policy
- A component policy is configuration referenced by an editable template; it controls allowed components and design properties for that template.
- Sling resource resolution
- Sling maps a URL path to a JCR resource, then uses sling:resourceType, selectors, and extension to choose the script or servlet that renders it.
- ResourceResolver
- A ResourceResolver provides access to resources and adapts to a JCR Session; it must be closed after use to release repository connections.
- OSGi @Reference
- The @Reference annotation injects an OSGi service into a component; a missing mandatory reference leaves the component unsatisfied.
- OSGi component states
- OSGi components can be active, resolved, or unsatisfied; unsatisfied components usually have a missing mandatory reference or missing configuration.
- ModifiableValueMap
- ModifiableValueMap allows a Sling resource's properties to be changed; the changes persist when the underlying ResourceResolver commits.
- ResourceChangeListener
- A ResourceChangeListener receives asynchronous notifications about repository changes and can filter by path, resource type, and change type.
- Client library proxy path
- When allowProxy is true, client libraries under /apps are served from /etc.clientlibs on publish, which is the exposed client-library path.
- js.txt and css.txt
- These files list the JavaScript or CSS source files in a client library folder; their order determines the order in the built output.
- ui.frontend module
- The AEM project archetype's ui.frontend module runs npm and webpack builds, then copies generated assets into an AEM client library.
- DAM rendition
- A rendition is a generated version of an asset, such as a thumbnail or web image, stored under the asset's metadata/renditions node.
- Asset metadata schema
- A metadata schema defines which metadata fields editors see for assets; values are stored on the asset node and can map to XMP properties.
- Dynamic Media
- Dynamic Media delivers images and video from a separate tier and supports smart imaging, responsive viewers, and URL-based transformations.
- Dispatcher filter rules
- Dispatcher filter rules allow or deny requests by path and HTTP method; the default posture is deny unless a rule explicitly permits the request.
- Dispatcher cache rules
- Cache rules determine which requests Dispatcher stores, including headers, TTL, and query parameters used to build the cache key.
- Cache invalidation
- Cache invalidation removes stale Dispatcher entries; it is triggered by flush agents when content is activated or explicitly invalidated.
- ignoreUrlParams
- The ignoreUrlParams setting excludes specified query parameters from the Dispatcher cache key, reducing cache fragmentation from tracking parameters.
- Cloud Manager web-tier pipeline
- A web-tier pipeline deploys Dispatcher and CDN configuration for AEM as a Cloud Service without deploying application code.
- Sticky sessions
- Sticky sessions route a user's requests to the same AEM instance; they are required for author clusters because local repository state is not shared.