AEM Site users report that the web content pages render very slowly. An Architect notices that the CPU usages of the AEM Publish instances are spiking and reviews the following entry in the log:
[Frt Nov 27 23:11:00 2019] [I] [pid 16004 (tid 140134145820416)] Current cache hit ratio: 47.94 %
What should the Architect do to increase the dispatcher cache ratio and prevent the AEM Publish CPU usage spikes?
A client has an existing AEM site using components that proxy AEM WCM Core Components. The site uses simple page authoring without referenced content, The client wants to create a new experience on another marketing channel. The plan is to use as much of the existing page content as possible to avoid refactoring the current content and to maintain consistency across channels.
Which AEM capability should an Architect use to meet these requirements?
A client's marketing pages are generally slow to load which is causing a significant drop in sales. All other AEM pages load within expected performance guidelines regardless of whether the visitor is being served the desktop or mobile experiences.
The marketing pages typically get slower when multiple external campaigns such as Facebook and AdWords drive traffic to those pages. The page performance tends to dip during high traffic periods. Internal campaign clicks such as those from hero images use similar campaign codes as external campaign traffic.
What should the Architect do to resolve this issue?
In a client's test environment AEM QA Testers from multiple groups and regions are testing and making requests to the AEM application. Due to the sheer number of hosts making connections, an Architect needs a quick and easy way to allow any hosts to make requests to the AEM application.
Which approach should the Architect take to meet this requirement for this non-production environment?