Channel Configuration, Security, and Deployment
Domain 4 - Channel Configuration, Security, and Deployment. The exam tests the last mile: connecting a digital assistant to a messaging platform, controlling who can build and who can talk to it, and moving a build from development to production without breaking live channels.
Channels
A channel is a connector to a platform - web (via the Web SDK), Microsoft Teams, Slack, Facebook Messenger, Twilio SMS, WeChat, Alexa, Google Assistant, Service Cloud, or a custom channel. Each channel is configured against a specific DA version, has its own channel key and secret, and needs the platform side configured with the webhook or messaging endpoint the channel exposes. Because a channel pins a version, publishing a new DA version does not change what users see until the channel is updated.
Security
Security has two layers. OCI IAM policies govern the service instance with verbs such as manage oda-instance, use oda-instance and inspect oda-instance; inside the instance, roles control who trains, builds and publishes. End-user identity is separate: the web channel can require authentication through an identity provider using OAuth 2.0/OIDC, yielding a token whose claims populate the user profile for personalisation. Never accept a user id supplied by the client and treat it as verified.
Deployment
A typical lifecycle is build in a development instance, export the digital assistant and its skills, import into production, publish the skills, activate the DA version, then point channels at it. Referenced skill versions must exist in the target instance, or the import or activation fails.
Worked example
A Teams pilot: create the Teams channel, point it at DA version 1.2, paste the channel's messaging endpoint into the Teams app registration, and enable SSO so the user principal name fills the profile. On release you publish 1.3 and update the channel's version reference. Skip that step and Teams keeps serving 1.2 indefinitely.