The DevOps engineer is defining a new project setup in AEM as a Cloud Service. The initial setup for Maven Profiles is done by the development team.
The test is to check where the build is running and provide a statement. The build needs to be run within AEM as a Cloud Service and on Stage to see where the build was executed.
The expected test output was not observed during the most recent pipeline run.
<profile>
<id>CMBuild</id>
<activation>
<property>
<name>!env.CM_BUILD</name>
</property>
</activation>
<build>
<plugins>
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.8</version>
<executions>
<execution>
<phase>initialize</phase>
<configuration>
<target>
<echo>I'm running inside Cloud Manager!</echo>
</target>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
What must the DevOps engineer do?

• A. Change
  <name>!env.CM_BUILD</name>
  to
  <name>STAGE.CM_BUILD</name>
• B. Configure the STAGE environment via the Cloud Manager API using the CLI to run if ( STARTED === event["@type"] && EXECUTION === event["xdmEventEnvelope:objectType"] ) { console.log(`I'm running inside Cloud Manager!`);
  }
• C. Replace the Maven profile with a different plugin configuration.
• D. Change
  <name>!env.CM_BUILD</name>
  to
  <name>env.CM_BUILD</name>

What is the primary function of Adobe Cloud Manager?

• A. Automating deployments and managing cloud environments
• B. Optimizing AEM workflows and process automation
• C. Managing user roles and permissions in AEM
• D. Configuring replication agents for content delivery

Which actions help identify bottlenecks affecting AEM performance? (Choose two)

• A. Reviewing logs for long-running queries
• B. Increasing the number of publish instances without checking load balancer settings
• C. Modifying the sling.properties file to boost performance
• D. Analyzing request latency using Cloud Manager metrics

A DevOps engineer notices that the Online Revision Garbage collection is not running as part of the daily maintenance tasks. After inspecting the server's error log, the following shows up during the maintenance schedule:
"Revision GC will not run: Size delta is N% or N/N (N/N bytes), so skipping compaction for now" The DevOps engineer needs to make sure that the revision garbage collection runs during the scheduled maintenance task. Which additional step should the DevOps engineer take?

• A. Increase the size of the TarMK segment files.
• B. Set full compaction schedule property for com.adobe.granite.maintenance.crx.impl.
  RevisionCleanupTask to a preferred day.
• C. Invoke startRevisionGC() for SegmentRevisionGarbageCollection MBean in the JMX console.
• D. Disable the estimation phase in the Apache Jackrabbit Oak segment-Tar Nodestore Factory.

A DevOps engineer notices that a system occasionally gets slower.
* No deployment has been recently performed.
* After a restart of the instance, the performance degradation is mitigated.
* If no action is taken, the JVM tends to crash in an unpredictable manner with Out Of Memory exceptions.
* There is no clear correlation between visitor peaks and crashes of the instances.
* The same symptoms affect author and publish instances.
What is causing this issue?

• A. There are too many concurrent users.
• B. The data store used is not appropriate.
• C. JCR sessions are not closed properly.
• D. The access rights strategy has too many groups and too many ACLs.