A kelp-farm inventory deploy should ensure database kelp-db exists on first run and must not fail when the database is already present on later deploys. Which SDK approach fits?
Select an answer to reveal the explanation.
Short Explanation
First deploy builds the greenhouse; next deploy shouldn’t burn it down. Use create-if-not-exists so kelp-db appears once and later runs smile and move on.
Full Explanation
Cosmos DB SDK methods such as create-if-not-exists for databases make provisioning idempotent across redeploys. Blind non-idempotent create, destructive recreate-every-time, or portal-only creation either fail on reruns or skip automated deploy needs. ARM/Bicep may also provision resources, but this item targets the SDK idempotent create pattern.