CDC / RDC · All levels

RDC Signoff: Tricky Q&A

Senior interview and review questions for RDC Signoff.

Section Q&A bank

Use these drills after completing all topics in RDC Signoff. Answer with crossing class, mechanism, risk, evidence, owner, and signoff decision.

What is unique about RDC vs CDC?

diagram

[INT][CDC-RDC][RDC-SIGNOFF]

Q: What is unique about RDC vs CDC?

A:
RDC centers on reset control relationships and release ordering, often intertwined with boot and power sequences.

FOLLOW-UP TRAP: Running CDC checks only and calling reset safe.

Why is chip-level RDC harder than block-level?

diagram

[INT][CDC-RDC][RDC-SIGNOFF]

Q: Why is chip-level RDC harder than block-level?

A:
Subsystem reset assumptions interact and can conflict at integration boundaries.

FOLLOW-UP TRAP: Assuming local IP clean implies top-level clean.

What evidence closes RDC?

diagram

[INT][CDC-RDC][RDC-SIGNOFF]

Q: What evidence closes RDC?

A:
Structural hazard closure plus reset-aware simulation/formal evidence on critical bring-up paths.

FOLLOW-UP TRAP: Closing with structural report only.

Q&A drill guide

diagram

INTENT -> FAILURE MODE -> EVIDENCE -> FIX/WAIVER -> REGRESSION

Sketch while answering

diagram

RDC CLOSURE

IP reset intent + SoC sequencing -> structural checks -> dynamic stress -> signoff

Key takeaways

State crossing class, assumptions, and owner with every issue.
Run structural and dynamic regressions after each fix.

Common pitfalls

Treating all warnings as equivalent risk.
Waiving issues without containment evidence.
Skipping reset and reconvergence stress after CDC fixes.

Practice this lesson