In HTL, theformatoption in the data-sly-use or data-sly-test attribute can be used to format values according to a pattern. The pattern'-#.##%'indicates that the number should be formatted as a percentage with up to two decimal places. ThepiValuevariable would be the number to format, and in this example, it would convert -3.14 to -314%. The@symbol is used to denote the use of an option with the variable in HTL.

• Options B and C are incorrect because they do not use the correct syntax for the format option in HTL. The use of@is to specify options and not part of the variable or pattern itself.

When the dispatcher encounters a URL that is defined as 'deny' in the /filter settings, the out-of-the-box response is typically a 403 Forbidden error. This HTTP status code indicates that the server understands the request but refuses to authorize it. This means the dispatcher configuration has rules set up to explicitly prevent access to certain patterns of URLs, and when such a pattern is matched, it will deny the request, resulting in a 403 response.

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.

A Java service, which is a backend Java class that encapsulates some business logic or functionality, should be placed in thecoreMaven module of an AEM project. This module is intended for the Java code that contains OSGi services, servlets, and other Java backend code. By creating the service in thecoremodule, it can be properly compiled, packaged, and deployed as an OSGi bundle within AEM.

In the Apache Felix Web Console, which is the OSGi management console of AEM, components are managed under the "Components" tab. The provided OSGi component, a servlet in this case, can be disabled by navigating to the "Components" tab, where all the active components are listed. Once the specific servlet is located, it can be disabled by clicking on the "Disable" action button associated with that component. This does not remove the servlet from the system; it simply stops it from being active.

• Option A is incorrect because the "Bundle Resource Provider" tab does not deal with enabling or disabling of components.
• Option B is also incorrect because the "Services" tab provides information about services but does not provide a direct way to disable them.

Experience Fragments in AEM can be exported to Adobe Target, and the default format for this export is HTML. When Experience Fragments are exported to Adobe Target, they are typically used for personalization and A/B testing. HTML is the format that is readily usable within Adobe Target to create variations of a page or a component for these testing purposes.

• XML (Option B) and JSON (Option C) are not the default formats for exporting Experience Fragments to Adobe Target. While they can represent structured data, for the purposes of visual personalization in Adobe Target, the HTML format is used because it can directly represent the markup required for the content to be rendered in a browser.

In an AEM Single Page Application (SPA) project, the.model.jsonendpoint 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.jsonto 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.

When customizing a core component in AEM, setting thesling:resourceSuperTypeproperty in the new component's definition allows it to inherit features from an existing core component. This property points to the resource type of the core component that is being extended or customized. By doing so, the new component inherits the core component's logic and rendering scripts but can be customized further according to project-specific requirements.

• Option A,sling:resourceType, is used to define the primary resource type for a component and does not indicate inheritance.
• Option B,jcr:title, is used to give a human-readable title to a node in the JCR and is unrelated to component inheritance.

In the dispatcher configuration, to allow the caching of requests with an authorization header, the property/cacheAuthorized "true"must be set. By default, the dispatcher does not cache responses to requests that include authorization headers to prevent private or user-specific data from being incorrectly cached and served to other users. Setting this property totrueoverrides the default behavior, enabling the cache to store and serve responses even for requests that contain an authorization header.