गाइड से जुड़ी प्रश्नोत्तरी · कठिन स्तर
एआई क्लाउड आर्किटेक्चर प्रश्नोत्तरी
कार्यभार पृथक्करण, प्राधिकरण, बैकप्रेशर, निर्भरता सीमा, कतारें, प्रति कार्य लागत और रोलबैक अनुकूलता का परीक्षण करता है।
प्रश्न 1 का 8
Why separate interactive and background AI workloads?
प्रत्येक प्रश्न का पूर्वावलोकन करें8 प्रश्न
जैसे ही आप प्रश्नोत्तरी लेते हैं उत्तर और स्पष्टीकरण दिखाई देते हैं।
- Why separate interactive and background AI workloads?
- वे हमेशा अलग-अलग मॉडल का उपयोग करते हैं
- Background work needs no monitoring
- They can have different response-time and processing requirements
- Interactive work cannot use queues
- What is the purpose of backpressure in an overloaded service?
- Limit incoming work so a struggling dependency does not overwhelm the system
- Increase every retry rate
- Hide the queue from operators
- Make a slow provider respond faster
- Why is network location alone insufficient to establish authorization?
- Anything inside a network is automatically trusted
- Cloud services cannot enforce access control
- Network boundaries replace secret management
- Access roles and credentials still determine which data or actions are permitted
- A provider has a rate limit and model loading is slow. What should architecture plan for?
- Unlimited retries from every worker
- Bounded retries, admission control, capacity behavior, and clear unavailable states
- A larger prompt
- Automatic acceptance of stale outputs
- A service scales web workers, but every worker calls the same limited inference endpoint. What may happen?
- More workers can create a longer queue without increasing model capacity
- Inference capacity necessarily scales with web workers
- The model stops using memory
- User authorization is automatically improved
- What should cost per useful task include?
- Only the provider’s listed input-token price
- Only GPU electricity
- Storage, transfer, failed attempts, and idle resources in addition to API cost
- The server’s initial purchase price
- Why use clear queue status and retry behavior for background jobs?
- They guarantee every job succeeds on the first try
- They make long-running work and recovery observable
- They remove the need for durable state
- They reduce model output length
- What does a rollback test need to consider?
- Only the web page title
- Whether the new deployment has a shorter name
- The model’s training benchmark alone
- Compatible model, preprocessing, and data-migration versions