用户原始简报第 9 节的硬指标:≥30 个完整场景决策题。本目录交付 32 题(EX01–EX32),四类各 8 题,每题完整八要素。这是把 13 个模块的知识收束为「架构师肌肉记忆」的练兵场——对应 CURRICULUM_PLAN.md 的场景题格式标准。
难度标注:★☆☆ 基础(单概念决策)|★★☆ 进阶(多概念权衡)|★★★ 综合(跨模块/陷阱题)。
| # | 标题 | 核心张力(英文) | 难度 | 所在文件 |
|---|---|---|---|---|
| EX01 | 法务合同库问答 | RAG or long context? | ★☆☆ | scenarios-retrieval-context.md |
| EX02 | 电信运营商 8M token 知识库 | RAG or long context? | ★☆☆ | scenarios-retrieval-context.md |
| EX03 | 客服 RAG 的「加料」提案 | more context or better retrieval? | ★★☆ | scenarios-retrieval-context.md |
| EX04 | 销售分析助手 | RAG or tool query / database? | ★★☆ | scenarios-retrieval-context.md |
| EX05 | 年度更新的编码手册 | fine-tuning or RAG? | ★★☆ | scenarios-retrieval-context.md |
| EX06 | 金标块总被忽略 | reranking + position (Lost in the Middle) | ★★☆ | scenarios-retrieval-context.md |
| EX07 | 竞品情报分析 | pre-built RAG or agentic search? | ★★☆ | scenarios-retrieval-context.md |
| EX08 | 多租户知识库 | prompt-level or retrieval-level permissions? | ★★★ | scenarios-retrieval-context.md |
| EX09 | 集团 AI 平台接入 30+ 系统 | API or MCP? | ★★☆ | scenarios-tools-mcp.md |
| EX10 | 创业公司的一个天气 API | API or MCP? | ★☆☆ | scenarios-tools-mcp.md |
| EX11 | 组织架构树与 wiki 库 | Tool or Resource? | ★★☆ | scenarios-tools-mcp.md |
| EX12 | 退款流水线 | Claude decides or application decides? | ★★☆ | scenarios-tools-mcp.md |
| EX13 | CRM 批量修改与外发邮件 | automatic write or human approval? | ★★☆ | scenarios-tools-mcp.md |
| EX14 | 支付工具超时 | retry, reconcile, or give up? (idempotency) | ★★★ | scenarios-tools-mcp.md |
| EX15 | 参数错误率高的录入 agent | strict tool use or prompt discipline? | ★★☆ | scenarios-tools-mcp.md |
| EX16 | 2MB 日志工具结果 | trim, summarize, or server-side processing? | ★★☆ | scenarios-tools-mcp.md |
| EX17 | 日均 5000 份合同审查 | Workflow or agent? | ★☆☆ | scenarios-agents-orchestration.md |
| EX18 | 退款审批的灰区判断 | Agent or deterministic code? | ★★☆ | scenarios-agents-orchestration.md |
| EX19 | 每日并购尽调报告 | Single or multi-agent? | ★★☆ | scenarios-agents-orchestration.md |
| EX20 | 跨模块代码重构 | Single or multi-agent?(反例) | ★★☆ | scenarios-agents-orchestration.md |
| EX21 | 十分钟后要的文档摘要 | synchronous or asynchronous? | ★☆☆ | scenarios-agents-orchestration.md |
| EX22 | 实时客服 + 疑难工单分层 | synchronous or asynchronous? | ★★☆ | scenarios-agents-orchestration.md |
| EX23 | 研究型 agent 不收敛 | stopping conditions & budgets | ★★☆ | scenarios-agents-orchestration.md |
| EX24 | 千条评论双视角分析 | parallelization pattern (fan-out/voting) | ★★☆ | scenarios-agents-orchestration.md |
| EX25 | 客服流量 85/15 分层 | larger model or smaller model? | ★☆☆ | scenarios-production-security.md |
| EX26 | 抽取任务 F1 卡在 0.82 | larger model or better prompt? | ★★☆ | scenarios-production-security.md |
| EX27 | 100k token 知识前缀 | cache or not cache? | ★★☆ | scenarios-production-security.md |
| EX28 | 高度个性化的实时前缀 | cache or not cache?(反例) | ★★☆ | scenarios-production-security.md |
| EX29 | HR 数据库的部门隔离 | which layer enforces permissions? | ★★☆ | scenarios-production-security.md |
| EX30 | 邮件里的注入指令 | which layer prevents exfiltration? | ★★★ | scenarios-production-security.md |
| EX31 | 大促期间 API 529 | retry strategy under overload | ★★☆ | scenarios-production-security.md |
| EX32 | 夜间 20 万条评估请求 | Batch API or synchronous? (cost) | ★☆☆ | scenarios-production-security.md |
questions/ 的场景题提炼改写为独立练习(场景、约束、选项均已重写,与原题不构成复制);其余为本目录新创作。ARCHITECTURE_CHEATSHEET.md(速查)和 13-capstone-project(决策工作簿)互补:本目录管「练」,那两处管「查」与「用」。