A developer running a local AEM instance and working on an AEM project needs to change a large number of files locally in the filesystem. The developer needs to get the changes uploaded to the local AEM instance to verify changes almost immediately in the browser?
What action should the developer take to most efficiency meet these requirements?
The most efficient way for a developer to make changes locally and have them reflected almost immediately in the browser is to install FileVault bundle in the AEM instance and register the local working directory for synchronization. This allows for real-time synchronization between the local filesystem and the AEM repository, ensuring that changes are instantly available without the need for manual uploads or package deployments.
Shouldn't be Option C ?
yes the answer is C
Should be C
Answer: C Vault Sync The vault sync service is used to synchronize repository content with a local filesystem representation and vice versa. This is achieved by installing an OSGi service that will listen for repository changes and scans the filesystem contents periodically. It uses the same serialization format as vault for mapping the repository contents to disk. The vault sync service is a development tool and it is highly discouraged to use it on a productive system. Also note that the service can only sync with the local filesystem and cannot be used for remote development. Reference: https://jackrabbit.apache.org/filevault/usage.html#vault_sync
Answers is C