What is the correct order of steps for performing a rollback?

What is the correct order of steps for performing a rollback?

• A. Re-install new, Update configs to point to correct database, Start Confluence, Rebuild index
• B. Start Confluence, Rebuild index, Update configs, Re-install
• C. Rebuild index, Start Confluence, Re-install, Update configs
• D. Update configs, Rebuild index, Start Confluence, Re-install

Answer: (A)

Rolling back to a known-good state starts with placing the correct software version in place, then pointing the application to the right data, bringing the service online, and finally making sure search and navigation are accurate with a fresh index. First, re-install the appropriate version so the runtime environment and features match the rollback target. This establishes the correct binaries and platform for the restored state. Next, update the configuration so Confluence connects to the correct database. The rollback relies on the data in that database, so wiring the application to the proper data store before starting is essential to avoid misaligned content or failed startup. Then start Confluence. Booting with the right configuration ensures the system initializes properly, connections are established, and the application comes online to operate on the restored data. Finally, rebuild the index. Once the data is accessible, rebuilding the search index ensures fast, accurate search results reflect the current content and structure, rather than any previous, out-of-sync index.

Rolling back to a known-good state starts with placing the correct software version in place, then pointing the application to the right data, bringing the service online, and finally making sure search and navigation are accurate with a fresh index.

First, re-install the appropriate version so the runtime environment and features match the rollback target. This establishes the correct binaries and platform for the restored state.

Next, update the configuration so Confluence connects to the correct database. The rollback relies on the data in that database, so wiring the application to the proper data store before starting is essential to avoid misaligned content or failed startup.

Then start Confluence. Booting with the right configuration ensures the system initializes properly, connections are established, and the application comes online to operate on the restored data.

Finally, rebuild the index. Once the data is accessible, rebuilding the search index ensures fast, accurate search results reflect the current content and structure, rather than any previous, out-of-sync index.