Which action should users avoid to prevent errors when writing to immutable repositories such as /libs and /apps at runtime in AEM as a Cloud Service?

Question

Options

• AAccessing CRXDE Lite
• BUsing Developer Console
• CManaging Logs
• DContacting Support

• A
  88% (29)
• B
  6% (2)
• C
  3% (1)
• D
  3% (1)

Explanation

Accessing CRXDE Lite (option A) is the action to avoid because, in AEM as a Cloud Service, CRXDE Lite is disabled in production environments and attempting to use it to write to immutable paths like /libs and /apps will result in errors - these paths are read-only at runtime by design, enforcing a strict separation between immutable application code and mutable content.

Why the distractors are wrong:

• B (Developer Console): This is a legitimate, read-only diagnostic tool for inspecting bundles, OSGi configuration, and system state - it does not write to the repository.
• C (Managing Logs): Log management is a standard operational activity (e.g., via Cloud Manager) that doesn't interact with immutable repository paths.
• D (Contacting Support): Reaching out to Adobe Support is always appropriate and has no bearing on runtime repository writes.

Memory tip: Think of /libs and /apps as "locked library shelves" - CRXDE Lite is the only tool that would let you try to put a book back on a locked shelf and fail. The other options are just reading or asking for help, never touching the shelf.

No community discussion yet for this question.