What must a DevOps engineer do to install an AEM instance as an author?

What must a DevOps engineer do to install an AEM instance as an author?

• A. Provide java property instance.type=author.
• B. Set run mode for author in an OSGi console after the first start.
• C. Change the name of the jar file to have author as run mode.
• D. Provide the run mode "author" on a first installation.

Answer: (C)

Run modes control what the AEM instance enables when it starts up. In this context, the approach being tested is configuring the initial boot so that the instance comes up as an author automatically by including the run mode in the startup artifact itself. Renaming the quickstart jar to include author as part of its run mode is a way to ensure that the first boot applies the author configuration without needing extra startup flags or manual changes. This makes the initial installation deterministic: the instance is created as an author right away, which is often desirable in automated deployment pipelines. Other methods, like setting a java property or adjusting things after the system has started, don’t reliably establish the author role on the very first startup, and relying on post-start changes or OSGi console tweaks won’t guarantee the same immediate author setup. Providing the run mode during the first installation is a valid approach, but the item in question emphasizes embedding the run mode in the jar name as the mechanism to achieve an author instance on first boot.

Run modes control what the AEM instance enables when it starts up. In this context, the approach being tested is configuring the initial boot so that the instance comes up as an author automatically by including the run mode in the startup artifact itself. Renaming the quickstart jar to include author as part of its run mode is a way to ensure that the first boot applies the author configuration without needing extra startup flags or manual changes. This makes the initial installation deterministic: the instance is created as an author right away, which is often desirable in automated deployment pipelines.

Other methods, like setting a java property or adjusting things after the system has started, don’t reliably establish the author role on the very first startup, and relying on post-start changes or OSGi console tweaks won’t guarantee the same immediate author setup. Providing the run mode during the first installation is a valid approach, but the item in question emphasizes embedding the run mode in the jar name as the mechanism to achieve an author instance on first boot.