You're aware that a new FDI application update just became available. What's a best practice for upgrading an FDI instance?

• A. Deploy the update immediately during peak hours.
• B. Skip the upgrade to avoid downtime.
• C. Notify users after the upgrade.
• D. Review the documentation, prepare for the upgrade, and schedule it when you're ready.

Answer: (D)

Upgrading an FDI instance should be planned and coordinated with preparation, documentation review, and a scheduled window. Before you run the upgrade, read the release notes and upgrade guide to understand what’s changing, what prerequisites exist, and how any customizations or integrations might be affected. Check system requirements and compatibility with your current setup, and inventory any third‑party plugins or extensions that could be impacted. Prepare by backing up data and configuration, and create a rollback plan in case something goes wrong.

Testing in a non-production environment is essential to validate the upgrade path, confirm that critical workflows, reports, and integrations work as expected, and catch issues before affecting users. After planning, schedule the upgrade during a maintenance window that minimizes business impact, and communicate the timing and expectations to stakeholders in advance. Post-upgrade validation should follow a defined checklist to ensure everything operates correctly and to confirm that the upgrade delivered the intended improvements.

That’s why reviewing the documentation, preparing for the upgrade, and scheduling it when you’re ready represents the best practice. Deploying during peak hours can cause noticeable downtime and performance issues; skipping the upgrade to avoid downtime leaves you exposed to bugs and missing enhancements; informing users only after the upgrade misses the opportunity to set expectations and coordinate any required changes.