AEM as a Cloud Service - Fundamentals Quiz 1

Question 1

Provisioning repository principals as code

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

Context: Cloud deployment

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

Question 2

What does the Repository Modernizer help convert?

Which legacy project structure can it modernize?

Context: AEM Cloud Service migration

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

Question 3

Which environment type is intended for production traffic?

Which AEM Cloud Service environment serves live end users?

Context: AEM Cloud Service environments

Development Production Local SDK Rapid Development Environment

Question 4

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

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

Question 5

What web-tier component fronts publish instances?

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

Context: AEM Cloud Service architecture

Replication agent Dispatcher CRXDE Lite Oak indexer

Question 6

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 Dispatcher filter rule A plain-text .cfg.json value

Question 7

What is the purpose of a stage environment?

How is a stage environment primarily used?

Context: AEM Cloud Service environments

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

Question 8

What platform capability handles changing demand?

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

Context: AEM Cloud Service architecture

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

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

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

Question 10

What supports local Cloud Service development?

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

Context: AEM Cloud Service development

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

Question 11

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 /content /var /apps

Question 12

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 local filesystem copy An author replication agent A Git repository processed by Cloud Manager A direct CRX Package Manager upload

Question 13

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

Question 14

How is Dispatcher configuration managed in Cloud Service?

Where should Dispatcher configuration changes be maintained?

Context: AEM Cloud Service Dispatcher

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

Question 15

Handling environment-specific behavior

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

Context: Cloud-native configuration

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

Question 16

Who manages AEM platform updates in Cloud Service?

Who is responsible for maintaining the underlying AEM service platform?

Context: AEM Cloud Service operations

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

Question 17

What is the Content Transfer Tool used for?

What migration task does this tool support?

Context: AEM Cloud Service migration

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

Question 18

When are code quality checks run?

Which Cloud Service process runs code quality analysis before deployment?

Context: AEM Cloud Service

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

Question 19

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

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

Question 20

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 Oak forbids all caching Because Dispatcher writes data back into the JVM Because publish nodes are elastic and can be replaced at any time Because author and publish share the same memory space

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