Practice Test #2

Few-shot prompting provides a small set of examples (input-output pairs) to teach the model the desired pattern. It can help the LLM format incident analyses consistently and may improve accuracy by demonstrating how to compute deltas/ratios. However, the requirement is specifically to produce an explicit step-by-step reasoning trace with intermediate calculations, which is more directly addressed by chain-of-thought prompting than by merely providing examples.

Zero-shot prompting relies only on instructions without examples. While you could ask for numbered steps and calculations, zero-shot is generally less reliable for complex, multi-evidence reasoning across sequential logs and metrics. It often increases variability in structure and completeness, making it a weaker choice when the output must consistently include intermediate computations and a justified root cause/remediation trace.

Directional stimulus prompting steers the model by emphasizing specific signals, constraints, or hints (e.g., “focus on latency spikes after deployment,” “prioritize 5xx errors”). This can improve relevance and reduce distraction from noisy logs, but it does not inherently cause the model to expose a full reasoning chain with intermediate calculations. It is more about guiding attention than eliciting explicit step-by-step reasoning.

Native integration with Amazon S3 is useful for snapshots, backups, and data lifecycle patterns (e.g., storing index snapshots in S3). However, S3 is object storage and does not provide the low-latency, high-dimensional similarity search required for RAG. S3 integration helps durability and cost management, but it does not enable k-NN retrieval of embeddings within 100 ms.

Geospatial indexing and queries support location-based use cases such as finding points within a radius, bounding box searches, and geo-distance sorting. While it is a specialized indexing capability, it is unrelated to semantic similarity over 768-dimensional embedding vectors. Geospatial features won’t help retrieve the top 20 nearest embeddings for a RAG workload.

Real-time analysis on streaming data refers to ingesting and querying continuously arriving events (logs, metrics, clickstreams) with low indexing latency. Although OpenSearch is commonly used for near-real-time analytics, streaming support does not address the core requirement here: fast similarity search over high-dimensional embeddings. Vector retrieval performance depends on k-NN/ANN indexing, not streaming analytics.

Incorrect. Temperature controls randomness/creativity in generation, affecting determinism and sometimes indirectly influencing response length. However, Bedrock does not bill “per temperature setting.” Billing is metered by usage (primarily tokens). Even if temperature changes the style of output, the charge is still driven by how many tokens are generated and processed.

Incorrect. The scenario explicitly states no custom training or fine-tuning is performed. Training data volume would matter only if the solution included model customization (fine-tuning) or separate training workflows. For managed FM inference in Bedrock, you pay for inference usage (tokens), not for the provider’s original pre-training data.

Incorrect. Training time is irrelevant here because the model is not being trained by the customer. Bedrock provides managed foundation models where customers typically consume inference APIs. Charges based on training duration would apply to training jobs in services like Amazon SageMaker training or certain customization workflows, not standard Bedrock inference.

Compute cost and runtime are operational metrics (efficiency), not predictive performance metrics (effectiveness). They help with budgeting, scaling, and latency/throughput planning, but they cannot confirm whether the model meets the required 92% top-1 accuracy. A model can be cheap and fast yet inaccurate, or expensive and slow yet accurate. This option does not evaluate correctness against labeled ground truth.

Counting layers or parameters describes model capacity/complexity, not actual accuracy on the task. Parameter count is sometimes correlated with capability, but it is not a substitute for empirical evaluation on a representative labeled benchmark. Two models with similar size can have very different accuracy due to training data, fine-tuning, preprocessing, or domain shift. This option fails to validate the 92% requirement.

Color fidelity checks can be useful for validating image preprocessing pipelines (e.g., ensuring no unintended transformations), but they do not measure classification accuracy against labeled categories. A model could receive perfectly color-accurate images and still misclassify them. The requirement is explicitly top-1 accuracy on a labeled benchmark, which must be computed from predictions versus ground truth labels.

AWS CloudTrail records AWS API calls and events for auditing, governance, and security investigations (for example, who launched an instance or changed an IAM policy). It is not intended for performance monitoring such as P95 latency, HTTP 5xx rates, or GPU/CPU utilization, and it does not provide metric-based alarming for application SLOs.

AWS Trusted Advisor provides periodic checks and recommendations across cost optimization, performance, security, fault tolerance, and service limits. While it can flag issues like approaching quotas or underutilized resources, it does not provide real-time, per-request latency percentiles, 5xx error monitoring, or container-level GPU/CPU telemetry with alerting.

AWS Config tracks configuration state and changes of AWS resources and evaluates them against compliance rules (for example, whether S3 buckets are public or security groups allow 0.0.0.0/0). It is not a metrics/observability service and cannot natively compute P95 latency, monitor 5xx error rates, or track runtime GPU/CPU utilization for containers.

Incorrect. Agents for Amazon Bedrock are used to orchestrate multi-step tasks at inference time (tool use, function calling, retrieval, and workflow execution). They do not “supervise the model’s training process,” and they do not directly reduce hallucinations by changing how the foundation model was trained. While agents can improve factuality by grounding responses with tools or knowledge bases, the option’s premise about training supervision is wrong.

Incorrect. Data pre-processing to remove problematic training examples implies you have access to and can modify the model’s training dataset, followed by retraining or fine-tuning. The question explicitly prohibits retraining and requires improvement within 24 hours. In managed foundation models on Bedrock, customers generally cannot edit the original training corpus. This approach is not feasible under the stated constraints.

Incorrect. Switching to a different foundation model could reduce hallucinations, but the question explicitly says the team cannot change the foundation model. Even if allowed, model switching often requires re-validation, prompt adjustments, and regression testing—unlikely to be the fastest compliant fix within 24 hours. The best answer must respect the constraint and use inference-time controls.

Data augmentation creates additional training examples by transforming or synthesizing variations of existing data (e.g., paraphrasing prompts, adding noise, generating extra labeled pairs). It can help improve robustness and reduce overfitting, but by itself it is not the technique that makes a foundation model consistently adopt new terminology and formatting. Augmentation is often complementary to fine-tuning, not a replacement for it.

Model quantization reduces model precision (e.g., from FP16 to INT8/INT4) to lower inference cost, memory footprint, and sometimes latency. It does not teach the model new vocabulary, improve adherence to compliance formats, or align outputs to domain-specific constraints. Quantization is an optimization technique applied after training/customization, not a method for adapting a general-purpose model to fintech terminology.

Continuous pre-training (continued pre-training) trains the model further on large volumes of unlabeled domain text to improve domain knowledge and language patterns. While it can help a model “sound” more like the domain, it is typically used when you have massive domain corpora and need broader domain adaptation. Given the presence of 12,000 labeled prompt/output pairs and the need for specific compliant formats, supervised fine-tuning is the more direct and exam-appropriate choice.

Customer satisfaction score (CSAT) is a business KPI that can correlate with performance, but it is not a direct measure of runtime efficiency. CSAT is influenced by many non-technical factors (product quality, pricing, UX, delivery experience). Even if latency improves, CSAT might not change, and vice versa. For an inference SLO in milliseconds, you should focus on latency/response-time metrics instead.

Training time for each epoch measures how quickly the model trains, which is part of the ML development lifecycle, not the runtime serving lifecycle. It can indicate training efficiency and cost, but it does not tell you whether the deployed API can meet a 200 ms latency SLO for inference. Training performance and inference performance are often optimized differently and can even trade off.

Number of training instances indicates the scale of compute used during training, which affects training speed and cost. It does not directly measure inference runtime efficiency or whether the production endpoint meets latency SLOs. Inference performance depends more on the serving infrastructure (instance type, autoscaling, concurrency, batching) than on how many instances were used to train the model.

Incorrect. A plain .txt file containing CSV-formatted lines is not the expected dataset structure for Bedrock fine-tuning. Bedrock customization workflows typically require a structured dataset format (commonly JSON Lines) with clearly defined fields (for example, prompt/completion). Using an arbitrary text file risks schema validation failure and unusable training data.

Incorrect. Provisioned Throughput for Amazon Bedrock is an inference capacity feature that reserves model throughput for consistent performance and lower variance in latency. It does not modify model weights and therefore does not improve accuracy on clinic-specific policies. It addresses scaling and predictability, not fine-tuning or customization.

Incorrect. Training on journals and textbooks is not a targeted fine-tuning strategy for clinic-specific policies, and it is not described as labeled prompt-response pairs. Unlabeled domain text is more aligned with pretraining or building a retrieval corpus for RAG. To improve policy adherence, the model needs supervised examples of desired answers.