If reconnection attempts are not configured and the initial connectivity test fails, what happens by default?

If reconnection attempts are not configured and the initial connectivity test fails, what happens by default?

• A. The application stops during startup
• B. The application retries automatically until success
• C. The failure is logged and the application starts anyway without trying to reconnect
• D. The deployment fails

Answer: (C)

When a connectivity check is run at startup and no automatic reconnect policy is configured, the system treats the failure as a non-fatal issue. It records a clear error in the logs indicating the connectivity problem, but it does not halt startup or terminate the deployment. The application continues to start, and the connector or resource may attempt to connect later when actually used, or during later health checks. This approach avoids blocking the entire startup due to an external resource being temporarily unavailable, while still making the failure visible for diagnosis.

When a connectivity check is run at startup and no automatic reconnect policy is configured, the system treats the failure as a non-fatal issue. It records a clear error in the logs indicating the connectivity problem, but it does not halt startup or terminate the deployment. The application continues to start, and the connector or resource may attempt to connect later when actually used, or during later health checks. This approach avoids blocking the entire startup due to an external resource being temporarily unavailable, while still making the failure visible for diagnosis.