before the video started I wanted to say a huge thank you for helping us learn many things that we didn't know. Health to you and your loved ones! Don't stop, good luck!
Q40: I think B is correct. For example if you update product_id 27 in the backend and invalidate the cache for that item then on the next read of the data, it'll get the correct value. The next read could be soon or it could be after many more product update writes happen. Answer D is pretty close but you're updating the backend and the cache for every write regardless of how many reads and cache-misses there are between the writes. Potentially B is better assuming the cache invalidation is faster operation than actually updating the cached value. Full disclosure: I have no idea
![Web Development [17] - Build a Reusable Code Editor in React](http://i.ytimg.com/vi/LkEjvHmiu6c/mqdefault.jpg)
![Web Development [17] - Build a Reusable Code Editor in React](/img/tr.png)
![Web Development [1]](http://i.ytimg.com/vi/JqbkfqOOScQ/mqdefault.jpg)
![Web Development [18] - React Reusable Snackbar Component for Notifications](http://i.ytimg.com/vi/btV22rpki7s/mqdefault.jpg)
![Web Development [3] - Development Environment Setup](/img/n.gif)
Thanks I passed my exam today, this did help. Thank you.
Pls post part 2 ..I hv scheduled aws developer associate exam. This dumps helped a lot clear the concept
before the video started I wanted to say a huge thank you for helping us learn many things that we didn't know.
Health to you and your loved ones! Don't stop, good luck!
TQ u sir nice video
It will help to certification preparation
Can u pls share doc file in link sir 🎉🎉
Can we access other videos related to developer exam practice?
Q-40 ,Is the answer correct?..bz invalidate cache gives us latest data..
Q40: I think B is correct. For example if you update product_id 27 in the backend and invalidate the cache for that item then on the next read of the data, it'll get the correct value. The next read could be soon or it could be after many more product update writes happen.
Answer D is pretty close but you're updating the backend and the cache for every write regardless of how many reads and cache-misses there are between the writes. Potentially B is better assuming the cache invalidation is faster operation than actually updating the cached value.
Full disclosure: I have no idea