Q: 3
A developer is managing a common mistake that can lead to performance degradation in AEM
development.
Which mistake would cause this type of problem?
Options
Discussion
Option C Lack of indexing slows down repository queries big time in AEM. Official docs and hands-on labs cover this mistake a lot, so worth reviewing those if you're unsure.
C imo. Not indexing big data in AEM means queries get super slow, seen that flagged on several exam dumps. Static variables can be tricky too but performance suffers most from poor indexing. Open to other views if someone disagrees.
C
Probably B, since using static variables everywhere can lead to memory leaks and weird side effects which might slow things down. Not positive but I see people tripped up by that in AEM projects all the time.
B or D? Both of these can impact performance if used badly. I've seen static variables cause weird app state issues in AEM, and overusing synchronized blocks can slow things down with lots of threads. Not sure which hurts more in real world, but B seems pretty plausible for performance drops. Let me know if you disagree.
Had something like this in a mock recently. C makes sense since not having proper indexing on large datasets in AEM drags query performance way down. Other options can cause issues but not the same hit to speed. Agree with C?
B . Static variables across requests can mess up state and cause memory leaks, pretty common trap for AEM newbies.
Nice and straightforward wording, C.
Be respectful. No spam.
