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 must use print-314% in a webpage.
Assuming piValue = -3.14
Which HTL approach would be used?
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.
A developer wants to build an AEM project with a specific version. Which property on Maven would be used for this purpose9
In a Maven project, the <version> property is used to specify the version of the project itself. This version can include the version of the AEM project being built if that's the convention used in the project's versioning strategy. It's typically specified in the pom.xml file at the root of the project and is inherited by all the modules of the project unless they specify a different version locally in their respective pom.xml files.
What would be the packageType for immutable code packages in Maven project structure?
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.
A developer working in an AEM as a Cloud Service environment will be using Golden Master.
What is being used by this developer?
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.
