AIP-C01 Exam Preparation Material | AWS Certified Generative AI Developer - Professional

Explanation:
This scenario requires strict data residency, regional processing, classification, and auditable decision trails, which Option C addresses using AWS-native governance services.
Region-specific Amazon S3 buckets enforce geographic data boundaries. Amazon S3 Object Lock ensures immutability of stored data and logs, supporting regulatory retention and non-repudiation requirements. Pre-processing data within the same Region before invoking Amazon Bedrock ensures that inference and data handling do not cross continental boundaries.
Amazon Macie provides managed, automated data classification for sensitive data types such as PII and financial records, fulfilling the classification requirement without custom tooling.
AWS CloudTrail immutable logs provide comprehensive audit trails of all API calls, model invocations, and data access events, ensuring traceability of AI decision-making processes.
Option A violates residency rules through cross-Region inference.
Option B does not provide data classification.
Option D introduces high operational overhead and relies on manual compliance reporting.
Therefore, Option C is the most compliant, scalable, and operationally efficient solution for regionally governed GenAI workloads.

Explanation:
Option C best meets the requirements by aligning with AWS best practices for data isolation, access control, and scalable GenAI retrieval. Implementing a separate Amazon Bedrock knowledge base for each hotel ensures strict separation of data and permissions. This approach naturally enforces hotel-level access control without requiring complex policy logic or post-query filtering.
A multi-account structure further strengthens security and governance by isolating each hotel’s data plane. AWS recommends account-level isolation for workloads with strong tenancy or compliance boundaries. Hotel staff can be granted access only to their hotel’s account and corresponding knowledge base, eliminating the risk of cross-hotel data exposure.
Direct data ingestion into each knowledge base enables near real-time updates for critical data such as room availability. For information that does not change frequently, scheduled synchronization reduces ingestion cost while maintaining accuracy. This hybrid ingestion model balances freshness and operational efficiency.
Because Amazon Bedrock Knowledge Bases are fully managed, performance remains consistent during peak usage periods without the company managing indexing, scaling, or retrieval infrastructure. Each knowledge base scales independently, preventing noisy-neighbor issues that could arise in a centralized design.
Option A and B rely on a centralized knowledge base, which increases policy complexity and introduces risk of misconfigured access controls.
Option D adds unnecessary orchestration complexity and does not inherently solve real-time data freshness requirements.
Therefore, Option C provides the most secure, scalable, and operationally efficient solution for enhancing the PMS with Amazon Bedrock Knowledge Bases.

Explanation:
Option A is the best solution because it natively delivers retrieval grounding, source attribution, and low operational overhead through Amazon Bedrock Knowledge Bases. The key requirements are: retrieve from company data sources, cite sources, link claims to source documents, and keep latency under 3 seconds. Knowledge Bases are a managed RAG capability that handles document ingestion, chunking, embeddings, retrieval, and assembly of context for model generation. This eliminates the need to build and maintain custom retrieval infrastructure.
Source attribution is crucial: the application must “link data claims to source documents.” When source attribution is enabled, the RAG pipeline can return references to the underlying documents and segments used for generation. This enables traceable citations that can be surfaced to end users and used for internal auditing.
Using the Anthropic Claude Messages API (or equivalent conversational interface) with RAG allows the application to generate recommendations grounded in retrieved context while keeping responses conversational. Setting relevance thresholds helps reduce noisy retrieval, which supports both accuracy and latency targets by limiting the context passed to the model.
Storing reasoning and citations in Amazon S3 supports audit and retention needs with minimal operational burden. While the prompt may request step-by-step reasoning, AWS best practice is to produce user-facing explanations that are faithful and attributable without exposing internal reasoning traces unnecessarily. With source-grounded outputs, the system can provide concise rationale tied to citations while maintaining fast response times.
Option B emphasizes extended thinking, which increases latency and does not ensure source linkage.
Option C adds significant operational overhead through custom model hosting and separate citation systems.
Option D requires more custom tracking work than A while not improving retrieval attribution beyond what Knowledge Bases already provide.
Therefore, Option A best meets the requirements with the least operational overhead.

Explanation:
Option D best satisfies all functional, performance, and governance requirements while minimizing architectural complexity. The requirement explicitly states that all filtering must complete before content reaches the foundation model, which rules out asynchronous or streaming-based approaches that could delay enforcement.
Amazon Comprehend supports toxicity detection, prompt safety classification, and PII detection with entity redaction as managed capabilities. Running these filters in parallel ensures low end-to-end latency, which is essential for customer-facing communication platforms. Parallel execution avoids the cumulative latency that would be introduced by sequential pipelines.
Toxicity detection identifies offensive or abusive content early. Prompt safety classification detects requests for unethical, harmful, or manipulative advice, which directly addresses inappropriate advice solicitation requirements. PII detection with entity redaction ensures that customer privacy is preserved before data is sent to the FM, preventing sensitive information from being processed or echoed in generated responses.
Configuring thresholds allows fine-grained control over sensitivity while maintaining acceptable false-positive rates. Using CloudWatch metrics and alarms enables continuous monitoring of filtering behavior and intervention rates without adding custom routing or human review pipelines that would slow responses.
Option A lacks PII redaction.
Option B introduces unnecessary model-building complexity and delayed PII checks.
Option C adds sequential latency and introduces human review routing, which violates the response-time requirement.
Therefore, Option D provides the most robust, performant, and AWS-aligned layered content filtering solution.

Explanation:
Option B is the correct solution because AWS AppConfig is specifically designed to support dynamic configuration management with safe rollout, validation, and rollback, which are explicit requirements in the scenario.
By storing the active model provider configuration in AWS AppConfig, the company can switch between Amazon Bedrock model providers in real time without redeploying Lambda code. AppConfig supports deployment strategies such as canary releases, linear rollouts, and immediate deployments, allowing safe and controlled changes. If a configuration causes issues, AppConfig supports automatic rollback, reducing operational risk.
AWS AppConfig also supports schema validation, ensuring that configuration values such as model identifiers, provider names, or inference parameters are valid before being applied. This prevents misconfiguration from impacting production workloads.
Option A uses Parameter Store, which lacks native rollout strategies, validation, and automated rollback, making it unsuitable for safe real-time switching.
Option C requires manual routing changes and code coupling, increasing operational overhead and deployment risk.
Option D introduces unnecessary complexity by hosting configuration files in Amazon S3 when AppConfig already supports native hosted configurations.
Therefore, Option B provides the most robust, scalable, and low-maintenance solution for dynamic model switching in a serverless Amazon Bedrock inference architecture.