A new AEM Sites implementation includes a component that lists the 10 most recently published PDF documents in AEM Assets. The component works as expected during development and passes QA testing…

Question

Options

• AA PDF with too large file size has been uploaded.
• BThe component is missing a matching Oak index.
• CThe component is missing the HTL display context to escape the PDF title.
• DA PDF with incorrect MIME type has been uploaded.

• A
  69% (27)
• B
  10% (4)
• C
  18% (7)
• D
  3% (1)

Explanation

When an oversized PDF is uploaded to AEM Assets, it can overwhelm the DAM Update Asset ingestion workflow - causing it to stall, fail, or exhaust system resources (disk space, heap). This can leave AEM's Lucene/Oak search index in a corrupted or stale state, which means JCR queries powering the PDF list return zero results, even for previously visible documents. The timing fits: the component worked fine with a small content set during dev and QA, but broke only after heavy asset uploading began in pre-launch preparation.

Why the distractors are wrong:

• B is a classic AEM gotcha, but if the Oak index were entirely missing, the component would have returned empty results from day one - it never would have passed QA.
• C (missing HTL display context) is an XSS/escaping concern; it might mangle rendered titles or create a security vulnerability, but it would not cause the list to be empty.
• D (wrong MIME type) would only exclude that one mistyped asset from MIME-type-filtered queries - it cannot cause all 10 slots to disappear.

Memory tip: Think "one bad apple spoils the barrel" - a single oversized PDF doesn't just fail itself; it can corrupt the shared index that every other asset query depends on, wiping the whole list.

No community discussion yet for this question.