Pass Using AIP-C01 Exam Dumps

Option B is correct because the workload has predictable short peak periods, strict low-latency requirements, and lower demand between spikes. Amazon SageMaker Serverless Inference is designed for intermittent or unpredictable traffic because SageMaker manages the infrastructure and the customer pays based on usage rather than continuously running idle instances. AWS documentation describes serverless inference as suitable when traffic is intermittent or unpredictable and when users do not want to manage instances or scaling policies.

Provisioned concurrency is the key part of this answer. For latency-sensitive serverless inference workloads, provisioned concurrency keeps the required number of serverless instances initialized and ready to respond. AWS documentation states that SageMaker Serverless Inference integrates with Application Auto Scaling so provisioned concurrency can be scaled up or down based on a target metric or schedule. This fits a daily 2-hour peak window because the company can configure enough provisioned concurrency for 500 concurrent requests during peak periods and scale down when demand decreases.

Deploying each model to a separate serverless endpoint is also important. The categorization, extraction, and response-generation models likely have different memory, latency, and concurrency needs. Separate endpoints allow independent memory sizing, maximum concurrency configuration, monitoring, and scaling for each task. AWS API documentation also shows that serverless endpoint configuration includes maximum concurrency and provisioned concurrency settings, with provisioned concurrency required to be less than or equal to maximum concurrency.

Option A is less suitable because multi-model endpoints are usually best when many models can share infrastructure, but model loading and shared capacity can add latency risk. Option C assumes Amazon Bedrock provisioned throughput for models, but the company is developing specialized NLP models and needs task-specific deployment controls. Request batching can also add latency. Option D uses asynchronous inference, which is inappropriate for a less-than-500-ms synchronous response requirement. Therefore, option B best satisfies latency, concurrency, accuracy isolation, and resource optimization.

==========

Options A and E are correct because the failure pattern is caused by exceeding the model’s usable context window and by sending too much raw customer data directly to the FM. Amazon Bedrock Knowledge Bases follows the RAG pattern by splitting source content into manageable chunks, converting chunks into embeddings, storing them in a vector index, and using semantic similarity to retrieve relevant content for a user query. This supports option E because the application can index customer purchases, profiles, and review-related information, then retrieve only the most relevant records for the current recommendation request instead of stuffing all raw data into one prompt.

Option A is also correct because chunking and staged synthesis are standard ways to handle inputs that exceed an FM’s context capacity. Processing smaller segments avoids context-length-exceeded errors, and a final synthesis call can combine intermediate findings into a complete recommendation. This is especially useful when the company says it wants the system to consider all customer data, not merely truncate older or less important data. Amazon Bedrock Knowledge Bases also lets teams configure how content is chunked for storage and retrieval, which supports a structured approach rather than an oversized one-shot prompt.

Option B is not sufficient because truncating “less important” data conflicts with the requirement to consider all customer data. Option C violates the implied design direction because the company wants to use Knowledge Bases, and simply choosing a larger context model does not solve long-term growth of customer histories. Option D is technically incorrect: model parameters such as max_tokens control output generation limits, not the model’s maximum context window, and different Claude models have model-specific maximum values. You cannot use additionalModelRequestFields to bypass the FM’s context limit.

==========

Option B is the correct solution because Amazon Bedrock provisioned throughput is only used when the application explicitly invokes the provisioned model ARN, not the base foundation model ID. In the provided code, the application is calling the standard model identifier (anthropic.claude-v2), which routes requests to on-demand capacity instead of the purchased provisioned throughput.

When the CreateProvisionedModelThroughput API is used, Amazon Bedrock returns a provisioned model ARN that represents the reserved capacity. Applications must reference this ARN in the modelId parameter when invoking the model. If the base model ID is used instead, Bedrock treats the request as on-demand traffic, which explains why CloudWatch metrics show unused provisioned capacity alongside throttled on-demand requests.

Option A would increase capacity but would not fix the root cause because the application is not using the provisioned resource at all. Option C adds resiliency but does not ensure usage of provisioned throughput and would still incur throttling. Option D changes the response delivery mechanism but does not affect capacity routing.

Therefore, Option B directly resolves the throttling issue by correctly routing traffic to the reserved capacity and ensures that the company benefits from the provisioned throughput it has purchased.

Option B is correct because the application is currently invoking the base foundation model identifier, which routes traffic to the on-demand capacity pool rather than the company’s purchased provisioned throughput. In Amazon Bedrock, provisioned throughput is attached to a specific provisioned resource created through the provisioned throughput APIs. To consume that reserved capacity, inference requests must target the provisioned resource identifier that represents the purchased throughput, not the generic model identifier used for on-demand inference.

The code snippet uses modelId= " anthropic.claude-v2 " . This value selects the on-demand endpoint for that model. As a result, requests are subject to on-demand quotas and throttling behavior, while the provisioned throughput remains idle. This directly explains the CloudWatch observation: provisioned capacity metrics show unused capacity because no traffic is being directed to the provisioned resource, and the on-demand path is throttling because it is exceeding the applicable on-demand limits during peak volume.

Replacing the modelId value with the provisioned throughput ARN returned by the CreateProvisionedModelThroughput workflow ensures the runtime invocation is routed to the reserved capacity. Once traffic is directed correctly, the purchased model units provide the consistent throughput required for predictable performance during business hours, which is exactly why provisioned throughput is used.

Option A could increase capacity, but it does not fix the core issue that the application is not using the provisioned resource at all. Option C can reduce the impact of throttling temporarily, but it adds latency and does not guarantee consistent throughput; it also still wastes the provisioned capacity. Option D changes the response delivery mechanism, but throttling is a capacity routing and quota issue, not a streaming API issue.