Adobe AD0-E124 : Adobe Experience Manager DevOps Engineer Expert

The Non-Production Deployment Pipeline for an Adobe Experience Manager as a Cloud Service program terminates prematurely.
Upon initial investigation, the DevOps engineer notes the following:
The pipeline status is ERROR
The last pipeline step is Build Images
The previous execution of the pipeline completed successfully
The DevOps engineer scans the log file, which produces the following output:
INFO [Apache Sling Repository Startup Thread #1] org.apache.sling.jcr.repoinit.impl.GroupMembershipVisitor Adding members '[corp-comm-authors]' to group 'contributor' ERROR [Apache Sling Repository Startup Thread #1] com.adobe.granite.repository.impl.SlingRepositoryManager Exception in a SlingRepositoryInitializer, SlingRepository service registration aborted java.lang.RuntimeException: contributor is not a group com.google.javascript.jscomp.LoggerErrorManager println SEVERE: /libs/cq/gui/components/workflow/editor/clientlibs/workflow.js:8033: ERROR - This language feature is only supported for ECMASCRIPT6 mode or better: const declaration.
const panelContainerType = CQ.CoreComponents.panelcontainer.v1.utils.getPanelContainerType(editable); WARN [Apache Sling Repository Startup Thread #1] org.apache.jackrabbit.oak.query.ast.SelectorImpl The query read or traversed more than 100000 nodes. To avoid affecting other tasks, processing was stopped. for query SELECT sling:vanityPath, sling:redirect, sling:redirectStatus FROM nt:base WHERE sling:vanityPath IS NOT NULL ERROR [Apache Sling Repository Startup Thread #1] org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResourceIterator seek: Problem creating Resource for next node, skipping org.apache.jackrabbit.oak.query.RuntimeNodeTraversalException: The query read or traversed more than 100000 nodes. To avoid affecting other tasks, processing was stopped.
Which two steps should the DevOps engineer take next? (Choose two.)

• A. Add an oak:index definition for the sling:vanityPath property.
• B. Manually trigger the pipeline to see if it terminates at the same step with similar log output.
• C. Inspect the most recent git commits in the pipeline branch for changes to repoinit configs.
• D. Temporarily switch the Non-Production pipeline from the development branch to the stable branch and rebuild to restore functionality in the environment.
• E. File a ticket named "SEVERE ECMASCRIPT ERROR" in the project issue tracker and assign it to a Frontend Developer for further investigation.

After deploying a new version of an AEM site, users report slow page load times.
What should be checked first?

• A. OSGi component logs for errors
• B. The number of active workflows running in AEM
• C. Dispatcher cache settings and invalidation rules
• D. CRX repository size and index settings

A customer's development team is expanding and requires more development environments to be added to the AEM as a Cloud Service. There is no visible option via the Cloud Manager UI to add a new development environment under the current program.
What should the DevOps engineer do?

• A. Add a new runmode via OSGi configuration.
• B. Advise the customer to contact the Adobe account team.
• C. Add a new sandbox program via the Cloud Manager UI.

A Cloud Manager pipeline deployment fails due to a missing dependency.
What is the best approach to resolve this issue?

• A. Check and update the pom.xml to ensure the dependency is correctly referenced
• B. Disable the dependency check and force the deployment
• C. Manually add the missing JAR file to the AEM instance
• D. Remove all dependencies and rebuild the project

A developer creates a new git branch for a feature that is being developed on AEM as a Cloud Service. The developer asks the DevOps engineer to establish an automated deployment to occur every 4 hours only.
What should the DevOps engineer do?

• A. Write a git commit hook to call Adobe I/O CLI every 4 hours.
• B. Set up a cron job to call Adobe I/O CLI every 4 hours.
• C. Set up a cron job to push a git commit every 4 hours.
• D. Schedule a pipeline in the Cloud Manager UI to run every 4 hours.