Over the weekend, a company's transaction database was moved to an upgraded server. All validations performed after the migration indicated that the database was functioning as expected. However, on M

Question

Options

• AThe access permissions for the service account used by the reporting application were not
• BThe new database server has its own reporting system, so the old one is not needed.
• CThe reporting jobs that could not process during the database migration have locked the
• DThe reporting application's mapping to the database location was not updated.
• EThe database server is not permitted to fulfill requests from a reporting application.
• FThe reporting application cannot keep up with the new, faster response from the database.

• A
  77% (33)
• B
  2% (1)
• C
  2% (1)
• E
  7% (3)
• F
  12% (5)

Explanation

After a database migration, two common failure points cause application outages: (A) Service account permissions - the new server does not automatically inherit the old server's permission grants, so the reporting application's service account must be explicitly re-granted the necessary database permissions on the new server. (D) Database location mapping - the reporting application was configured to connect to the old server's hostname or IP address. After migration, the connection string, DSN, or configuration file pointing to the database must be updated to the new server's address. Both issues would cause the application to fail immediately on Monday morning without any problem showing up in the database validation tests, which are run directly on the server itself.

No community discussion yet for this question.