面试题库

14 天用 Agent 搭一条 AI 短剧生产线

D11 质检与合规：机器审片、内容安全、生成内容标识与版权边界

• 内容安全审核放在生成前还是生成后？为什么两边都要有？Should content safety checks run before generation or after? Why both?

  国内高频海外高频基础#content-safety#moderation#pipeline-design

  分析过程 · 先想清楚再作答

  1. 这题的正确答案是「两边都要」，但拿分的关键不在结论，而在你能不能说清两道关**防的是不同的事**。答成「双重保险更稳妥」就是没答。
  2. 前置那道查的是你要发出去的提示词，省的是钱和账号：违规提示词发过去会命中厂商审核被拒（MiniMax 这边返回 1026 或 1027），白等一轮，严重的会触发风控。它是一层本地词表加规则，几毫秒，拦一条省一次调用。
  3. 后置那道查的是厂商还给你的成片，它更重要，理由是**提示词干净不代表结果干净**——生成模型会自己加戏，你写便利店门口，它可能给你摆一整面货架的品牌包装。前置只保证你没主动要，后置才保证观众看到的没问题。
  4. 前置被拦下之后不能只抛异常，要给替代方案并让流程继续：把命中片段替换成安全表述、打印出来、记进报告，人回头能看到哪一句被改成了什么。
  5. 还要点破一个常见误解：**厂商的审核不能替代你的审核**。厂商审的是它自己的合规风险，边界跟你的业务不同；而且发布责任在你，出事找的是发布者。
  6. 可预期的追问是「后置发现问题怎么办」。按严重程度分流：能自动修的（比如字幕里的词）就修完重跑那一个节点，修不了的直接拦住不许发布并推给人工，绝不能因为已经花了钱就放行。

  How to reason about it · think before answering

  1. The answer is both, but the marks come from explaining that the two gates defend against different things. Saying defence in depth is safer earns nothing.
  2. The pre-check inspects the prompt you are about to send, and it saves money and account standing: a violating prompt gets rejected by the vendor's own moderation (1026 or 1027 at MiniMax), wasting a round trip, and repeated hits can trip risk controls. It is a local word list plus rules, milliseconds, and each catch saves a call.
  3. The post-check inspects what the vendor returned, and it matters more, because a clean prompt does not imply a clean result. Generative models improvise: you ask for a convenience store and get a shelf of branded packaging. The pre-check only proves you did not ask for it; the post-check protects the viewer.
  4. When the pre-check fires, do not just throw. Offer a replacement and keep going: swap the matched fragment for safe wording, print it, and record it so a human can see which line was changed and how.
  5. Call out the common misconception: vendor moderation does not replace yours. The vendor moderates its own risk, with different boundaries, and publishing liability sits with you.
  6. Expected follow-up: what to do when the post-check fails. Triage by severity: auto-fixable issues get fixed and only that node reruns; anything else blocks publishing and goes to a human. Never wave it through because the money is already spent.

  答题要点

  • 两道都要，因为防的事不同：前置省钱与账号，后置保护观众与合规。
  • 前置是本地词表加规则，几毫秒，拦下一条就省一次调用；命中要给替代写法而不是抛异常停线。
  • 后置更重要：提示词干净不代表结果干净，模型会自己加戏。
  • 厂商的审核只兜它自己的风险，不能替代你的，发布责任在你。
  • 后置发现问题按严重度分流：能自动修的修完重跑该节点，修不了的硬拦并推人工。

  Key points

  • Both, because they defend different things: the pre-check saves spend and account standing, the post-check protects viewers and compliance.
  • The pre-check is a local rule pass in milliseconds; on a hit, substitute safe wording instead of throwing and halting the line.
  • The post-check matters more, because a clean prompt does not guarantee a clean result.
  • Vendor moderation covers the vendor's risk, not yours; publishing liability stays with you.
  • Triage post-check failures: auto-fix and rerun that node, or hard-block and escalate.