Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

NVIDIA NCP-AAI Exam - Topic 9 Question 1 Discussion

You are building a customer-support chatbot that fetches user account data from an external billing API. During testing, the API sometimes returns timeouts or 500 errors. You want the agent to be resilient-retrying when appropriate but failing gracefully if the service is down.Which strategy best handles intermittent failures in API calls while still ensuring a good user experience?
B) Implement exponential-backoff retries with a circuit breaker, and return a clear message to the user if all retries fail.
A) Retry requests with a consistent short delay after each failure and notify the user as each retry takes place.
C) Return a standard fallback message on failures to maintain conversation flow and reduce the risk of service interruptions for the user.
D) Schedule retries using a fixed delay for all failure types, maintaining predictable timing and user notifications after each attempt.

NVIDIA NCP-AAI Exam - Topic 9 Question 1 Discussion

Actual exam question for NVIDIA's NCP-AAI exam
Question #: 1
Topic #: 9
[All NCP-AAI Questions]

You are building a customer-support chatbot that fetches user account data from an external billing API. During testing, the API sometimes returns timeouts or 500 errors. You want the agent to be resilient-retrying when appropriate but failing gracefully if the service is down.

Which strategy best handles intermittent failures in API calls while still ensuring a good user experience?

Show Suggested Answer Hide Answer
Suggested Answer: B

The selected design maps to Implement exponential-backoff retries with a circuit breaker and return a clear message to the user if all retries..., which is the highest-control path for this scenario rather than a prompt-only or single-service shortcut. For tool-using agents, the durable pattern is schema-bound function invocation with timeouts, typed outputs, retry policy, and traceable execution rather than free-form endpoint guessing. The evaluation target is the full agent workflow: planning quality, tool selection, intermediate state, latency, retries, user feedback, and final task completion. Instrumentation must expose where degradation starts so remediation can focus on prompts, tool schemas, retrieval, model parameters, or infrastructure rather than random retuning. The distractors are weaker because they lean on A: Retry requests with a consistent short delay after each failure and notify...; C: Return a standard fallback message on failures to maintain conversation flow and...; D: Schedule retries using a fixed delay for all failure types maintaining predictable..., which compromises traceability, resilience, scalability, or policy enforcement in production. The answer therefore fits NVIDIA's production-agent pattern: modular workflow design, measurable runtime behavior, GPU-aware serving where applicable, and controlled integration with enterprise systems.


Contribute your Thoughts:

0/2000 characters
Josefa
4 days ago
A seems too chatty with all those notifications.
upvoted 0 times
...
Samira
10 days ago
Totally agree with B! Clear messaging is key.
upvoted 0 times
...
Shonda
15 days ago
I think B is the best option. Exponential backoff is smart!
upvoted 0 times
...
Kandis
20 days ago
I agree with B, it balances retries and user experience perfectly!
upvoted 0 times
...
Lisha
25 days ago
Wait, are we sure the circuit breaker is necessary? Sounds complicated.
upvoted 0 times
...
Levi
1 month ago
C is a safe fallback, but does it really help users?
upvoted 0 times
...
Lynette
1 month ago
A seems too annoying with all those notifications.
upvoted 0 times
...
Samira
1 month ago
I think B is the best choice. Exponential backoff is smart!
upvoted 0 times
...
Francine
2 months ago
I feel like D might be too rigid. Fixed delays could make the situation worse if the API is down for a longer time.
upvoted 0 times
...
Deja
2 months ago
I practiced a similar question where a fallback message was suggested, but I'm not convinced that C would really help in this case.
upvoted 0 times
...
Gerald
2 months ago
I'm not entirely sure, but I think option A could lead to a frustrating experience for users if they get notified too often about retries.
upvoted 0 times
...
Yolande
3 months ago
I remember we discussed the importance of exponential backoff in our last class. It seems like B might be the best choice for handling those intermittent failures.
upvoted 0 times
...

Save Cancel