Adobe AD0-E123 Exam

In HTL, the format option 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. The piValue variable 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.

In Maven for AEM, application is the packageType that is typically used for immutable code packages. These are packages that contain code that is not expected to change between deployments, such as OSGi bundles and certain content packages that do not contain user-editable content. This type of package is intended to be deployed to an AEM instance as part of the application's codebase, and the application packageType signifies this use case.

container is not a standard package type in AEM Maven project structures.

content is typically used for packages that contain mutable content, such as pages and configurations that can be edited by authors.

In the context of AEM as a Cloud Service, a 'Golden Master' typically refers to the production-ready, main branch within the Cloud Manager Git Repository. This repository is used to manage and deploy code to AEM Cloud Service environments. It is considered the source of truth for the codebase that is used to build, test, and deploy AEM applications in the cloud.

When an AEM instance starts with specified run modes, it selects configurations from the repository that match those run modes. Run modes allow for flexible management of settings and configurations across different environments. For the instance started with 'author', 'dev', and 'emea' run modes, it would apply configurations from paths that match these run modes.

Option B, /config/author.dev.emea.noldap, is correct. This path matches all three run modes specified and would, therefore, be included.

Option D, /apps/mysite/config.author.emea.dev, is also correct. This path matches the run modes and would be applied to the instance as well.

Options A and C do not match all three run modes and therefore would not be applied.

In AEM, when you need to extend a dialog from a core component but want to hide or exclude one tab or part of the dialog, you can use the sling:hideResource property. This property allows you to selectively hide resources (like a tab in a dialog) inherited from a super type (the core component) in your overlay or custom component.