CCA-F Domain 5 Study Guide: Configuration and Knowledge Management
Domain 5 (12%, ~7 items) — scoping Projects, writing durable system instructions, managing uploaded knowledge and connectors, and keeping it all current.
Domain weight: 12% (approximately 7 of 60 items). Based on Exam Guide Version 1.0, effective July 2026; study-guide edition updated August 1, 2026.
Domain purpose
Domain 5 tests whether an Associate can configure a dependable Claude workspace: place related work in the right Project, write durable instructions, supply approved knowledge, use connectors appropriately, and keep the configuration current.
This is not a repeat of individual prompt writing. Domain 1 covers the request for one task. Domain 5 covers the shared environment that influences many tasks over time.
Official objectives
Candidates are expected to:
- Configure Claude Projects with instructions and knowledge sources.
- Manage uploaded knowledge and connectors, such as Google Drive and Gmail.
- Create effective system-level instructions.
- Inform, maintain, and update Claude configurations, knowledge sources, and instructions.
Configuration framework: scope
SCOPE is a study framework, not an official Anthropic acronym.
| Letter | Element | Key question |
|---|---|---|
| S | Specific purpose | What recurring work belongs here? |
| C | Controlled sources | Which approved files, links, and connectors supply knowledge? |
| O | Operating instructions | What stable behavior, terminology, output conventions, and boundaries apply? |
| P | Permissions and people | Who can access, edit, share, or act through this workspace? |
| E | Evergreen maintenance | Who reviews sources, instructions, versions, and stale content? |
Configure a project
Anthropic describes Projects as self-contained workspaces with their own chat histories and knowledge bases. A well-configured Project has one coherent purpose.
| Good Project examples | Weak Project example |
|---|---|
| Marketing Campaign Operations; University Accreditation Support; Customer Service Policy Assistant; Quarterly Business Review Preparation | “Everything for the company” with unrelated files, audiences, and instructions. |
4.1 Project purpose statement
Define:
- Users
- Recurring tasks
- Permitted source material
- Expected deliverables
- What is outside scope
- Owner and review cycle
4.2 Project instructions
Use Project instructions for stable rules across related chats:
- Organization terminology
- Audience defaults
- Approved source priority
- Standard format
- Missing-information behavior
- Confidentiality reminder
- Escalation conditions
Do not bury temporary task details in permanent instructions.
4.3 Project knowledge
Add approved, relevant sources that users repeatedly need. Examples:
- Current policy manuals
- Brand guidelines
- Product documentation
- Curriculum material
- Templates
- Controlled terminology
Knowledge is context, not automatic truth. Files can become stale, conflict, or contain errors.
Write system-level instructions
System-level or Project instructions should be durable, concise, and broadly applicable to the Project. Useful structure:
| Section | What it covers |
|---|---|
| Purpose | What this Project supports. |
| Source priority | Which sources are authoritative when they conflict. |
| Working rules | Required terminology, audience, tone, and methods. |
| Output defaults | Common deliverable structure and level of detail. |
| Limitations | What Claude must not assume, disclose, or decide. |
| Escalation | When to seek a person or specialist. |
Example: “Use the approved HR Policy Manual as the primary source for policy questions. If a question is not addressed, say so and direct the user to HR Operations. Do not infer exceptions. Write for employees in plain language and cite the relevant policy heading.”
Avoid:
- Conflicting rules
- Copied instructions from unrelated Projects
- Obsolete dates and personnel
- Vague statements such as “always be perfect”
- Sensitive credentials
- Instructions too long for users to maintain
Manage uploaded knowledge
6.1 Before adding a source
Check:
- Relevance
- Authority
- Ownership and permission
- Sensitivity
- Version and effective date
- Duplication
- Expected update frequency
6.2 Name files clearly
| Prefer | Avoid |
|---|---|
| Travel_Policy_2026-07_Approved.pdf | final_new_latest2.pdf |
6.3 Record metadata
For important sources, retain owner, approval status, effective date, next review date, and replaced version.
6.4 Resolve conflicts
If two files disagree:
- Identify the source owner
- Compare effective dates and approval status
- Remove or archive the superseded source
- Update instructions if source priority changes
- Test common questions again
Do not expect Claude to determine organizational authority from filenames alone.
6.5 Remove irrelevant and stale knowledge
More files do not automatically improve performance. Outdated policies and duplicate drafts can produce conflicting answers.
Use connectors appropriately
Connectors allow Claude to retrieve information from and, depending on the connector and permissions, take actions in external services.
Current Anthropic help guidance states that connectors inherit the user's permissions from the connected service. If the user cannot access a record in the source system, the connector cannot access it on the user's behalf. Organization owners may also restrict connector actions.
7.1 Uploaded file versus connector
| Upload a file when | Use a connector when |
|---|---|
| A controlled snapshot is required; the source changes infrequently; the exact reviewed version must remain fixed. | Information changes frequently; the source system is authoritative; live retrieval reduces manual uploads; permissions and organizational policy allow it. |
7.2 Google Drive
Current help guidance says Google Docs added through the Drive connector can sync from Drive, supporting work with the latest version. Availability and shared-Project behavior may vary; verify current product documentation.
7.3 Gmail and other connected sources
Use connectors only for a defined business need. Search and retrieval may expose information that is technically accessible but inappropriate for the task. Apply least access, source-system permissions, and organizational policy.
7.4 Read versus write
Review connector capabilities before use. Searching email is different from sending email; reading an issue is different from creating or closing one. Prefer review and confirmation for consequential actions.
7.5 Trust
Only connect services and custom connectors that the user and organization trust. Connection can grant access to data or actions within the user's permissions.
Maintain the configuration
Assign ownership. A Project without an owner gradually accumulates stale instructions and sources.
Use a review cycle based on change rate:
- Fast-changing operational data: Frequent review or live connector.
- Monthly procedures: Monthly check.
- Annual policy: Review at approval and before effective-date changes.
- Brand or terminology: Review when governance changes.
Maintenance checklist:
- Confirm purpose remains valid
- Review user access and sharing
- Test connectors
- Verify source owners and dates
- Remove superseded material
- Resolve contradictions
- Simplify instructions
- Test representative questions
- Record changes
- Communicate material updates
Use a small change log with columns: Date | Change | Reason | Owner | Test completed.
Common traps
- One Project for unrelated work.
- Treating Project knowledge as automatically current.
- Keeping approved and draft policies together without labels.
- Putting temporary task details into permanent instructions.
- Duplicating conflicting instructions.
- Uploading sensitive files merely because access is technically possible.
- Assuming connectors have no action capability.
- Assuming a connector bypasses or expands source-system permissions.
- Using a static upload when live authoritative data changes frequently.
- Using a live source when a fixed audited snapshot is required.
- Failing to assign an owner and review date.
- Adding more files instead of curating relevant files.
Seven-day study plan
- Day 1: Design one focused Project purpose and scope.
- Day 2: Write concise durable Project instructions.
- Day 3: Audit a sample knowledge set for authority, date, duplication, and sensitivity.
- Day 4: Compare uploaded snapshot and connector use cases.
- Day 5: Create ownership, review-cycle, and change-log templates.
- Day 6: Diagnose five configuration failure scenarios.
- Day 7: Complete the seven questions and build a one-page SCOPE checklist.
Use Project and connector blog articles for walkthroughs, but recheck current help pages because availability and permissions change.
Readiness checklist
Rate your confidence on each item to gauge readiness for Domain 5.
- 1 — Not confident
- 2 — Somewhat confident
- 3 — Confident
| Statement | Your score |
|---|---|
| I can define a focused Project purpose. | |
| I distinguish permanent instructions from one-time prompts. | |
| I curate sources by relevance, authority, version, and sensitivity. | |
| I can choose upload versus connector. | |
| I understand inherited permissions and read/write capability. | |
| I can resolve conflicting or stale sources. | |
| I assign ownership, review dates, tests, and a change log. |
Your total
0 / 21
Score all 7 statements to see your verdict — 7 left.
| Total | Verdict | Next action |
|---|---|---|
| 7–12 | Not yet ready | Revisit the SCOPE framework and redo the seven-day plan before testing yourself again. |
| 13–18 | Getting there | Focus on your lowest-scoring items, especially connector governance and maintenance routines. |
| 19–21 | Ready | You can confidently handle Domain 5 configuration and knowledge-management scenarios. |
Sources
Primary: Claude Certified Associate - Foundations Exam Guide, Version 1.0, effective July 2026.
- Projects: https://support.claude.com/en/articles/9517075-what-are-projects
- Manage Projects and Project memory: https://support.claude.com/en/articles/9519177-how-can-i-create-and-manage-projects
- Connectors: https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities
- Google Workspace connectors: https://support.claude.com/en/articles/10166901-use-google-workspace-connectors
- Enterprise role permissions: https://support.claude.com/en/articles/13930458-set-up-role-based-permissions-on-enterprise-plans