During development the AEM Publisher server keeps crashing randomly. The deployment included a new static FAQ component that was used in the websites Contact Us page. An Architect investigates to find the root cause for the random failures, and notices the following parameters:
* The server slows down when requests are sent to the Contact us page
* The number of requests to the page were very few
* Heap dump shows a large number of instances of the FAQ component
What is likely causing this issue?

A media company wants to use AEM as content hub for multiple customer touch points:
* Brand-specific marketing websites hosted on AEM Sites
* Single Page Applications using headless content
* Native mobile applications
* Content offers in Adobe Target
The company wants to manage its content efficiently with its small editor staff. Text should be entered and reviewed only once, then reused for all touch points.
How should an Architect incorporate these requirements into a solution that leverages AEM Sites features?
A)

B)

C)

D)

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?

A client is using AEM and wants to make sure they are managing their configurations correctly. Refer to the following requirements:
The client has multiple brands that they will be hosting on a single AEM implementation The client wants to reuse as much between brands as possible Each brand needs to be able to override the default values for items like contact us information The client plans to support multiple languages in multiple regions for each brand Each brand/language/region combination will have its own set of content approvers used as part of a custom workflow Which approach should an Architect recommend to manage the client's configurations for AEM?

A client is in the discovery process for building a React native app, which is a single codebase that runs natively on iOS and Android. The goal is to reduce development costs. The client wants to reduce content creation costs in the new react Native app by reusing as much of the marketing content already publish in their AEM instance.
What should the Architect recommend to meet this requirement?