A large AEM enterprise site is implementing authentication and requires a true optimal load balancing across the site's multi AEM publish instances. Which approach should an Architect take to meet this requirement?

1. A. Configure Sticky Connections
2. B. Configure the Dispatcher to run with a Dedicated System Usei
3. C. Enable Encapsulated Token Option
4. D. Enable Round Robin processing in Dispatcher configuration

Correct Answer: C
“enabling Encapsulated Token Option can provide optimal load balancing across multiple AEM publish instances by using a token-based authentication mechanism”.

A client is migrating the content from a legacy website to an existing AEM implementation. An Architect evaluates the content of the legacy site and determine-that there are approximately 20.000 pages with a common structure, and a few hundred pages that do not follow a pattern. The client wants to complete the migration as soon as possible.
Which approach should the Architect recommend for the content migration?

1. A. Migrate all common pages using the ETL procedure with multiple rounds
2. B. Migrate all common pages using the ETL procedure and use manual authoring for the rest
3. C. Use Site importer to import the content into AEM
4. D. Recreate the entire content manually with a group of Content Authors

Correct Answer: B
“migrating all common pages using the ETL procedure and using manual authoring for the rest can reduce the time and effort required for the content migration”.

A customer wants to implement an AEM solution to serve localized content to several regional websites. Which AEM capability should the Architect recommend?

1. A. Use translation connector and Multi Site Manager
2. B. Use il8N API and Multi Site Manager
3. C. Use translation connector and il8N API
4. D. Use translation connector and translation workflows

Correct Answer: A
According to Adobe Experience Manager documentation, translation connectors are used to integrate AEM with third-party translation services to orchestrate the translation of AEM content. Multi Site Manager (MSM) is used to create and manage multiple websites that share common content and structure.
https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/sites/administering/reusing

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?

1. A. Modify the dispatcher.any file's section to ignore campaign-based URL parameters
2. B. Set AEM to use GZIP compression instead of the web server's compression
3. C. Add a new dispatcher farm to assist with the client's marketing pages
4. D. Convert the marketing pages to a responsive design instead of an adaptive design

Correct Answer: A
Modify the dispatcher.any file’s section to ignore campaign-based URL parameters12. According to Adobe Experience Manager documentation2, dispatcher can be configured to ignore certain URL parameters that do not affect the content of a page. This can improve caching performance and reduce load on AEM servers.

A customer's photo gallery site uses query parameters to filter photo search results. The site experiences high AEM Publish server load when users filter photos on the site. The customer would like to identify the cause of this issue.
What should the Architect investigate first?

1. A. ignoreUrlParams configuration in dispatcher.any
2. B. Dispatcher load balancing configuration
3. C. Cache-Control Headers in dispatcher.any
4. D. Volume of assets being loaded at a time

Correct Answer: C
“Cache-Control Headers in dispatcher.any control how long the dispatcher caches responses from the publish server. If these headers are not configured properly, the dispatcher may cache stale or dynamic content, resulting in high server load and poor performance”.