Explanation (Adobe Docs Reference):

AEM supports basic multi-tenancy through separation by content paths, ACLs, and templates. However, this is not true multi-tenancy. For strict isolation with no code/content overlap, separate AEM instances per tenant is required. Adobe’s official recommendation for true isolation (zero cross-tenant knowledge or sharing) is to run dedicated AEM environments per tenant.

Adobe Documentation:

“AEM supports multi-tenancy by allowing separation of content trees, ACLs, and components. However, for strict tenant isolation (true multi-tenancy), each tenant must be deployed on separate AEM environments.”

— Adobe AEM Multi-tenancy Concepts

In AEM, multi-site management allows centralized content updates to be pushed across different localized or departmental sites. The “Partial” option on the rollout configuration ensures that only specific components or regions designated for shared updates are synchronized, while leaving local content intact. This fits the described requirement where a portion of each school’s homepage must receive university updates without affecting school-specific content. Option A, Experience Fragments, could be used but are better suited for shared fragments of design/content, not controlled rollout scenarios. Option C requires manual inheritance restoration per page, which is inefficient. Option D, implementing custom rollout logic, is not needed when the built-in “Partial Rollout” option fulfills the requirement. Adobe emphasizes using partial rollout in multi-site configurations to balance central control with localized autonomy.

Explanation (Adobe Docs Reference):

Editable templates + Policies: Editable templates allow developers to restrict which components are available by defining policies that control allowed components for layout containers.

Content Fragment Model validation: Developers can define validation rules (e.g., regex, required fields, min/max length) directly in the content fragment model.

Options A, C, and D are incorrect:

Field validation is not configured in editable templates (A is wrong).

Workflows are not used for enforcing component usage (C is wrong).

Dynamic templates are deprecated in favor of editable templates (D is wrong).

Adobe Documentation:

“Editable templates support defining policies to determine which components can be used in the layout container.”

— AEM Templates – Defining Policies

“Content Fragment Models can include validation rules to ensure data integrity, including regex patterns, length restrictions, and required fields.”

— AEM Content Fragment Models – Validation Rules

By default, when saving dialog values, AEM stores them as String types in the JCR unless a type hint is provided. To ensure a checkbox is stored as a Boolean, developers must add a hidden TypeHint field to the dialog. This informs Sling Post Servlet about the correct JCR type when persisting values. Option A, using a JCR Event Listener, is inefficient and adds unnecessary complexity. Option C, using a Switch, would still result in a String unless the TypeHint is specified. Adobe documentation specifies that TypeHint fields should be added whenever developers need precise control over how values are stored, especially for Boolean, Long, or Date properties.

Explanation (Adobe Docs Reference):

Assets in AEM are stored as dam:Asset nodes, not nt:base or cq:image.

Metadata like cq:lastModified is stored under jcr:content/metadata.

Therefore, the correct query must use [dam:Asset] with the proper metadata path.

Options A and C are invalid because they use wrong node types or incorrect property paths.

Adobe Documentation:

“Assets are represented as dam:Asset nodes. Metadata such as lastModified is stored under jcr:content/metadata and can be queried using JCR-SQL2.”

— AEM Assets – Querying Assets

Run mode-specific configurations in AEM follow a strict naming convention under the osgiconfig folder. The folder structure defines both the run mode (author or publish) and the environment (e.g., dev, stage, uat, prod). For UAT author environments, the correct structure is config.author.uat. Option C follows this convention correctly. Option A and B use incorrect naming patterns, which would prevent AEM from loading the configuration under the desired run mode. Adobe emphasizes the importance of placing OSGi configs in the correct folder paths within the ui.apps project or ui.config project depending on deployment structure.

AEM package files follow a standard naming convention in CRX Package Manager:

--.zip

Thus, with the package name aem-package, group aem_group, and version 1.0, the correct package name is aem-package-aem_group-1.0.zip. Option B is invalid because group names and content paths are not combined in filenames. Option C omits the group name, making it incomplete. Adobe documentation emphasizes this naming convention for easier package identification and dependency management across environments.