Cloud-hosted large language model APIs commonly use token-based pricing, where inference charges depend on the quantity of input and output tokens processed. Option C is correct because including extensive conversational history increases the number of input tokens submitted with each request, potentially increasing operational expenditure.
For example, consider an application sending 20,000 input tokens and producing 2,000 output tokens. If the provider charges $2 per million input tokens and $8 per million output tokens, the request costs approximately $0.056 before applicable discounts or additional fees.
As conversation history grows, repeated transmission of earlier messages can create substantial cumulative costs.
Option A is incorrect because temperature is a configurable sampling parameter and does not automatically increase when a longer prompt is submitted.
Option B is incorrect as the primary explanation because longer contexts can increase computational and memory requirements, but the observed billing increase is directly explained by the growth in processed tokens.
Option D is incorrect because expanding supplied context does not automatically select a different model.
Cost-management strategies include conversation summarization, selective history retention, prompt caching where supported, and retrieval of relevant past exchanges.
Specific Cisco AITECH Course Guide References: Generative AI Ecosystem; AI Architect's Toolkit; Objective 1.3 — Context windows and token limits; Objective 5.4 — Token usage and prototyping economics.
===================
Submit