In Adobe Experience Manager, environment and runmode-specific OSGi configurations are managed using folder naming conventions. To target a specific runmode, the folder name must be appended with . followed by the runmode name. Therefore, to supply separate configurations for the Author and Publish runmodes, the configurations must reside in /config.author/ and /config.publish/ respectively. Option D uses a nested folder approach (/config/author/) which is not the standard OSGi runmode resolution syntax in AEM.

According to Adobe Support ticketing protocols, once a ticket has been marked as resolved and successfully closed (especially after a prolonged period like three weeks), it cannot be re-opened or escalated. The system locks closed tickets. Even if the symptoms appear identical, a recurrence requires the engineer to open a brand new ticket. They should reference the old ticket number in the new ticket's description so the support team can review the historical context and previous resolutions.

In AEM as a Cloud Service, directly deploying packages via the AEM Package Manager UI is severely restricted. You cannot deploy immutable content (code, OSGi configs, or anything under /apps or /libs) via the Package Manager; immutable content must go through the CI/CD pipeline. If a DevOps engineer is forced to use the Package Manager, the package must be strictly limited to mutable content (authorable content, configurations under /conf, /content, /dam). Therefore, they must refactor the package, explicitly set the < packageType > to content, and update the filter.xml to exclude any immutable paths.

Adobe Support has strict Service Level Agreement (SLA) definitions for priority levels.

P1 (Critical): The production application is completely down and unavailable to end-users (e.g., Publish tier is crashed).

P2 (Serious): A core, business-critical function is down for all users, causing severe revenue or operational impact.

P3 (Interruption to normal operations): The application is functional, but specific users are experiencing degraded performance or feature loss (like a broken authoring workflow).

Even though the business has a deadline (a product launch within 24 hours), the fact that the live production site is still up and only two authors are currently reporting an inability to activate pages categorizes this strictly as a P3 issue according to standard Adobe support guidelines.

In AEM as a Cloud Service, the Preview tier is designed to act as an internal staging ground to verify content exactly as it will look on Publish, but restricted from the general public. By default, the Preview Service is completely blocked from external access via a default IP Allow List. To grant access to specific internal authors or stakeholders, the DevOps engineer must first remove/unbind this default blocking rule, and then create and bind a custom IP Allow List via Cloud Manager that explicitly whitelists the corporate IP addresses or VPN IP ranges of those specific authors.

In both AEM On-Premise/Managed Services and AEM as a Cloud Service, routine repository maintenance tasks (like Version Purge, Workflow Purge, and Audit Log Purge) are configured natively within the AEM author UI. The DevOps engineer navigates to the Maintenance Dashboard via Tools > Operations > Dashboard > Maintenance to configure the daily and weekly maintenance windows and schedule which tasks run inside them.

For headless, service-to-service integrations via Adobe I/O (Adobe Developer Console), JWT (JSON Web Tokens) was historically the standard. However, Adobe officially deprecated the Service Account (JWT) credentials in favor of the new OAuth 2.0 Server-to-Server credential implementation. Because Adobe exams are updated to reflect current platform deprecations and best practices, OAuth 2.0 is the correct, modern standard for programmatic authentication without a user interface.