Question 550 A prompt rollout is staged for 10% of traffic, but evaluation logs do not indicate which prompt version produced each response. What prevention measure is most targeted to this underlying cause? Record prompt/version attribution and canary rollback thresholds in deployment policy. Use immutable prompt versions, approval records and controlled release aliases. Mark minimum-safe prompt revisions and retest safety invariants on every rollback. Standardize three-level naming, registry configuration and permission smoke tests in release automation. ExplanationCorrect Answer A:Without treatment attribution, observed response changes cannot be confidently linked to the prompt revision. Other Answers B:That without treatment attribution, observed response changes cannot be confidently linked to the prompt revision. C:Without treatment attribution, observed response changes cannot be confidently linked to the prompt revision. D:This control addresses a different exposure: A team logs an MLflow model successfully but cannot find it in the approved Unity Catalog registry because it used an unqualified local registry name. It would not prevent this failure, because without treatment attribution, observed response changes cannot be confidently linked to the prompt revision.
Question 551 A security fix changes an agent's tool instructions, and an emergency rollback accidentally restores a previously vulnerable prompt. Which implementation decision best restores the intended behavior? Register a versioned prompt artifact and roll the serving application back to the last evaluated revision. Use approved server-side credentials and tool authentication with scoped network access, never model-visible plaintext secrets. Attach the immutable prompt revision ID to every trace and exposure record during the rollout. Maintain a security-approved baseline and disallow rollback targets that lack required current safety constraints. ExplanationCorrect Answer D:The action targets the stated cause: Rollback is a version selection operation; reverting blindly can reintroduce closed vulnerabilities. Check the repair by: attempt a rollback to a known unsafe revision and confirm the deployment gate rejects it. Other Answers A:Rollback is a version selection operation; reverting blindly can reintroduce closed vulnerabilities. B:Rollback is a version selection operation; reverting blindly can reintroduce closed vulnerabilities. C:Rollback is a version selection operation; reverting blindly can reintroduce closed vulnerabilities.
Question 552 A field-service chatbot works in a notebook but external users have no authenticated interface or way to connect it to an approved agent endpoint. Which engineering action most directly addresses this specific requirement? Deploy a user-facing interface through a supported Databricks Apps or approved channel integration with authenticated backend agent calls. Translate backend failures into safe user-facing error states, redact internals and keep detailed diagnostics in protected logs. Remove the client-side secret and use approved service or user authorization through a backend with only required endpoint permissions. Use an approved user-authorization pattern or enforce equivalent per-user data access checks behind the app service. ExplanationCorrect Answer A:The action targets the stated cause: A notebook or model endpoint is not a complete end-user application; session, identity and interaction boundaries need a serving front end. Check the repair by: sign in as a test user and verify a chat question invokes the right endpoint without exposing tokens. Other Answers B:A notebook or model endpoint is not a complete end-user application; session, identity and interaction boundaries need a serving front end. C:A notebook or model endpoint is not a complete end-user application; session, identity and interaction boundaries need a serving front end. D:A notebook or model endpoint is not a complete end-user application; session, identity and interaction boundaries need a serving front end.
Question 553 A field-service chatbot works in a notebook but external users have no authenticated interface or way to connect it to an approved agent endpoint. What architectural constraint is most directly responsible? The app service identity can have broader permissions than the caller; its successful query does not establish user entitlement. Browser code exposes embedded secrets to users; endpoint access must be authenticated and authorized at a trusted server boundary. A notebook or model endpoint is not a complete end-user application; session, identity and interaction boundaries need a serving front end. User interface error handling is a security boundary; propagating raw exceptions can expose credentials and system internals. ExplanationCorrect Answer C:Deploy a user-facing interface through a supported Databricks Apps or approved channel integration with authenticated backend agent calls. Other Answers A:A notebook or model endpoint is not a complete end-user application; session, identity and interaction boundaries need a serving front end. B:That mechanism describes another problem: A web application invokes an LLM serving endpoint using a developer's long-lived personal access token baked into front-end JavaScript. It does not explain this case, where a notebook or model endpoint is not a complete end-user application; session, identity and interaction boundaries need a serving front end. D:A notebook or model endpoint is not a complete end-user application; session, identity and interaction boundaries need a serving front end.
Question 554 A field-service chatbot works in a notebook but external users have no authenticated interface or way to connect it to an approved agent endpoint. What validation evidence would most specifically confirm the resolution? Trigger a simulated endpoint outage and verify the UI shows a neutral retry path while protected logs retain trace IDs. Sign in as a test user and verify a chat question invokes the right endpoint without exposing tokens. Compare responses for authorized and unauthorized users and confirm restricted rows are never returned. Inspect compiled assets for tokens, test requests with and without required permissions, and verify audit identity. ExplanationCorrect Answer B:A notebook or model endpoint is not a complete end-user application; session, identity and interaction boundaries need a serving front end. Other Answers A:Sign in as a test user and verify a chat question invokes the right endpoint without exposing tokens. C:Sign in as a test user and verify a chat question invokes the right endpoint without exposing tokens. D:Sign in as a test user and verify a chat question invokes the right endpoint without exposing tokens.
Question 555 A field-service chatbot works in a notebook but external users have no authenticated interface or way to connect it to an approved agent endpoint. What prevention measure is most targeted to this underlying cause? Test app authentication, sessions, input limits and errors before exposing an agent interface. Use managed identities, secret rotation and least-privilege endpoint grants instead of hard-coded personal tokens. Document identity propagation and audit user-scoped data access on every app release. Add error-redaction and graceful-failure tests to front-end acceptance criteria. ExplanationCorrect Answer A:A notebook or model endpoint is not a complete end-user application; session, identity and interaction boundaries need a serving front end. Other Answers B:This control addresses a different exposure: A web application invokes an LLM serving endpoint using a developer's long-lived personal access token baked into front-end JavaScript. It would not prevent this failure, because a notebook or model endpoint is not a complete end-user application; session, identity and interaction boundaries need a serving front end. C:That a notebook or model endpoint is not a complete end-user application; session, identity and interaction boundaries need a serving front end. D:A notebook or model endpoint is not a complete end-user application; session, identity and interaction boundaries need a serving front end.
Question 556 A Databricks App uses its service identity for every end-user data query and leaks rows that users cannot see in the dashboard. Which implementation decision best restores the intended behavior? Deploy a user-facing interface through a supported Databricks Apps or approved channel integration with authenticated backend agent calls. Translate backend failures into safe user-facing error states, redact internals and keep detailed diagnostics in protected logs. Add staging integration tests with the same scoped service-principal grants before production promotion. Use an approved user-authorization pattern or enforce equivalent per-user data access checks behind the app service. ExplanationCorrect Answer D:The action targets the stated cause: The app service identity can have broader permissions than the caller; its successful query does not establish user entitlement. Check the repair by: compare responses for authorized and unauthorized users and confirm restricted rows are never returned. Other Answers A:The app service identity can have broader permissions than the caller; its successful query does not establish user entitlement. B:The app service identity can have broader permissions than the caller; its successful query does not establish user entitlement. C:The app service identity can have broader permissions than the caller; its successful query does not establish user entitlement.
Question 557 A Databricks App uses its service identity for every end-user data query and leaks rows that users cannot see in the dashboard. Which underlying technical principle explains why this occurs? User interface error handling is a security boundary; propagating raw exceptions can expose credentials and system internals. A model endpoint credential is not a substitute for row-level or source-document entitlement enforcement. The app service identity can have broader permissions than the caller; its successful query does not establish user entitlement. A notebook or model endpoint is not a complete end-user application; session, identity and interaction boundaries need a serving front end. ExplanationCorrect Answer C:Use an approved user-authorization pattern or enforce equivalent per-user data access checks behind the app service. Other Answers A:That mechanism describes another problem: A new chat integration publishes raw agent exceptions and request headers in the user interface when model serving temporarily fails. It does not explain this case, where the app service identity can have broader permissions than the caller; its successful query does not establish user entitlement. B:The app service identity can have broader permissions than the caller; its successful query does not establish user entitlement. D:The app service identity can have broader permissions than the caller; its successful query does not establish user entitlement.
Question 558 A Databricks App uses its service identity for every end-user data query and leaks rows that users cannot see in the dashboard. After correction, what targeted test should demonstrate success? Trigger a simulated endpoint outage and verify the UI shows a neutral retry path while protected logs retain trace IDs. Sign in as a test user and verify a chat question invokes the right endpoint without exposing tokens. Execute allowed and forbidden model/index access tests in staging and verify the expected audit identities. Compare responses for authorized and unauthorized users and confirm restricted rows are never returned. ExplanationCorrect Answer D:The app service identity can have broader permissions than the caller; its successful query does not establish user entitlement. Other Answers A:Compare responses for authorized and unauthorized users and confirm restricted rows are never returned. B:Compare responses for authorized and unauthorized users and confirm restricted rows are never returned. C:Compare responses for authorized and unauthorized users and confirm restricted rows are never returned.
Question 559 A Databricks App uses its service identity for every end-user data query and leaks rows that users cannot see in the dashboard. Which release safeguard most directly addresses this failure class? Add error-redaction and graceful-failure tests to front-end acceptance criteria. Test app authentication, sessions, input limits and errors before exposing an agent interface. Document identity propagation and audit user-scoped data access on every app release. Make environment-specific least-privilege checks a required CI promotion gate. ExplanationCorrect Answer C:The app service identity can have broader permissions than the caller; its successful query does not establish user entitlement. Other Answers A:That the app service identity can have broader permissions than the caller; its successful query does not establish user entitlement. B:The app service identity can have broader permissions than the caller; its successful query does not establish user entitlement. D:This control addresses a different exposure: A Git workflow deploys an agent without running tests against the target workspace's security permissions, causing launch-time authorization failures. It would not prevent this failure, because the app service identity can have broader permissions than the caller; its successful query does not establish user entitlement.
Question 560 A new chat integration publishes raw agent exceptions and request headers in the user interface when model serving temporarily fails. Which design change directly satisfies the stated constraints? Package and deploy the custom model through supported Model Serving rather than assuming a managed Foundation Model API serves arbitrary uploaded weights. Use an approved user-authorization pattern or enforce equivalent per-user data access checks behind the app service. Deploy a user-facing interface through a supported Databricks Apps or approved channel integration with authenticated backend agent calls. Translate backend failures into safe user-facing error states, redact internals and keep detailed diagnostics in protected logs. ExplanationCorrect Answer D:The action targets the stated cause: User interface error handling is a security boundary; propagating raw exceptions can expose credentials and system internals. Check the repair by: trigger a simulated endpoint outage and verify the UI shows a neutral retry path while protected logs retain trace IDs. Other Answers A:User interface error handling is a security boundary; propagating raw exceptions can expose credentials and system internals. B:User interface error handling is a security boundary; propagating raw exceptions can expose credentials and system internals. C:User interface error handling is a security boundary; propagating raw exceptions can expose credentials and system internals.
