Adobe Experience Manager Sites Developer Professional AD0-E123 Exam Questions

Answer : A

The 'Multi Resource Support' property is used in custom workflow models in AEM to allow a single workflow instance to handle multiple resources, such as assets or pages. When this property is set to true, if multiple assets or pages are selected and the workflow is initiated, AEM will start only one workflow instance instead of individual instances for each item. This is useful for bulk processing of resources, improving efficiency, and managing workflows better.

Option B, 'Multi Resource Enable,' is not a standard AEM workflow property.

Option C, 'Transient Workflow,' refers to workflows that do not persist their data and are not related to handling multiple resources in a single instance.

Answer : A

When modifications are made to a workflow model in AEM, they must be saved and synchronized with the running instance of AEM. If a user starts a workflow and does not see the recent changes or workflow steps, it could be because the workflow model was not synced in runtime. This means the running instance of AEM is not yet aware of the changes, and as a result, the workflow instance uses the old version of the workflow model.

Option B is incorrect because permissions would not cause the recent changes to be unavailable; they would more likely prevent the user from starting the workflow at all.

Option C is also incorrect because while errors in subsequent steps could potentially stop the workflow from proceeding, they would not prevent new steps from appearing in the workflow instance if they were properly saved and synced.

Answer : C

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.

Answer : C

When customizing a core component in AEM, setting the sling:resourceSuperType property 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.

Answer : A

In Sling Models, the @DefaultInjectionStrategy annotation is used to specify the strategy for injecting fields into the model. When setting it to DefaultInjectionStrategy.OPTIONAL, it indicates that all injected fields in the Sling Model are optional and the model will not fail to instantiate if a field cannot be injected. This is a class-level annotation that affects the default injection behavior of all fields within the Sling Model.

Option B is incorrect because requiredInjectionStrategy is not a valid annotation property in Sling Models.

Option C is incorrect because injectionStrategy is not specified at the class level; it is used on the field level with the @Inject annotation.

Answer : A

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.

Answer : B, D

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.