Viva Prep

SimpleSame slot twice 400. Two users race. Approval workflow. Book appointment verify edges.

Demo fail then success.

Pehle 1-line definition, phir related MAD2 layer (Vue SFC / Flask route / models.py / tasks.py / Redis).

4-line formula: input kahan se aaya, auth/validation kaunsa, DB ya cache ya Celery, kya return.

Related mix mat karo — cache ≠ Celery, authentication ≠ authorization, v-if ≠ v-show, Beat ≠ Worker. Follow-up ke liye ek difference ready rakho.

Project example: book route checks.

Project example: book route checks.

SimpleVue = UI ka smart assistant. Data badlo, screen khud update. MAD1 Jinja har click pe naya HTML.

Progressive frontend framework. Components, reactivity, directives.

MAD2 SPA: ek index.html, Vue Router pages, Flask sirf JSON.

Fayde: easy, SFC, docs. Vs React: templates HTML-like, course sikhata hai. Vs plain JS: baar-baar DOM mat chhedo.

Example

<!-- HelloWorld.vue -->
<template>
  <h1>{{ msg }}</h1>
</template>
<script>
export default { data() { return { msg: 'Hello' } } }
</script>

Project example: Navbar.vue + views (Login, Dashboard). data() / setup() reactive. fetch APIs.

Viva tipFayde: easy, SFC, reactivity. Vs React: chhota learning curve. Vs plain JS: UI state auto-update.

SimpleORM = Object Relational Mapping. Tables → Python classes. Raw SQL kam likhte ho.

Example

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    email = db.Column(db.String(120), unique=True)

User.query.get(5)  # SELECT ... WHERE id=5

SimpleSach % + kahan + kaise verify + kya seekha. Report se contradict mat.

Boilerplate vs business logic. Examiner process poochta. 'Sab ChatGPT' red flag.

Verify: docs, run, edge case. Seekha: CORS, JWT exp, beat vs worker.

Pehle 1-line definition, phir related MAD2 layer (Vue SFC / Flask route / models.py / tasks.py / Redis).

4-line formula: input kahan se aaya, auth/validation kaunsa, DB ya cache ya Celery, kya return.

Related mix mat karo — cache ≠ Celery, authentication ≠ authorization, v-if ≠ v-show, Beat ≠ Worker. Follow-up ke liye ek difference ready rakho.

Project example: Jo number form/PDF mein hai wahi. Example file jo AI se start kiya, khud debug kiya.

Viva tipExaminer 'kya seekha / kaise check kiya' pe marks. 'Sab ChatGPT' red flag. Jo khud debug kiya woh story ready rakho.

SimpleRBAC = Role Based Access Control. Roles (admin/user) se permissions milti hain, har user pe alag list nahi.

Example

if current_user.role != 'admin':
    flash('Not allowed')
    return redirect(url_for('user.home'))

SimpleCache = pehli baar hisaab karke copy rakh lo, doosri baar copy dikha do.

Baar-baar same expensive kaam (DB query, counting bookings) mat karo. Result Redis jaise store mein timeout ke saath rakh do.

Cache hit: key mil gayi, DB skip. Cache miss: DB se lao, SET karo, return karo.

Tradeoff: speed vs stale data. Admin naya venue add kare aur cache 50s ka ho to user purani list dekh sakta hai — isliye write pe invalidation zaroori hai.

Browser cache, Flask-Caching, Redis alag layers hain. MAD2 examiner Redis + @cache.cached code dekhta hai.

Example

@cache.cached(timeout=50, query_string=True)
@app.route('/api/shows')
def shows():
    return jsonify([s.serialize() for s in Show.query.all()])

Project example: Admin dashboard counts / venues list cache. Create/update/delete ke baad cache.delete('venues').

Viva tipprint('DB queried') function ke andar laga ke miss/hit demo karo — hit pe print nahi chalega.

SimpleCascade parent delete pe children pe kya ho: delete-orphan related rows hata deta hai.

Example

db.relationship('Spot', cascade='all, delete-orphan')

Viva tipParking lot delete → uske spots/bookings policy clear bolo.

SimpleViva wrap-up hai. Short thanks + confirm submission ZIP latest hai.

SimpleDemo script pehle se practice: 5–7 min, Admin + User roles, saare mandatory features.

Suggested flow1) Register/login user
2) Admin login — CRUD
3) Approval/blacklist
4) Booking/apply + edge case
5) Search
6) Logout

Viva tipBolte-bolte dikhao. Code tab kholna jab poochhein.

SimpleLive Flask coding: chhota route likho, save, browser/curl se test. Syntax error terminal mein padho.

Example

@app.route('/ping')
def ping():
    return jsonify(ok=True)

@app.route('/even/<int:n>')
def even(n):
    return 'even' if n % 2 == 0 else 'odd'

SimpleMAD1 frontend usually Jinja templates + HTML/CSS/Bootstrap (+ thoda JS). MAD2 pe Vue ho to clearly bolo.

SimpleVue = UI ka smart assistant. Data badlo, screen khud update. MAD1 Jinja har click pe naya HTML.

Progressive frontend framework. Components, reactivity, directives.

MAD2 SPA: ek index.html, Vue Router pages, Flask sirf JSON.

Fayde: easy, SFC, docs. Vs React: templates HTML-like, course sikhata hai. Vs plain JS: baar-baar DOM mat chhedo.

Example

<!-- HelloWorld.vue -->
<template>
  <h1>{{ msg }}</h1>
</template>
<script>
export default { data() { return { msg: 'Hello' } } }
</script>

Project example: Navbar.vue + views (Login, Dashboard). data() / setup() reactive. fetch APIs.

Viva tipFayde: easy, SFC, reactivity. Vs React: chhota learning curve. Vs plain JS: UI state auto-update.

SimpleCelery background tasks (email, CSV, reports) async chalaata hai. Redis broker/queue + cache.

User 'Export' click → Celery task queue → Redis message → worker CSV banaata hai → user baad mein download.
Saath isliye: Celery ko broker chahiye, Redis tez in-memory. MAD2 topic zyada, MAD1 mein optional.
Priority: task queues/routing. Caching: Redis mein key-value, DB hits kam.
Pub/Sub: publisher channel pe message, subscribers sunte hain — Redis yeh bhi karta hai.

SimpleAJAX page reload ke bina server se data laata hai. Aaj kal fetch() + Promises.

fetch('/api/users').then(r => r.json()).then(data => { ... })
Promise: future value (pending/fulfilled/rejected). fetch Promise return karta hai.
SPA (Vue): ek HTML, baaki routes JS se, partial update. MAD1 generally full page render (Jinja) — submit pe poora refresh.
async/await Promise ka clean syntax.

SimpleTheory = concepts: ORM, MVC, auth vs authz, Jinja inheritance, sessions. 1-line def + project example.

SimpleCDN = Vue script tag se, jaise pen drive. CLI/Vite = poori factory (SFC, npm, bundle).

CDN: no build, chhote apps, exam PC pe Node nahi to bhi chal. Weak: no .vue compile, 3rd-party cache, scale/team.

CLI/Vite: Single File Components, env, code-split, production dist/. Scalable.

Examiner 'which + why' — jo use kiya wahi justify, doosra naam rato mat.

Example

<!-- CDN -->
<script src="https://unpkg.com/vue@3/dist/vue.global.js"></script>

# Vite
npm run dev
npm run build

Project example: CDN: index.html unpkg vue. CLI: package.json, npm run serve / vite.

Viva tipCDN scalable large teams ke liye weak (no SFC compile, caching 3rd party). Examiner 'which + why' poochta hai — jo use kiya wahi justify karo.

SimpleLive UI change: relevant CSS/HTML template kholo — color, margin, flex, bootstrap class. Save + hard refresh.

Example

/* button red */
.btn-primary { background: red; }

/* center navbar item */
.navbar { justify-content: center; }

Viva tipDevTools se pehle try, phir file mein permanent change.

Simplemodels.py = har table ki class: columns, PK/FK, relationships. Yeh Model layer hai.

Suggested flow1) Classes list karo
2) Har table ka kaam 1 line
3) Relationships (1-M / M-M)
4) Constraints (unique, nullable)

Example

class Lot(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    name = db.Column(db.String(80), nullable=False)
    spots = db.relationship('Spot', backref='lot', lazy=True)

SimpleCode explain formula: input kya aaya → auth/validation → DB change → response/UI.

Viva tipFunction signature + 3-4 important lines + edge case.

SimpleNayi booking flow: UI form/button → route POST → login_required → validate seats → insert Booking → commit → redirect/flash.

Suggested flowBrowser → Flask route → Auth → Business rules → SQLAlchemy → SQLite → Response template/JSON

SimpleUngli rakhe to 4-line formula — panic ki jagah structure.

1) File ka role: model / Flask route / Vue SFC / celery task / config
2) Input kahan: JSON, params, token, props, $route
3) Kya kaam: query, cache, validation, .delay()
4) Output: jsonify, this.items, email, redirect

Unknown keyword: import, decorator, if, commit — har ka reason. Bluff mat.

Suggested flow1) Kaunsi layer?
2) Input?
3) DB/cache/task?
4) Response/UI?

Project example: Booking POST: jwt, seats check, commit, 201, Vue list push.

Viva tipUnknown keyword: import, decorator, if, commit — har ka reason. Panic mat.

SimpleLive coding: notepad/editor mein chhota Flask route / Jinja loop / model field. Calm raho, run karke dikhao.

SimpleViva wrap-up hai. Short thanks + confirm submission ZIP latest hai.

SimpleUngli rakhe to 4-line formula — panic ki jagah structure.

1) File ka role: model / Flask route / Vue SFC / celery task / config
2) Input kahan: JSON, params, token, props, $route
3) Kya kaam: query, cache, validation, .delay()
4) Output: jsonify, this.items, email, redirect

Unknown keyword: import, decorator, if, commit — har ka reason. Bluff mat.

Suggested flow1) Kaunsi layer?
2) Input?
3) DB/cache/task?
4) Response/UI?

Project example: Booking POST: jwt, seats check, commit, 201, Vue list push.

Viva tipUnknown keyword: import, decorator, if, commit — har ka reason. Panic mat.

SimpleCode explain formula: input kya aaya → auth/validation → DB change → response/UI.

Viva tipFunction signature + 3-4 important lines + edge case.

SimpleValidation = input rules: required, email format, length, unique. Frontend UX, backend security — dono.

Example

if not email or '@' not in email:
    flash('Invalid email')
    return redirect(request.url)
if User.query.filter_by(email=email).first():
    flash('Email taken')

SimpleMAD1 mein usually session-based auth: login pe session['user_id'], har request pe verify.

Example

session['user_id'] = user.id
uid = session.get('user_id')
user = User.query.get(uid)

Viva tipSECRET_KEY set karo warna session insecure. logout pe session.clear().

SimpleBeat clock hai, Worker haath hai. Clock kaam nahi karti, haath nahi sochte kab.

Worker: @celery.task execute. Beat: crontab padhke due time pe queue mein daal.
Sirf worker = scheduled nahi. Sirf beat = queue bhar jaaye, koi run nahi.

Dono ke saath redis-server. Logs mein 'Sending due task' Beat, 'Task succeeded' Worker.

Example

celery -A app.celery worker -l info
celery -A app.celery beat -l info

Project example: daily_reminder Beat 18:00. Worker MailHog. Export worker-only (button).

Viva tipSirf worker = scheduled jobs nahi chalenge. Sirf beat = queue bhar jaaye, koi run nahi karega.

SimpleGitHub repo open karo: commits, collaborators, README. Examiner check karta hai tumne khud kaam kiya.

Example

Settings → Collaborators
Commits: regular messages, last-day dump nahi.

Viva tipPrivate repo access pehle de do. Main branch submitted ZIP se match honi chahiye.

Simplejsonify(message='Hello World'). Create API Hello World. Write Hello World API.

Simple.

Pehle 1-line definition, phir related MAD2 layer (Vue SFC / Flask route / models.py / tasks.py / Redis).

4-line formula: input kahan se aaya, auth/validation kaunsa, DB ya cache ya Celery, kya return.

Related mix mat karo — cache ≠ Celery, authentication ≠ authorization, v-if ≠ v-show, Beat ≠ Worker. Follow-up ke liye ek difference ready rakho.

Example

@app.route('/api/hello')
def hello():
    return jsonify(message='Hello World')

Project example: GET /api/hello.

SimpleRBAC = Role Based Access Control. Roles (admin/user) se permissions milti hain, har user pe alag list nahi.

Example

if current_user.role != 'admin':
    flash('Not allowed')
    return redirect(url_for('user.home'))

SimpleCRUD 4 operations live: add list edit delete, list refresh.

REST mapping. Related bookings after delete ready answer.

Examiner 2 cheezein: simple desi line + tumhare project ki exact file.

Pehle ID, GitHub, portal ZIP. Phir run: Redis + Flask + worker + beat + Vue. Feature demo: login, RBAC, cache hit/miss, Celery mail, search.

Line pe ungli: input kahan, kaunsa check, query/cache/task, JSON/UI. Copilot band. Jo nahi kiya honestly bolo + kaise add karte.

Example

POST /api/venues → add
GET /api/venues → list
PUT /api/venues/3 → edit
DELETE /api/venues/3

Project example: Admin venues. Postman + UI dono.

Viva tipUpdate ke baad list refresh hoke naya data dikhe. Delete ke baad related bookings kya hoti hain, ready raho.

SimpleCache = pehli baar hisaab karke copy rakh lo, doosri baar copy dikha do.

Baar-baar same expensive kaam (DB query, counting bookings) mat karo. Result Redis jaise store mein timeout ke saath rakh do.

Cache hit: key mil gayi, DB skip. Cache miss: DB se lao, SET karo, return karo.

Tradeoff: speed vs stale data. Admin naya venue add kare aur cache 50s ka ho to user purani list dekh sakta hai — isliye write pe invalidation zaroori hai.

Browser cache, Flask-Caching, Redis alag layers hain. MAD2 examiner Redis + @cache.cached code dekhta hai.

Example

@cache.cached(timeout=50, query_string=True)
@app.route('/api/shows')
def shows():
    return jsonify([s.serialize() for s in Show.query.all()])

Project example: Admin dashboard counts / venues list cache. Create/update/delete ke baad cache.delete('venues').

Viva tipprint('DB queried') function ke andar laga ke miss/hit demo karo — hit pe print nahi chalega.

SimpleLive UI change: relevant CSS/HTML template kholo — color, margin, flex, bootstrap class. Save + hard refresh.

Example

/* button red */
.btn-primary { background: red; }

/* center navbar item */
.navbar { justify-content: center; }

Viva tipDevTools se pehle try, phir file mein permanent change.

SimpleViva wrap-up hai. Short thanks + confirm submission ZIP latest hai.