Cuestionario vinculado a una guía · Medio Nivel
Prueba de ingeniería de contexto
Prueba en qué se diferencia la ingeniería de contexto de las indicaciones, por qué el contexto es un presupuesto simbólico y técnicas como la carga justo a tiempo y el almacenamiento en caché de indicaciones.
Pregunta 1 de 8
What best distinguishes context engineering from prompt engineering?
Vista previa de cada pregunta8 preguntas
Las respuestas y explicaciones aparecen a medida que realiza el cuestionario.
- What best distinguishes context engineering from prompt engineering?
- It only concerns the wording of the user's question
- It covers everything the model sees, including retrieved data, tool results and memory, not just the wording
- It requires fine-tuning the model's weights
- It applies only to image-generation models
- What did the 'lost in the middle' research suggest about long inputs?
- Models read every part of a long input equally well
- Models ignore the beginning of their input
- Models often use information at the start and end of a long input better than information in the middle
- Models cannot process more than about 1,000 tokens
- Why does the guide describe context as a budget?
- Every token costs money and latency, and irrelevant material can distract the model
- Providers charge a flat monthly fee for context
- Models refuse inputs above a certain dollar amount
- The word refers only to the compute used in training
- What is just-in-time loading?
- Loading the entire codebase into the window at the start of a session
- Retraining the model whenever new data arrives
- Caching every model output permanently
- Giving the agent lightweight references, such as file names, and letting it fetch full content with tools when needed
- ¿Por qué es útil poner contenido estable, como instrucciones del sistema y definiciones de herramientas, al principio en un orden fijo?
- Hace que el modelo sea más creativo.
- Every API requires this order
- An identical prefix can be reused through prompt caching, which lowers cost and latency
- It hides the instructions from the user
- Which approach to tool design does the guide recommend?
- Tools should return all raw data so nothing is missed
- Tools should return concise, high-signal output and support filtering or pagination
- Many tools with overlapping descriptions give the model more choice
- Tool descriptions should be left empty to save tokens
- Which statement is a misconception the guide warns about?
- Large context windows increase cost per request
- Tool definitions take up tokens on every turn
- Retrieval can reduce how much text goes into the window
- A bigger context window removes the need to curate what goes in
- What role do sub-agents play in context engineering?
- They explore in their own separate context and return condensed findings to the main agent
- They double the context window of the main agent
- They replace the system prompt
- They store user passwords between sessions