Denodo Design Studio and Solution Manager: Development Lifecycle and Deployment
What this domain tests
This domain covers how artifacts move from a developer's environment to test and production without manual rework: projects, revisions, solutions, environments and deployment.
Development in Design Studio
Design Studio is the web-based development environment for building databases, data sources, views and services. Work is organized into projects, and elements can be exported as VQL for review or version control. Development happens against a development server; production changes should never be made by hand in the production environment.
Solution Manager
Solution Manager manages revisions in a version control system and packages elements into solutions for deployment. A solution is a named set of elements plus their dependencies. Each target environment has its own connection settings. Deployment compares the solution with the target, shows the operations it will perform (create, replace, delete), and applies them, with impact analysis available beforehand.
Environment-specific configuration
The recurring problem is credentials and endpoints that differ per environment. Solutions parameterize these so the same artifact deploys unchanged while the data source points at the production database with production credentials.
Worked example
Promote a set of views from development to production where the Oracle data source uses different credentials. Reasoning: commit the elements as a revision, create a solution containing the views and their dependencies, run impact analysis to confirm nothing outside the solution breaks, configure the production environment's data source credentials, then deploy and verify by querying a production view. Hand-editing the data source in production afterwards would create drift that the next deployment overwrites.
Traps that cost marks
- Deploying a solution without its dependencies, so views fail on missing elements.
- Shipping development credentials and discovering it only at runtime.
- Making manual production edits that the next deployment silently reverts.
- Skipping impact analysis before replacing a widely used view.
- Assuming a deployment plan is read-only; reviewing the operations before applying matters.