-
Notifications
You must be signed in to change notification settings - Fork 37
Expand file tree
/
Copy pathquiz.json
More file actions
78 lines (78 loc) · 2.42 KB
/
Copy pathquiz.json
File metadata and controls
78 lines (78 loc) · 2.42 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
{
"lesson": "19-ai-gateways",
"title": "AI 网关 —— LiteLLM、Portkey、Kong AI Gateway、Bifrost",
"questions": [
{
"stage": "pre",
"question": "本课中 AI 网关的核心角色是什么?",
"options": [
"一个模型微调服务",
"一个用于检索的向量数据库",
"一个仅做日志的 sidecar",
"一个位于应用与模型供应商之间的进程,把路由、回退、重试、限流、密钥引用、可观测性和护栏整合到同一个 API 之后"
],
"correct": 3,
"explanation": ""
},
{
"stage": "check",
"question": "Kong 的基准测试报告 LiteLLM 的规模天花板是多少?",
"options": [
"它在 50 RPS 时见顶",
"它在约 2000 RPS 附近崩溃,占用 8 GB 内存,并在持续负载下出现级联故障",
"它在超过 10k RPS 后仍线性扩展",
"LiteLLM 无法被基准测试"
],
"correct": 1,
"explanation": ""
},
{
"stage": "check",
"question": "按 Kong 在同等 CPU 上的基准测试,Kong AI Gateway 比 Portkey 和 LiteLLM 快多少?",
"options": [
"比 Portkey 快 228%,比 LiteLLM 快 859%",
"大约快 10% 和 20%",
"完全相同",
"比两者都慢"
],
"correct": 0,
"explanation": ""
},
{
"stage": "check",
"question": "本课把哪个网关定位为延迟开销 20-40 ms、聚焦护栏 / PII 脱敏 / 越狱检测?",
"options": [
"Kong AI Gateway",
"LiteLLM",
"Cloudflare AI Gateway",
"Portkey"
],
"correct": 3,
"explanation": ""
},
{
"stage": "post",
"question": "本课认为自托管与托管网关之间做决策的决定性因素(forcing function)是什么?",
"options": [
"网关是否开源",
"支持的供应商数量",
"每请求成本",
"数据驻留(data residency)要求"
],
"correct": 3,
"explanation": ""
},
{
"stage": "post",
"question": "当 SLA 为 TTFT P99 < 100 ms 时,哪些网关能保持在预算之内?",
"options": [
"任何网关",
"仅 Portkey",
"仅 LiteLLM",
"Kong(约 3-8 ms)或 Cloudflare/Vercel 边缘网关(约 1-3 ms);Portkey 在 20-40 ms 太重了"
],
"correct": 3,
"explanation": ""
}
]
}