A retail company is building a customer-support application using Amazon Bedrock. Instead of a full agent, they want a synchronous request/response flow where an API Gateway REST endpoint invokes a Lambda function that calls Bedrock. The application prompt includes a large, static 4,000-token product catalog reference section that is identical across all customer requests, followed by a short dynamic user question. The team observes that per-request latency and input-token costs are unnecessarily high because the large static context is re-processed on every InvokeModel call. Which approach most directly reduces both cost and latency for the repeated static portion?