Question 540 A Databricks-managed Genie MCP tool works in development, but a production custom agent cannot call it because the workspace identity lacks required data grants. What prevention measure is most targeted to this underlying cause? Make environment-specific least-privilege checks a required CI promotion gate. Require secret scanning, short-lived credentials and egress controls for custom MCP services. Maintain principal-to-tool-to-data entitlement maps for each managed MCP integration. Review MCP tool allowlists and credentials whenever a connector version changes. ExplanationCorrect Answer C:Managed MCP discovery does not automatically grant rights to governed tables or semantic resources. Other Answers A: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 managed MCP discovery does not automatically grant rights to governed tables or semantic resources. B:That managed MCP discovery does not automatically grant rights to governed tables or semantic resources. D:Managed MCP discovery does not automatically grant rights to governed tables or semantic resources.
Question 541 An engineering team hosts a custom MCP server in a Databricks App but passes API keys through plain prompt text rather than through authenticated tool transport. Which implementation decision best restores the intended behavior? Register and govern the connector with an allowlisted read-only tool subset and a scoped execution identity. Configure the production agent identity and Unity Catalog permissions for the managed data tool, then test the exact delegated query. Use approved server-side credentials and tool authentication with scoped network access, never model-visible plaintext secrets. Remove the client-side secret and use approved service or user authorization through a backend with only required endpoint permissions. ExplanationCorrect Answer C:The action targets the stated cause: MCP tool descriptions and model prompts are not secret-management boundaries; credentials belong in the service runtime. Check the repair by: inspect sampled tool traces and outbound requests to verify no API secrets appear in model context. Other Answers A:MCP tool descriptions and model prompts are not secret-management boundaries; credentials belong in the service runtime. B:MCP tool descriptions and model prompts are not secret-management boundaries; credentials belong in the service runtime. D:MCP tool descriptions and model prompts are not secret-management boundaries; credentials belong in the service runtime.
Question 542 An engineering team hosts a custom MCP server in a Databricks App but passes API keys through plain prompt text rather than through authenticated tool transport. Which underlying technical principle explains why this occurs? Browser code exposes embedded secrets to users; endpoint access must be authenticated and authorized at a trusted server boundary. MCP tool descriptions and model prompts are not secret-management boundaries; credentials belong in the service runtime. MCP provides a tool interface; access policies, authentication and individual tool permissions remain separate requirements. Managed MCP discovery does not automatically grant rights to governed tables or semantic resources. ExplanationCorrect Answer B:Use approved server-side credentials and tool authentication with scoped network access, never model-visible plaintext secrets. Other Answers A: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 mCP tool descriptions and model prompts are not secret-management boundaries; credentials belong in the service runtime. C:MCP tool descriptions and model prompts are not secret-management boundaries; credentials belong in the service runtime. D:MCP tool descriptions and model prompts are not secret-management boundaries; credentials belong in the service runtime.
Question 543 An updated system prompt causes unexpected refusal rates, but the production application stores the prompt only as an overwritten string. 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. Maintain a security-approved baseline and disallow rollback targets that lack required current safety constraints. Register a versioned prompt artifact and roll the serving application back to the last evaluated revision. Attach the immutable prompt revision ID to every trace and exposure record during the rollout. ExplanationCorrect Answer C:The action targets the stated cause: Mutable unversioned prompts break provenance and make rollback impossible even when the base model is unchanged. Check the repair by: restore the previous prompt version and compare refusal rates on a fixed regression set. Other Answers A:Mutable unversioned prompts break provenance and make rollback impossible even when the base model is unchanged. B:Mutable unversioned prompts break provenance and make rollback impossible even when the base model is unchanged. D:Mutable unversioned prompts break provenance and make rollback impossible even when the base model is unchanged.
Question 544 An updated system prompt causes unexpected refusal rates, but the production application stores the prompt only as an overwritten string. What is the decisive mechanism behind the observed result? Rollback is a version selection operation; reverting blindly can reintroduce closed vulnerabilities. Without treatment attribution, observed response changes cannot be confidently linked to the prompt revision. Generation depends on multiple independently mutable assets; unversioned prompt drift prevents reproducible rollbacks. Mutable unversioned prompts break provenance and make rollback impossible even when the base model is unchanged. ExplanationCorrect Answer D:Register a versioned prompt artifact and roll the serving application back to the last evaluated revision. Other Answers A:Mutable unversioned prompts break provenance and make rollback impossible even when the base model is unchanged. B:That mechanism describes another problem: A prompt rollout is staged for 10% of traffic, but evaluation logs do not indicate which prompt version produced each response. It does not explain this case, where mutable unversioned prompts break provenance and make rollback impossible even when the base model is unchanged. C:Mutable unversioned prompts break provenance and make rollback impossible even when the base model is unchanged.
Question 545 An updated system prompt causes unexpected refusal rates, but the production application stores the prompt only as an overwritten string. Which verification is strongest for this particular failure mode? 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. Attempt a rollback to a known unsafe revision and confirm the deployment gate rejects it. Partition traces by revision and verify traffic share and high-risk error rates against the rollout plan. ExplanationCorrect Answer A:Mutable unversioned prompts break provenance and make rollback impossible even when the base model is unchanged. Other Answers B:Restore the previous prompt version and compare refusal rates on a fixed regression set. C:Restore the previous prompt version and compare refusal rates on a fixed regression set. D:Restore the previous prompt version and compare refusal rates on a fixed regression set.
Question 546 An updated system prompt causes unexpected refusal rates, but the production application stores the prompt only as an overwritten string. What change to engineering governance would reduce this risk over time? Record prompt/version attribution and canary rollback thresholds in deployment policy. Require release metadata linking code, prompt, model and index versions for each environment. Mark minimum-safe prompt revisions and retest safety invariants on every rollback. Use immutable prompt versions, approval records and controlled release aliases. ExplanationCorrect Answer D:Mutable unversioned prompts break provenance and make rollback impossible even when the base model is unchanged. Other Answers A:This control addresses a different exposure: A prompt rollout is staged for 10% of traffic, but evaluation logs do not indicate which prompt version produced each response. It would not prevent this failure, because mutable unversioned prompts break provenance and make rollback impossible even when the base model is unchanged. B:That mutable unversioned prompts break provenance and make rollback impossible even when the base model is unchanged. C:Mutable unversioned prompts break provenance and make rollback impossible even when the base model is unchanged.
Question 547 A prompt rollout is staged for 10% of traffic, but evaluation logs do not indicate which prompt version produced each response. Which engineering action most directly addresses this specific requirement? Configure the Unity Catalog registry and register using the intended catalog.schema.model three-level name with appropriate privileges. Register a versioned prompt artifact and roll the serving application back to the last evaluated revision. Maintain a security-approved baseline and disallow rollback targets that lack required current safety constraints. Attach the immutable prompt revision ID to every trace and exposure record during the rollout. ExplanationCorrect Answer D:The action targets the stated cause: Without treatment attribution, observed response changes cannot be confidently linked to the prompt revision. Check the repair by: partition traces by revision and verify traffic share and high-risk error rates against the rollout plan. Other Answers A:Without treatment attribution, observed response changes cannot be confidently linked to the prompt revision. B: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.
Question 548 A prompt rollout is staged for 10% of traffic, but evaluation logs do not indicate which prompt version produced each response. What architectural constraint is most directly responsible? Mutable unversioned prompts break provenance and make rollback impossible even when the base model is unchanged. Logging artifacts and registering a governed model version are separate lifecycle operations; UC names include catalog and schema. Without treatment attribution, observed response changes cannot be confidently linked to the prompt revision. Rollback is a version selection operation; reverting blindly can reintroduce closed vulnerabilities. ExplanationCorrect Answer C:Attach the immutable prompt revision ID to every trace and exposure record during the rollout. Other Answers A:That mechanism describes another problem: An updated system prompt causes unexpected refusal rates, but the production application stores the prompt only as an overwritten string. It does not explain this case, where without treatment attribution, observed response changes cannot be confidently linked to the prompt revision. B:Without treatment attribution, observed response changes cannot be confidently linked to the prompt revision. D:Without treatment attribution, observed response changes cannot be confidently linked to the prompt revision.
Question 549 A prompt rollout is staged for 10% of traffic, but evaluation logs do not indicate which prompt version produced each response. What validation evidence would most specifically confirm the resolution? Attempt a rollback to a known unsafe revision and confirm the deployment gate rejects it. Partition traces by revision and verify traffic share and high-risk error rates against the rollout plan. Restore the previous prompt version and compare refusal rates on a fixed regression set. List the model version in the target catalog and verify its source run and access grants. ExplanationCorrect Answer B:Without treatment attribution, observed response changes cannot be confidently linked to the prompt revision. Other Answers A:Partition traces by revision and verify traffic share and high-risk error rates against the rollout plan. C:Partition traces by revision and verify traffic share and high-risk error rates against the rollout plan. D:Partition traces by revision and verify traffic share and high-risk error rates against the rollout plan.
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.
