Deployment, Migration, and Environment Management
Deployment questions test package-based promotion across dev → stage → prod. Know the package export/import mechanism (schemas, workflows, deliveries, forms, scripts), package dependencies, and the data vs. configuration distinction - packages carry config, not business data. Understand schema synchronization, delta/conflict handling, and the update database structure wizard. Candidates must know environment-specific settings (external accounts, URLs, credentials) that must be re-pointed after import, and the role of version control of exported packages.
Traps: assuming packages move data (they move definitions); forgetting that schema changes require a DB structure update after import; and importing a package that overwrites a production customization. Another classic: hardcoding environment URLs or credentials in workflows/scripts so promotion breaks. Also watch namespace conflicts if the same schema is customized in two environments.
Rule of thumb: promote definitions as packages, keep environment values in external accounts/config, and always run the DB update wizard post-import. Worked example: moving a new workflow + custom schema from dev to prod - export the schema and workflow in one package, import to stage, run the structure update, re-point the external account to prod SFTP, test with a small seed list, then promote to prod with a rollback package saved first.