Question 5
Domain 4: NVIDIA Platform Implementation and Production OperationsWhat graceful degradation strategy works best?
Correct answer: A
Explanation
Graceful degradation means preserving core functionality when parts fail, so tiering dependencies as "critical, important, optional" lets the system protect essential services first. Using "try-catch blocks with fallbacks," returning "partial results with clear indicators of missing information," and offering retry options all reduce failure impact while keeping the user informed.
Why each option is right or wrong
A. Implement service dependency tiers (critical, important, optional), use try-catch blocks with fallbacks, provide partial results with clear indicators of missing information, and offer retry options for failed services.
The selected approach matches the standard resilience pattern for degraded operation: classify dependencies by business criticality, then isolate nonessential failures so they do not cascade into the core path. In practice, exception handling with fallback logic and partial-response rendering preserves available functionality while clearly flagging missing data, and retry affordances are the appropriate recovery mechanism for transient upstream failures.
B. Retry failed services indefinitely until all succeed.
C. Cache previous results and return cached data when services fail.
D. Fail the entire operation if any service fails to ensure data consistency.