Question 520 A customer calls back after a service restart, but the agent's in-process dictionary lost the order_id and current workflow phase. What prevention measure is most targeted to this underlying cause? Version session schemas and test recovery, expiration and ownership transitions. Enforce tenant-bound keys and periodic session revocation tests. Make environment-specific least-privilege checks a required CI promotion gate. Apply field-level retention rules, encryption and memory redaction tests. ExplanationCorrect Answer A:Process memory is ephemeral and fails across restarts or scaled replicas; durable state requires explicit storage and authorization. Other Answers B:That process memory is ephemeral and fails across restarts or scaled replicas; durable state requires explicit storage and authorization. C:Process memory is ephemeral and fails across restarts or scaled replicas; durable state requires explicit storage and authorization. D:This control addresses a different exposure: A conversational agent keeps raw OAuth tokens and complete customer records in its persistent memory table for convenience. It would not prevent this failure, because process memory is ephemeral and fails across restarts or scaled replicas; durable state requires explicit storage and authorization.
Question 521 Two users share a guessed session key, and an agent returns one user's private prior messages to the other. Which implementation decision best restores the intended behavior? Store only approved non-sensitive conversation state and keep secrets in managed credential storage with short-lived tool access. Scope durable memory to authenticated user/tenant identity and use unguessable session identifiers with server-side ACL enforcement. Remove the client-side secret and use approved service or user authorization through a backend with only required endpoint permissions. Persist essential typed session state in an authorized durable store keyed by session and user identity, then resume safely. ExplanationCorrect Answer B:The action targets the stated cause: A session identifier alone is not proof of authorization; memory reads must check identity before returning state. Check the repair by: attempt cross-user access with a stolen session ID and verify denial plus audit evidence. Other Answers A:A session identifier alone is not proof of authorization; memory reads must check identity before returning state. C:A session identifier alone is not proof of authorization; memory reads must check identity before returning state. D:A session identifier alone is not proof of authorization; memory reads must check identity before returning state.
Question 522 Two users share a guessed session key, and an agent returns one user's private prior messages to the other. Which underlying technical principle explains why this occurs? A session identifier alone is not proof of authorization; memory reads must check identity before returning state. Persisted memory expands the exposure and retention of sensitive data; tool authentication is separate from session context. Browser code exposes embedded secrets to users; endpoint access must be authenticated and authorized at a trusted server boundary. Process memory is ephemeral and fails across restarts or scaled replicas; durable state requires explicit storage and authorization. ExplanationCorrect Answer A:Scope durable memory to authenticated user/tenant identity and use unguessable session identifiers with server-side ACL enforcement. Other Answers B:A session identifier alone is not proof of authorization; memory reads must check identity before returning state. C:A session identifier alone is not proof of authorization; memory reads must check identity before returning state. D:That mechanism describes another problem: A customer calls back after a service restart, but the agent's in-process dictionary lost the order_id and current workflow phase. It does not explain this case, where a session identifier alone is not proof of authorization; memory reads must check identity before returning state.
Question 523 Developers manually copy an agent notebook and vector-search configuration into production, accidentally pointing the prod app at the dev catalog. What is the most targeted corrective step for this observed failure? Version prompt, model artifact, retrieval configuration and bundle commit together as one promotion unit. Add staging integration tests with the same scoped service-principal grants before production promotion. Supply compatible query embeddings and a matching indexed vector representation or choose an index configuration with managed embedding support. Define environment-specific catalog, model endpoint and index bindings in a reviewed Declarative Automation Bundle deployment. ExplanationCorrect Answer D:The action targets the stated cause: Manual configuration drift can silently redirect production to incorrect data and model resources across environments. Check the repair by: deploy to staging and inspect resolved resource names; verify production uses only production catalog IDs. Other Answers A:Manual configuration drift can silently redirect production to incorrect data and model resources across environments. B:Manual configuration drift can silently redirect production to incorrect data and model resources across environments. C:Manual configuration drift can silently redirect production to incorrect data and model resources across environments.
Question 524 Developers manually copy an agent notebook and vector-search configuration into production, accidentally pointing the prod app at the dev catalog. What is the decisive mechanism behind the observed result? Manual configuration drift can silently redirect production to incorrect data and model resources across environments. Local unit tests cannot establish real workspace permissions or endpoint accessibility under deployment identity. Vector nearest-neighbor queries operate on numerical embeddings; text cannot be compared as vectors without encoding. Generation depends on multiple independently mutable assets; unversioned prompt drift prevents reproducible rollbacks. ExplanationCorrect Answer A:Define environment-specific catalog, model endpoint and index bindings in a reviewed Declarative Automation Bundle deployment. Other Answers B:That mechanism describes another problem: A Git workflow deploys an agent without running tests against the target workspace's security permissions, causing launch-time authorization failures. It does not explain this case, where manual configuration drift can silently redirect production to incorrect data and model resources across environments. C:Manual configuration drift can silently redirect production to incorrect data and model resources across environments. D:Manual configuration drift can silently redirect production to incorrect data and model resources across environments.
Question 525 Developers manually copy an agent notebook and vector-search configuration into production, accidentally pointing the prod app at the dev catalog. Which verification is strongest for this particular failure mode? Compare deployment manifest hashes and reproduce a known answer using the previous release bundle. Execute allowed and forbidden model/index access tests in staging and verify the expected audit identities. Submit a known query vector of the proper dimension and verify expected document IDs at the top of results. Deploy to staging and inspect resolved resource names; verify production uses only production catalog IDs. ExplanationCorrect Answer D:Manual configuration drift can silently redirect production to incorrect data and model resources across environments. Other Answers A:Deploy to staging and inspect resolved resource names; verify production uses only production catalog IDs. B:Deploy to staging and inspect resolved resource names; verify production uses only production catalog IDs. C:Deploy to staging and inspect resolved resource names; verify production uses only production catalog IDs.
Question 526 Developers manually copy an agent notebook and vector-search configuration into production, accidentally pointing the prod app at the dev catalog. What change to engineering governance would reduce this risk over time? Make environment-specific least-privilege checks a required CI promotion gate. Validate embedding dimensions, model revision and query interface on every index deployment. Require release metadata linking code, prompt, model and index versions for each environment. Use parameterized environment targets, peer review and automated resource-diff checks. ExplanationCorrect Answer D:Manual configuration drift can silently redirect production to incorrect data and model resources across environments. Other Answers A:That manual configuration drift can silently redirect production to incorrect data and model resources across environments. B:Manual configuration drift can silently redirect production to incorrect data and model resources across environments. C:This control addresses a different exposure: A CI pipeline upgrades prompt text but leaves the registered model artifact unchanged and provides no way to identify the deployed combination. It would not prevent this failure, because manual configuration drift can silently redirect production to incorrect data and model resources across environments.
Question 527 A CI pipeline upgrades prompt text but leaves the registered model artifact unchanged and provides no way to identify the deployed combination. Which engineering action most directly addresses this specific requirement? Register a versioned prompt artifact and roll the serving application back to the last evaluated revision. Add staging integration tests with the same scoped service-principal grants before production promotion. Version prompt, model artifact, retrieval configuration and bundle commit together as one promotion unit. Define environment-specific catalog, model endpoint and index bindings in a reviewed Declarative Automation Bundle deployment. ExplanationCorrect Answer C:The action targets the stated cause: Generation depends on multiple independently mutable assets; unversioned prompt drift prevents reproducible rollbacks. Check the repair by: compare deployment manifest hashes and reproduce a known answer using the previous release bundle. Other Answers A:Generation depends on multiple independently mutable assets; unversioned prompt drift prevents reproducible rollbacks. B:Generation depends on multiple independently mutable assets; unversioned prompt drift prevents reproducible rollbacks. D:Generation depends on multiple independently mutable assets; unversioned prompt drift prevents reproducible rollbacks.
Question 528 A CI pipeline upgrades prompt text but leaves the registered model artifact unchanged and provides no way to identify the deployed combination. What architectural constraint is most directly responsible? Mutable unversioned prompts break provenance and make rollback impossible even when the base model is unchanged. Manual configuration drift can silently redirect production to incorrect data and model resources across environments. Generation depends on multiple independently mutable assets; unversioned prompt drift prevents reproducible rollbacks. Local unit tests cannot establish real workspace permissions or endpoint accessibility under deployment identity. ExplanationCorrect Answer C:Version prompt, model artifact, retrieval configuration and bundle commit together as one promotion unit. Other Answers A:Generation depends on multiple independently mutable assets; unversioned prompt drift prevents reproducible rollbacks. B:Generation depends on multiple independently mutable assets; unversioned prompt drift prevents reproducible rollbacks. D:That mechanism describes another problem: A Git workflow deploys an agent without running tests against the target workspace's security permissions, causing launch-time authorization failures. It does not explain this case, where generation depends on multiple independently mutable assets; unversioned prompt drift prevents reproducible rollbacks.
Question 529 A CI pipeline upgrades prompt text but leaves the registered model artifact unchanged and provides no way to identify the deployed combination. What validation evidence would most specifically confirm the resolution? Execute allowed and forbidden model/index access tests in staging and verify the expected audit identities. Restore the previous prompt version and compare refusal rates on a fixed regression set. Compare deployment manifest hashes and reproduce a known answer using the previous release bundle. Deploy to staging and inspect resolved resource names; verify production uses only production catalog IDs. ExplanationCorrect Answer C:Generation depends on multiple independently mutable assets; unversioned prompt drift prevents reproducible rollbacks. Other Answers A:Compare deployment manifest hashes and reproduce a known answer using the previous release bundle. B:Compare deployment manifest hashes and reproduce a known answer using the previous release bundle. D:Compare deployment manifest hashes and reproduce a known answer using the previous release bundle.
Question 530 A CI pipeline upgrades prompt text but leaves the registered model artifact unchanged and provides no way to identify the deployed combination. What prevention measure is most targeted to this underlying cause? Require release metadata linking code, prompt, model and index versions for each environment. Use immutable prompt versions, approval records and controlled release aliases. Use parameterized environment targets, peer review and automated resource-diff checks. Make environment-specific least-privilege checks a required CI promotion gate. ExplanationCorrect Answer A:Generation depends on multiple independently mutable assets; unversioned prompt drift prevents reproducible rollbacks. Other Answers B:Generation depends on multiple independently mutable assets; unversioned prompt drift prevents reproducible rollbacks. C:This control addresses a different exposure: Developers manually copy an agent notebook and vector-search configuration into production, accidentally pointing the prod app at the dev catalog. It would not prevent this failure, because generation depends on multiple independently mutable assets; unversioned prompt drift prevents reproducible rollbacks. D:That generation depends on multiple independently mutable assets; unversioned prompt drift prevents reproducible rollbacks.
