The compliance team at a firm has approved a Claude Skill that generates client-facing investment summaries. The Skill includes the firm's required disclaimers and prohibited-language list. A product manager has asked whether additional guardrails are needed at the application layer or whether the Skill alone is sufficient.
Which two guardrail responsibilities should remain at the application layer rather than the Skill? (Select two.) Each correct answer presents part of the solution.

• A. Verify the requesting user is authorized to generate investment summaries at all.
• B. Format output sections according to the firm's standardized house style guidelines.
• C. Apply the disclaimer template that the compliance team has standardized firm-wide.
• D. Apply the prohibited-language list that the compliance team maintains and updates.
• E. Log every generated summary to the firm's compliance audit trail for retention.

You are reviewing a peer's end-to-end design for a Claude-based platform expected to scale to thousands of concurrent users.
For each statement, indicate Yes if it reflects sound architectural practice. Otherwise, select No.

When communicating an architectural decision to a security and compliance reviewer, which content set is most aligned with that audience's primary concerns?

• A. Decision rationale, business outcomes, and high-level risk summary for executive review.
• B. Threat model, control mappings, residual-risk acceptance criteria, and audit traceability.
• C. Feature delivery schedule, roadmap dependencies, and scope boundaries for the product manager.
• D. Implementation timeline, component interfaces, and deployment sequence for the engineering team.

You are running a discovery engagement for a new Claude-based capability and must complete the requirements-gathering steps before validating with stakeholders.
Which two steps must be completed BEFORE validating the captured requirements with stakeholders? (Select two.) Each correct answer presents part of the solution.

• A. Produce architecture decision records that capture the rationale for major design choices.
• B. Capture the business goals, success criteria, and the in-scope user population for the engagement.
• C. Schedule the rollout milestones and dependencies with engineering and product partners.
• D. Identify the non-functional constraints covering latency, cost, audit, data sensitivity, and regulatory needs.
• E. Document the consolidated requirements with traceability to the source stakeholder for each item.

You are reviewing a customer-support agent's configuration. Each candidate tool falls into one of four categories: (1) required to complete defined tasks, (2) frequently used and reduces hand-offs, (3) occasionally useful for unrelated work, (4) speculative future utility.
Which categories should typically remain in the agent configuration?

• A. Only category 4, because speculative future-utility tools provide the most flexibility and should be configured even when no defined task currently requires them.
• B. Only category 3, because occasionally useful tools for unrelated work provide broader coverage and should take priority over tools required for the agent's defined tasks.
• C. Categories 1 and 2 only, because they map to defined tasks and the agent's regular hand-offs.
• D. All four categories, because broader tool access is categorically better for agent performance regardless of whether the tools map to defined tasks or regular hand-offs.