Check: architecture | ComputeSphere Learn

Goal: Confirm you can choose how to split an app, place each part, tell which parts scale by adding spherelets, and respond to a leaked key.

Four questions: three on Module 8 and one from Module 6. Every answer explains itself, right or wrong.

A two-person team is building a new invoicing app. How should they start?A service per feature: customers, invoices, paymentsOne service, organised into clear modulesOne service for the pages and another for the database queries

In the web, API, database, worker architecture, how does a new job reach the worker?The API calls the worker's URLThe API writes it to the database, and the worker picks it up from thereThe browser sends it to the worker

Which part can you scale by simply running more spherelets?An API that keeps sessions and uploads in the database and object storageA service that saves files to a SphereStor volumeA worker that keeps its job queue in memory

From Module 6: you notice a real API key in a commit you pushed yesterday to a public repository. What do you do first?Delete the line and push a new commitRevoke the key and replace it, then clean it out of the historyMake the repository private

Retry as often as you like.