CPN Learning Path CPN Connect On Demand Library All Courses Home

Product Foundations

Before you can advise a client on Claude Code, you need to know what you're working with. This course covers what Claude Code is, how to pick between Haiku, Sonnet, and Opus, and how to match one of the four deployment paths to a client's cloud posture.

rate limit

Code not recognized.

About this course

Start here before anything else in the learning path. This course answers three questions that come up in every client conversation before a deployment gets underway.

The first is what Claude Code actually is. It runs in the terminal, not as an IDE plugin, and works agentically: reading files, writing code, running commands, working through multi-step tasks. That posture shapes how you scope the work, what you configure, and what you need to explain to the client's IT team.

The second is model selection. You'll get a practical look at the three Claude models; Haiku, Sonnet, and Opus, and the tradeoffs between cost, speed, and reasoning depth that point you toward the right one for a given workload. Most deployments start with Sonnet, but the recommendation needs a reason behind it.

The third is deployment path. Four options exist: Claude for Enterprise direct, Amazon Bedrock, Google Vertex AI, and Microsoft Foundry. The choice follows the client's cloud commitments, how procurement wants to buy, what compliance requires, and who manages seats and budgets. This course gives you the framework to make that call, before the client defaults to one without thinking.

The course closes with a five-question scenario check: three client profiles, and for each one you'll identify the right model and deployment combination. No hands-on artifact for this one, it's orientation before the practical work begins.

Time In Skilljar (Measured) 29 MinPractice & Artifact Building (Estimated Time In Skilljar) 15 Min

Curriculum

  • What Claude Code is and how it behaves in a codebase
  • Claude family model selection and tradeoffs
  • Platform options at a glance: Enterprise, API, deployment paths

About this course

Start here before anything else in the learning path. This course answers three questions that come up in every client conversation before a deployment gets underway.

The first is what Claude Code actually is. It runs in the terminal, not as an IDE plugin, and works agentically: reading files, writing code, running commands, working through multi-step tasks. That posture shapes how you scope the work, what you configure, and what you need to explain to the client's IT team.

The second is model selection. You'll get a practical look at the three Claude models; Haiku, Sonnet, and Opus, and the tradeoffs between cost, speed, and reasoning depth that point you toward the right one for a given workload. Most deployments start with Sonnet, but the recommendation needs a reason behind it.

The third is deployment path. Four options exist: Claude for Enterprise direct, Amazon Bedrock, Google Vertex AI, and Microsoft Foundry. The choice follows the client's cloud commitments, how procurement wants to buy, what compliance requires, and who manages seats and budgets. This course gives you the framework to make that call, before the client defaults to one without thinking.

The course closes with a five-question scenario check: three client profiles, and for each one you'll identify the right model and deployment combination. No hands-on artifact for this one, it's orientation before the practical work begins.

Time In Skilljar (Measured) 29 MinPractice & Artifact Building (Estimated Time In Skilljar) 15 Min

Curriculum

  • What Claude Code is and how it behaves in a codebase
  • Claude family model selection and tradeoffs
  • Platform options at a glance: Enterprise, API, deployment paths