Agent Application DevelopmentAccount
Knowledge catalogChoose core direction and segmented content

KNOWLEDGE PRACTICE / INTERVIEW QUESTIONS

Agent engineering practice

Interview questions are used to check knowledge understanding, practice expression and derive engineering solutions. Answer independently first, and then compare and analyze; when encountering weak points, return to the corresponding knowledge to explain and complete them.

How do practice questions check understanding?

Choose the direction of knowledge you are learning, explain the principles, premises and boundaries independently, and then analyze and find out the omissions. When you need to make up lessons, use "Learn Corresponding Knowledge" to return to the explanation; when you need to verify the implementation, complete the hands-on tasks on the page.

The questions are designed based on public official information and engineering boundaries. The scale, faults and goals in the cases are teaching assumptions. The reference materials support the technical mechanism, and the Q&A, migration scenarios and self-evaluation standards are designed by this site.

When preparing for the interview, explain the principles, boundaries, and trade-offs in your own words, and then check against the basic compliance, intermediate and advanced signals, and senior signals. Reading records and single answers do not directly represent mastery.

Exercises found: 64

31
Long-running tasks and reliable executionAdvancedSystem designAbout 15 minutes

Lease takeover and fencing stale workers

Two Workers resume an Agent task at the same time. How to use lease and Fencing Token to prevent the old Worker from writing?

The lease is responsible for taking over, the monotonically increasing token is responsible for rejecting expired writes, and the business side effects must still be independently constrained.

WorkerleaseFencing TokenConcurrency control
38
Evaluation and quality assuranceIntermediateSystem designAbout 12 minutes

Executable acceptance checks and quality boundaries

How does the Agent define an executable acceptance contract to avoid going online based solely on "the answer looks good"?

Convert results, permissions, evidence, resource costs and recovery capabilities into decidable conditions, and then combine them into release access control.

Reviewacceptance contractReturnRelease access control
39
Evaluation and quality assuranceAdvancedConceptsAbout 13 minutes

Evaluate both outcomes and execution traces

The final result is correct, does the Agent trajectory still need to be evaluated? How to avoid misjudging different correct paths?

Use result postconditions, partial ordering of necessary events, and prohibited behaviors to evaluate trajectories without forcing all tool calls to be exactly the same.

Track evaluationTool callpartial orderObservability
46
Production operations and securityAdvancedSystem designAbout 15 minutes

Approval targets and execution-time authorization

Agent can call the writing tool. How to prevent parameters from being modified after exceeding authority and approval?

Implement permission checks at the tool execution boundary, bind approval to immutable parameters and resource versions, and reject prompt injection to expand authorization.

Permission isolationManual approvalMCPPrompt Injection
61
Model calls and application boundariesFundamentalsConceptsAbout 12 minutes

Token accounting, context capacity, and generation headroom

What are the constraints on token, context window and output upper limit respectively? How do you leave room for the next round?

Use a concrete budget example to distinguish input capacity, generation limits, and next-turn headroom, then decide when to split, filter, or compress.

Tokencontext windowOutput budgetTruncateevidence use
62
Model calls and application boundariesFundamentalsConceptsAbout 16 minutes

Boundaries between learned capabilities, contextual evidence, and task behavior

What do pretraining, RAG and fine-tuning change? Why are corporate knowledge questions and answers often used in combination?

Distinguish between capabilities in parameters, evidence in requests, and post-training behavior, and select adaptation methods based on failure reasons.

pre-trainingRAGfine-tuningModel adaptation
63
Model calls and application boundariesFundamentalsConceptsAbout 12 minutes

Model-response lifecycle and completion semantics

Does text or a tool request mean the model has finished? How should a disconnected stream be classified?

Judge the end of transfer, model termination, output type and tool results separately to know which fragments can be previewed and which states can be delivered.

Model interfaceResponse life cycleStreaming outputtool requestreject and truncate
64
Model calls and application boundariesFundamentalsImplementationAbout 20 minutes

Prompt iteration, evidence support, and independent acceptance checks

How to verify that a prompt modification improves business answers without destroying the boundaries between evidence and rejection?

Differentiate structure, provenance, policy fields, and free text support with the same task set, retaining failures and comparing old and new versions.

PromptStructured OutputEvidenceRegression