When using prebuilt templates in AI Agent Studio, which two actions are supported?

AI Agent Studio in Oracle Digital Assistant accelerates agent development through prebuilt templates. Option C is correct because the studio provides a catalog of Oracle-delivered templates for various domains (e.g., HR, Sales), enabling users to rapidly configure and deploy a functional agent. Option A is also correct as these templates serve as a foundation. After selecting a template, developers must customize and design the single-agent's specific conversational flows, intents, and integrations to align with their unique business requirements. This customization is a core part of the design process.

B: This describes a platform-level lifecycle management feature for templates themselves, not a supported action for a user who is using a template to build an agent.

D: This refers to migrating or importing agents from external systems, which is a separate functionality and the opposite of using Oracle's own prebuilt templates as a starting point.

1. Oracle Cloud Infrastructure Documentation - Oracle Digital Assistant

"Get Started with AI Agent Studio": This document states

"AI Agent Studio provides a catalog of pre-built agent templates that you can use to quickly create and deploy agents for various use cases... After you create an agent from a template

you can customize it to meet your specific requirements." This directly supports options C and A.

2. Oracle Cloud Infrastructure Documentation - Oracle Digital Assistant

"Create an Agent from a Template": This section details the process: "You can create an agent by selecting a template from the catalog... The template provides a pre-configured set of intents

entities

and dialog flows that you can customize." This confirms that users select from a catalog (C) and then design/customize the workflow (A).