AIP-C01 · Question #25
A company is building a multicloud generative AI (GenAI)-powered secret resolution application that uses Amazon Bedrock and Agent Squad. The application resolves secrets from multiple sources…
The correct answer is A. Use Step Functions Map states to run agent workflows in parallel. Pass updated secret metadata. Option A is the correct solution because it directly addresses all identified failure modes while preserving the existing Step Functions-based orchestration architecture with minimal redesign. Using Step Functions Map states enables parallel execution of secret resolution…
Question
A company is building a multicloud generative AI (GenAI)-powered secret resolution application that uses Amazon Bedrock and Agent Squad. The application resolves secrets from multiple sources, including key stores and hardware security modules (HSMs). The application uses AWS Lambda functions to retrieve secrets from the sources. The application uses AWS AppConfig to implement dynamic feature gating. The application supports secret chaining and detects secret drift. The application handles short-lived and expiring secrets. The application also supports prompt flows for templated instructions. The application uses AWS Step Functions to orchestrate agents to resolve the secrets and to manage secret validation and drift detection. The company finds multiple issues during application testing. The application does not refresh expired secrets in time for agents to use. The application sends alerts for secret drift, but agents still use stale data. Prompt flows within the application reuse outdated templates, which cause cascading failures. The company must resolve the performance issues. Which solution will meet this requirement?
Options
- AUse Step Functions Map states to run agent workflows in parallel. Pass updated secret metadata
- BUse Amazon Bedrock Agents only. Configure Amazon Bedrock guardrails to restrict prompt
- CUse a centralized Amazon EventBridge pipeline to invoke each agent. Store intermediate prompts
- DUse Amazon EventBridge Pipes to invoke resolvers based on Amazon CloudWatch log patterns.
How the community answered
(37 responses)- A70% (26)
- B8% (3)
- C5% (2)
- D16% (6)
Explanation
Option A is the correct solution because it directly addresses all identified failure modes while preserving the existing Step Functions-based orchestration architecture with minimal redesign. Using Step Functions Map states enables parallel execution of secret resolution workflows, which improves refresh latency for short-lived and expiring secrets. This ensures that secrets are refreshed in time before downstream agents require them. Passing updated secret metadata through Lambda outputs guarantees that subsequent steps always consume the latest resolved values, preventing agents from using stale data even after drift alerts are generated. Versioning prompt flows in AWS AppConfig is critical to resolving cascading failures caused by outdated templates. AppConfig natively supports version control, validation, staged rollout, and rollback of configuration artifacts. By gating prompt flows through AppConfig, the company can immediately roll back faulty templates and prevent agents from reusing outdated instructions. This solution maintains clear separation of concerns: Step Functions handle orchestration and parallelism, Lambda handles secret retrieval and metadata propagation, and AppConfig governs prompt lifecycle management. No additional event pipelines or custom retry coordination layers
Topics
Community Discussion
No community discussion yet for this question.