System configuration verification tests/approach/tools

Question is about best practices for testing/verifying configuration of product.

Let's say we are developing hotel booking system, have 1 web site for taking books, background daemon job for processing bookings and API for communicating with hotels. Web site publishes messages to Message Queue, daemon consumes those messages, persists in database and sends notifications to hotels through API.

In this scenario, does it make sense to test/verify thing like:

• Web site has correct config files - pointing to right database, MQ etc.
• Message Queue has correct Exchanges/Queues
• Daemon has correct schedules
• API - correct client configurations etc.

Yes, smoke tests and integration test will test everything this, but they're more likely to do application logic testing. I want to have something which I can run before smoke tests, and for pre-prod and prod environment it will do great job checking all configs are pointing to prod ones.

Any suggestions will be appreciated.