What three actions by an author automatically add nodes/properties to the content directory in the JCR?

The correct answer highlights actions that directly lead to the creation of new nodes or properties within the Java Content Repository (JCR) structure, which is integral to how Adobe Experience Manager (AEM) organizes content.

When an author edits content, they are updating existing nodes, which can involve changing properties or adding new ones based on the modifications being made. Creating a page inherently necessitates the creation of a new node within the JCR for that page. Adding an image also involves creating a new node or property for that image, which will be stored in the JCR.

Together, these actions reflect how authors interact with the content structure in AEM, leading to a direct impact on the repository by adding new nodes and properties.

In contrast, the other options do not consistently lead to the automatic addition of nodes or properties to the content directory. Deleting a page or moving assets may change the structure but do not create new nodes. Configuring workflows or previewing pages usually deals with processes or temporary presentations rather than direct content creation. Accessing content is generally a read operation and does not modify the structure, while modifying metadata might change properties of existing nodes, still not resulting in the addition of new nodes.