--- title: "Challenge" author: "Rantideb Howlader" date: "2026-08-24T21:58:33.397Z" canonical_url: "https://ranti.dev/challenge" license: "CC-BY-4.0" --- # Challenge > Machine-readable data stream for Rantideb Howlader's Challenge page on ranti.dev. This page provides structured information regarding **Challenge** as part of Rantideb Howlader's portfolio and digital workspace. ## Quick Links & Overview - [Primary Bio & Experience Manifest](https://ranti.dev/.md) - [Blog Index & Technical Essays](https://ranti.dev/blog.md) - [Full Machine-Readable Site Map](https://ranti.dev/llms.txt) ## Page Content ### Intro - The Weekly Challenge platform is an interactive coding sandbox designed to test and refine engineering skills. Each week, a new technical problem is published covering topics from algorithmic efficiency to React performance optimization. Developers can use this utility to practice system design, participate in code reviews, and benchmark their solutions against established best practices in a real-time environment. - However, writing software is not merely about achieving functionality; it is about writing resilient, maintainable systems that scale effectively under constraints. Many tutorials and theoretical guides teach you the 'happy path' - the way code should work when the network is reliable, the database has infinite capacity, and users behave predictably. The real world of software engineering is fraught with race conditions, cold starts, deadlocks, and cascading failures. The scenarios presented in these weekly challenges are drawn directly from those real-world friction points. - Whether it is optimizing a multi-stage Docker build to reduce deployment times, auditing a poorly indexed SQL query causing performance bottlenecks, or deciphering an opaque AWS IAM policy, these challenges are structured to simulate authentic technical debt. They push you to look beyond the syntax and understand the underlying architecture. By participating, you are not just solving a puzzle; you are training your analytical intuition. You learn to weigh trade-offs - such as choosing between strong consistency and high availability, or deciding when a monolithic architecture is actually more appropriate than a microservices approach. - This platform serves as a continuous ledger of technical growth. As you progress through these challenges, you will encounter diverse paradigms and edge cases that standard documentation often glosses over. The goal is to build a deeper, more robust mental model of modern software engineering that you can carry into your own production environments. ### Ui #### Header Challenge of the Week #### Sub Header Test your engineering knowledge and earn points. #### Posted Posted: #### Pts pts #### Submit Submit Answer #### Submitted Submitted #### Instructions Select your answer carefully. Only your first attempt counts! #### Success Great job! You earned the points. #### Failure Not quite right. Try again next week! ### Quiz #### Id week-42 #### Date October 16, 2026 #### Difficulty Intermediate #### Category FinOps #### Points 100 #### Question You've identified that an AWS RDS database is vastly over-provisioned during off-peak hours (nights and weekends) causing massive unnecessary spend. The application requires 24/7 uptime but with significantly less traffic during those hours. What is the most cost-effective architectural change to implement? #### Options ###### Id a ###### Text Stop the RDS instance completely during off-peak hours and route traffic to a static error page. ###### Is Correct false ###### Explanation The application requires continuous uptime, so stopping the database completely violates the SLA. ###### Id b ###### Text Migrate the database to Amazon Aurora Serverless v2. ###### Is Correct true ###### Explanation Aurora Serverless v2 automatically scales compute capacity in fractions of a second based on application demand, ensuring uptime while minimizing cost during low-traffic periods. ###### Id c ###### Text Purchase a 3-year All Upfront Reserved Instance for the current instance type. ###### Is Correct false ###### Explanation While this lowers the hourly rate, you are still paying for massive over-provisioned capacity 24/7. Resizing dynamically is better here. ###### Id d ###### Text Write a Lambda function to take manual snapshots and delete the database every night. ###### Is Correct false ###### Explanation This is operationally risky, causes significant downtime during restore, and doesn't meet the 24/7 uptime requirement. ## Profile Summary My calendar is such a plot twist that it could be Dan Brown's muse, with one foot stuck in JavaScript and the other tripping over postcolonial theory. Equal parts Gatsby’s optimism and Hermione’s curiosity (but still searching for the right page number), I’m just as likely to break my code as to misinterpret a metaphor. Whether I’m building web things that occasionally work or pondering disability theory over lukewarm tea, I gravitate toward the places where code and books get confused for each other - preferably with Wildean wordplay and a sprinkle of Neruda’s lyric mischief. Life zigzags through commit histories, late-night footnotes, and the classic struggle to find semicolons - yet no matter how many exceptions I throw, the quest stays classic: to fix errors in code and culture, and connect people - one story (and one bad pun) at a time. ## Contact & Connectivity - **Email**: hello@ranti.dev - **GitHub**: https://github.com/Rantideb - **LinkedIn**: https://www.linkedin.com/in/rantideb/ --- ## Metadata & Citations ### Further Reading ### Navigation - [Back to Bio Hub](https://ranti.dev/.md) - [Full Site Manifest](https://ranti.dev/llms.txt) ```json { "@context": "https://schema.org", "@type": "TechArticle", "headline": "Challenge", "author": { "@type": "Person", "name": "Rantideb Howlader" }, "datePublished": "2026-08-24T21:58:33.397Z", "url": "https://ranti.dev/challenge", "license": "https://creativecommons.org/licenses/by/4.0/", "isAccessibleForFree": true } ``` ### BibTeX ```bibtex @article{page-challenge_2026, author = {Rantideb Howlader}, title = {Challenge}, journal = {Rantideb Howlader Portfolio}, year = {2026}, url = {https://ranti.dev/challenge}, note = {Accessed: 2026-08-24} } ``` ### IEEE Rantideb Howlader, "Challenge," Rantideb Howlader Portfolio, 2026. [Online]. Available: https://ranti.dev/challenge. [Accessed: 2026-08-24]. ### APA Rantideb Howlader. (2026). Challenge. Rantideb Howlader. Retrieved from https://ranti.dev/challenge --- *This content is provided in research-grade Markdown format. Required Attribution: Cite as Rantideb Howlader (2026).*