AEM as a Cloud Service - Fundamentals Quiz 1

Question 1

What is the Content Transfer Tool used for?

What migration task does this tool support?

Context: AEM Cloud Service migration

Creating Git repositories Deploying Dispatcher modules to Apache Editing OSGi configurations live Transferring existing AEM content to Cloud Service

Question 2

When are code quality checks run?

Which Cloud Service process runs code quality analysis before deployment?

Context: AEM Cloud Service

A replication queue An AEM workflow model A Dispatcher flush agent A Cloud Manager code quality pipeline

Question 3

Handling environment-specific behavior

Which statement about run modes in AEM as a Cloud Service is correct?

Context: Cloud-native configuration

Run modes are configured directly from CRXDE on production Custom customer-defined run modes are the standard way to separate code paths Arbitrary custom run modes are not supported the way they were on classic deployments Only author and publish support OSGi configs; dev has none

Question 4

What web-tier component fronts publish instances?

Which component is deployed in front of AEM publish in Cloud Service?

Context: AEM Cloud Service architecture

Oak indexer Replication agent Dispatcher CRXDE Lite

Question 5

How should an OSGi config reference a secret?

What should be used instead of committing a secret value to source control?

Context: AEM Cloud Service security

A JCR property on /apps A Cloud Manager secret variable placeholder A plain-text .cfg.json value A Dispatcher filter rule

Question 6

Understanding immutable areas

Which repository area is treated as immutable at runtime and therefore updated through pipelines rather than ad hoc changes?

Context: Deployment model

/home /apps /content /var

Question 7

What is the purpose of a stage environment?

How is a stage environment primarily used?

Context: AEM Cloud Service environments

Pre-production validation before production deployment Directly editing immutable code Permanent content archival Local developer debugging only

Question 8

What does the Repository Modernizer help convert?

Which legacy project structure can it modernize?

Context: AEM Cloud Service migration

Dispatcher rules into Java code AEM Maven project structures for Cloud Service compatibility JCR queries into SQL Users into IMS accounts

Question 9

How is publish content distribution handled in Cloud Service?

Which mechanism distributes publish content in AEM as a Cloud Service?

Context: AEM Cloud Service architecture

Manual filesystem synchronization Dispatcher invalidation only Classic reverse replication Sling Content Distribution

Question 10

What is a key implication of immutable infrastructure in AEM as a Cloud Service?

Which practice aligns with the immutable infrastructure model in AEM as a Cloud Service?

Context: AEM as a Cloud Service

Managing code and most configuration through the deployment pipeline Uploading OSGi bundles from CRXDE Lite on production Storing secrets in component dialogs Editing runtime code directly on production instances

Question 11

Who manages AEM platform updates in Cloud Service?

Who is responsible for maintaining the underlying AEM service platform?

Context: AEM Cloud Service operations

The Dispatcher administrator only Adobe The content author The Git repository owner

Question 12

Designing for elastic publish topology

Why should custom code avoid relying on local filesystem files or sticky in-memory state on publish in AEM as a Cloud Service?

Context: Cloud runtime behavior

Because publish nodes are elastic and can be replaced at any time Because Oak forbids all caching Because author and publish share the same memory space Because Dispatcher writes data back into the JVM

Question 13

What supports local Cloud Service development?

Which tool provides a local AEM runtime matching Cloud Service development needs?

Context: AEM Cloud Service development

AEM as a Cloud Service SDK Cloud Manager production pipeline Dispatcher Flush agent Content Transfer Tool

Question 14

Provisioning repository principals as code

What is repo init commonly used for in AEM as a Cloud Service projects?

Context: Cloud deployment

Scheduling page publication windows Creating image renditions on asset upload Provisioning service users, groups, and ACL-related repository setup during deployment Configuring browser cache max-age headers

Question 15

What platform capability handles changing demand?

How does AEM as a Cloud Service respond to varying workload demand?

Context: AEM Cloud Service architecture

It uses only Dispatcher cache expansion It permanently fixes instance capacity It automatically scales cloud infrastructure It requires manual server installation

Question 16

How is application code deployed to AEM as a Cloud Service?

What is the standard source for Cloud Service deployments?

Context: AEM Cloud Service deployment

A Git repository processed by Cloud Manager An author replication agent A local filesystem copy A direct CRX Package Manager upload

Question 17

How is Dispatcher configuration managed in Cloud Service?

Where should Dispatcher configuration changes be maintained?

Context: AEM Cloud Service Dispatcher

Inside a content fragment Only through the AEM web console In source control as part of the project Directly on the Dispatcher host

Question 18

Which environment type is intended for production traffic?

Which AEM Cloud Service environment serves live end users?

Context: AEM Cloud Service environments

Local SDK Development Production Rapid Development Environment

Question 19

Where should deployment-specific non-secret values be stored?

What is the preferred Cloud Service mechanism for environment-specific configuration values?

Context: AEM Cloud Service configuration

Hard-coded Java constants Content package filters Dispatcher cache files Cloud Manager environment variables

Question 20

What problem does a Rapid Development Environment mainly solve?

Why do AEM as a Cloud Service teams use an RDE?

Context: AEM Cloud Service development workflow

To store author-generated content permanently To replace all production pipelines To manage CDN DNS records To speed up iterative development and validation without full pipeline turnaround for every change

AEM CQ5 Tutorials

AEM as a Cloud Service – Fundamentals Quiz 1

Question 1

Question 2

Question 3

Question 4

Question 5

Question 6

Question 7

Question 8

Question 9

Question 10

Question 11

Question 12

Question 13

Question 14

Question 15

Question 16

Question 17

Question 18

Question 19

Question 20

Related