Search viva questions

SimpleCamera pe clearly IITM/college ID dikhao — naam photo match.

Pehle se ID haath mein rakho. Glare mat aane do. Examiner screenshot/verify karta hai. Iske baad GitHub + project run.

SimpleDemo script pehle se practice karo, 5-7 minute, saari roles.

Suggested flow

1) Register/login user 2) Admin login — CRUD 3) Approval/blacklist 4) Booking/apply 5) Search 6) Validation edge (slots 0, duplicate) 7) Logout
Bolte-bolte dikhao: 'Yahan overbooking rokta hoon'. Code tab kholna jab poochhein.
Crash ho to debug calmly: terminal error, typo, DB path.
Mandatory features skip mat karna — examiner list tick karta hai.

SimpleRoutes/controllers URLs handle karte hain. app.py app banata hai, models.py data, templates/ views, static/ CSS-JS.

Typical structure:
app.py / __init__.py → Flask app, db.init, register blueprints
models.py → tables
routes.py / views → @app.route functions
templates/ → Jinja HTML
static/ → css, images
instance/*.db → SQLite

Ek route explain karne ka template:
1) URL + methods 2) Auth/role check 3) Form/query se data 4) Business rule (duplicate, slots) 5) db.session 6) render ya redirect

Example GET+POST same route: GET form, POST save.
Data HTML se: form name= → request.form. Data HTML ko: render_template(..., items=query).
Nayi .py file: import karke use karo, warna Flask ko pata nahi. Folder rename: imports/paths/templates check.

SimpleCRUD = Create, Read, Update, Delete — kisi bhi resource ke 4 basic operations.

Create: POST, db.session.add(new_user); commit() — register, add trek.
Read: GET, User.query.all() — dashboard list.
Update: POST/PUT, user.name = 'Ram'; commit() — edit profile.

DeletePOST/DELETE, db.session.delete(obj); commit().

REST mapping: POST create, GET read, PUT/PATCH update, DELETE delete.
Admin panel mein yeh 4 dikhana viva demo ka common task hai.

SimpleStatus code number batata hai request ka result.

200 OK — success, page/data mil gaya.
201 Created — POST se naya resource.
302/303 Found/See Other — redirect (login ke baad).
304 Not Modified — cache use karo.
400 Bad Request — galat input.
401 Unauthorized — login nahi (ironically authentication missing).
403 Forbidden — login hai, permission nahi.
404 Not Found — route/record nahi.
500 Internal Server Error — server crash (DB error, NoneType). debug=True pe traceback.
501 Not Implemented — method server nahi sambhalta.

abort(404) Flask mein. get_or_404(id) record na ho to 404.
User ID GET pe exist na kare to 404 return karo, 500 nahi.

Yeh MAD-1 viva question tumhare project ke context se linked hai. Short answer is structure se do:

Pehle 1 line definition/purpose, phir tumhare project ka example, phir chhota code/flow.

Typical Flask flowBrowser request → @app.route controller → SQLAlchemy model/DB → Jinja template response.

Auth: session['user_id'] + role check. CRUD: add/commit, query.all, field update, delete.
Live change maange to: related model → route → template, phir browser refresh karke dikhao.

Example (generic create):
obj = Model(name=request.form.get('name'))

db.session.add(obj); db.session.commit()
return redirect(url_for('list_view'))

SimpleCamera pe clearly IITM/college ID dikhao — naam photo match.

Pehle se ID haath mein rakho. Glare mat aane do. Examiner screenshot/verify karta hai. Iske baad GitHub + project run.

SimpleGitHub repo public/private policy ke hisaab, MAD-1 collaborator add, commits dikhao.

Repo → Settings → Collaborators → instructor added.
Commits: git log / GitHub History — regular commits better, ek dum 1 commit suspicious.
README + report mein AI usage likha hona chahiye agar use kiya.

SimpleBlacklist flag user/company ko block karta hai — login ya features band.

user.is_blacklisted = True; db.session.commit()
Login: if user.is_blacklisted: flash('Blocked'); return
Student dashboard: blacklisted company ke drives hide — query filter join Company.is_blacklisted==False.
Demo: admin blacklist → us user se login fail.

SimpleRoutes/controllers URLs handle karte hain. app.py app banata hai, models.py data, templates/ views, static/ CSS-JS.

Typical structure:
app.py / __init__.py → Flask app, db.init, register blueprints
models.py → tables
routes.py / views → @app.route functions
templates/ → Jinja HTML
static/ → css, images
instance/*.db → SQLite

Ek route explain karne ka template:
1) URL + methods 2) Auth/role check 3) Form/query se data 4) Business rule (duplicate, slots) 5) db.session 6) render ya redirect

Example GET+POST same route: GET form, POST save.
Data HTML se: form name= → request.form. Data HTML ko: render_template(..., items=query).
Nayi .py file: import karke use karo, warna Flask ko pata nahi. Folder rename: imports/paths/templates check.

SimpleBlacklist flag user/company ko block karta hai — login ya features band.

user.is_blacklisted = True; db.session.commit()
Login: if user.is_blacklisted: flash('Blocked'); return
Student dashboard: blacklisted company ke drives hide — query filter join Company.is_blacklisted==False.
Demo: admin blacklist → us user se login fail.

SimpleDemo script pehle se practice karo, 5-7 minute, saari roles.

Suggested flow

1) Register/login user 2) Admin login — CRUD 3) Approval/blacklist 4) Booking/apply 5) Search 6) Validation edge (slots 0, duplicate) 7) Logout
Bolte-bolte dikhao: 'Yahan overbooking rokta hoon'. Code tab kholna jab poochhein.
Crash ho to debug calmly: terminal error, typo, DB path.
Mandatory features skip mat karna — examiner list tick karta hai.

SimpleRoutes/controllers URLs handle karte hain. app.py app banata hai, models.py data, templates/ views, static/ CSS-JS.

Typical structure:
app.py / __init__.py → Flask app, db.init, register blueprints
models.py → tables
routes.py / views → @app.route functions
templates/ → Jinja HTML
static/ → css, images
instance/*.db → SQLite

Ek route explain karne ka template:
1) URL + methods 2) Auth/role check 3) Form/query se data 4) Business rule (duplicate, slots) 5) db.session 6) render ya redirect

Example GET+POST same route: GET form, POST save.
Data HTML se: form name= → request.form. Data HTML ko: render_template(..., items=query).
Nayi .py file: import karke use karo, warna Flask ko pata nahi. Folder rename: imports/paths/templates check.

Examiner code pe ungli rakh ke poochta hai — panic mat karo, 4-line formula bolo.

1) Yeh file/line kya role hai (model / route / template / config)?
2) Input kahan se aata hai (form, URL <id>, session, JSON)?
3) DB pe kya query/write?
4) Output kya (render_template / redirect / jsonify)?

Example

@app.route('/book/<int:id>', methods=['POST']) — logged-in user session se, trek id URL se, Booking add, slots--, redirect history.

Unknown line: imports (request, url_for, flash), decorators, if checks, commit — har keyword ka reason ready rakho.

Simplerender_template HTML page bana ke turant dikhata hai, redirect user ko doosre URL pe bhej deta hai.

render_template('home.html', user=user) → server template fill karke 200 response deta hai. URL same rehta hai.
redirect(url_for('dashboard')) → 302 response, browser naya GET karta hai. URL change ho jaata hai.

Examplelogin POST successful hone ke baad render_template mat use karo, warna refresh pe form dubara submit ho jaayega.

Sahi tarika: redirect(url_for('dashboard')) — yeh Post-Redirect-Get pattern hai.

render_template tab: page dikhana hai with data.
redirect tab: kaam ho gaya, ab doosre page pe le jaana hai (login, delete, update ke baad).

Simple{{ }} value print, {% %} logic (if/for), {# #} comment.

{{ user.name }} → HTML mein naam dikhega
{% if user.role == 'admin' %} ... {% endif %} → condition
{% for t in treks %} {{ t.name }} {% endfor %} → loop
{# yeh comment browser mein nahi jaata #}

Object access: {{ reservation.spot.lot.name }} — relationship follow karke nested data.
List pass kiya to loop, single object to .field.

SimpleJinja2 Flask ka template engine hai. HTML ke andar Python-jaisa data print/loop/if kar sakte ho.

Bina Jinja har user ke liye alag HTML file. Jinja se ek template + data.

{{ user.name }} print, {% for x in items %} loop, {% if %} condition, {% extends %} layout.

Example routereturn render_template('dash.html', treks=treks)

dash.html: {% for t in treks %}<li>{{ t.name }}</li>{% endfor %}

HTML files templates/ folder mein isliye kyunki Flask default wahan dhundhta hai. render_template Jinja ko run karta hai.
Boolean Jinja handle karta hai: {% if user.is_admin %}.

SimpleJinja2 Flask ka template engine hai. HTML ke andar Python-jaisa data print/loop/if kar sakte ho.

Bina Jinja har user ke liye alag HTML file. Jinja se ek template + data.

{{ user.name }} print, {% for x in items %} loop, {% if %} condition, {% extends %} layout.

Example routereturn render_template('dash.html', treks=treks)

dash.html: {% for t in treks %}<li>{{ t.name }}</li>{% endfor %}

HTML files templates/ folder mein isliye kyunki Flask default wahan dhundhta hai. render_template Jinja ko run karta hai.
Boolean Jinja handle karta hai: {% if user.is_admin %}.

Simplerender_template HTML file ko Jinja se process karke browser ko bhejta hai. Backend data ko frontend se jodta hai.

return render_template('dashboard.html', user=user, treks=treks)

File templates/dashboard.html honi chahiye.
Keyword arguments template mein variables ban jaate hain: {{ user.name }}.
Route kuch return na kare to Flask error. Boolean return typical HTML view ke liye nahi — string/Response chahiye.

SimpleMVC = Model-View-Controller. Code ko 3 hisson mein baant ta hai taaki mix na ho.

Model: data + DB. models.py — User, Trek, Booking classes.
View: jo user dekhta hai. templates/*.html + Jinja.
Controller: beech ka logic. routes / app.py — request lo, model se data, view ko do.

Example flow (register):
Browser form POST → Controller register() → User model save → redirect → View dashboard.html

Draw: Browser → Controller → Model → DB, phir Controller → View → Browser.
ORM na ho to bhi MVC ho sakta hai — Model raw SQL functions ho sakte hain. Structure matter karta hai, library nahi.
MVP/MVVM doosri architectures hain; MAD1 mein MVC expected hai.

SimplePUT poori resource replace karta hai, PATCH sirf kuch fields update karta hai.

PUTfull update. Jo fields nahi bheji, woh empty/default ho sakti hain. Idempotent — same request 5 baar bhejo, result same.

PATCHpartial update. Sirf name change karna hai to sirf name bhejo, baaki fields same rehti hain.

ExampleUser {name: Ram, city: Delhi, age: 20}

PUT /user/1 {name: Shyam} → city/age lose ho sakte hain agar poora object nahi bheja.
PATCH /user/1 {name: Shyam} → sirf name Shyam, city Delhi, age 20 same.

MAD1 Flask forms mein aksar POST se update karte hain kyunki HTML form PUT/PATCH native support nahi karta. Theory mein farq yeh hai.

SimpleSach bolo. AI se boilerplate/docs theek, logic samajh ke explain karo.

'Boilerplate aur CSS ke liye AI use kiya, models/routes khud design kiye. Report mein X% mention hai.'
Line-by-line nahi explain kar paoge to examiner pakad lega. Documentation: official Flask/SQLAlchemy + course lectures.

Simple20-30 second intro, phir ID nikaal ke rakhna.

Example'Namaste, main <Name> hoon, IITM BS degree, MAD-1 project <ProjectName> — Flask, SQLAlchemy, Jinja. Roles: Admin, Staff, User. CRUD, auth, search implement kiye.'

Interest poochhe to ek genuine cheez (ML, web, cricket) + 1 line. Fake buzzwords mat maaro.
End mein feedback maangna theek hai: 'Koi improvement suggest karenge?'

SimpleCamera pe clearly IITM/college ID dikhao — naam photo match.

Pehle se ID haath mein rakho. Glare mat aane do. Examiner screenshot/verify karta hai. Iske baad GitHub + project run.

SimpleExaminer submitted ZIP chahta hai, local extra changes nahi.

Portal se ZIP download → extract → venv → pip install -r requirements.txt → flask run / python app.py.
Checksum maange to hash match karke dikhao. Camera/OPPE setup unke instructions.
Linux/Mac: paths, gunicorn; Windows paths alag ho to relative paths use karo.
Do browsers: admin + user parallel demo impressive lagta hai.

SimpleRoutes/controllers URLs handle karte hain. app.py app banata hai, models.py data, templates/ views, static/ CSS-JS.

Typical structure:
app.py / __init__.py → Flask app, db.init, register blueprints
models.py → tables
routes.py / views → @app.route functions
templates/ → Jinja HTML
static/ → css, images
instance/*.db → SQLite

Ek route explain karne ka template:
1) URL + methods 2) Auth/role check 3) Form/query se data 4) Business rule (duplicate, slots) 5) db.session 6) render ya redirect

Example GET+POST same route: GET form, POST save.
Data HTML se: form name= → request.form. Data HTML ko: render_template(..., items=query).
Nayi .py file: import karke use karo, warna Flask ko pata nahi. Folder rename: imports/paths/templates check.

SimpleRoutes/controllers URLs handle karte hain. app.py app banata hai, models.py data, templates/ views, static/ CSS-JS.

Typical structure:
app.py / __init__.py → Flask app, db.init, register blueprints
models.py → tables
routes.py / views → @app.route functions
templates/ → Jinja HTML
static/ → css, images
instance/*.db → SQLite

Ek route explain karne ka template:
1) URL + methods 2) Auth/role check 3) Form/query se data 4) Business rule (duplicate, slots) 5) db.session 6) render ya redirect

Example GET+POST same route: GET form, POST save.
Data HTML se: form name= → request.form. Data HTML ko: render_template(..., items=query).
Nayi .py file: import karke use karo, warna Flask ko pata nahi. Folder rename: imports/paths/templates check.

SimpleRoutes/controllers URLs handle karte hain. app.py app banata hai, models.py data, templates/ views, static/ CSS-JS.

Typical structure:
app.py / __init__.py → Flask app, db.init, register blueprints
models.py → tables
routes.py / views → @app.route functions
templates/ → Jinja HTML
static/ → css, images
instance/*.db → SQLite

Ek route explain karne ka template:
1) URL + methods 2) Auth/role check 3) Form/query se data 4) Business rule (duplicate, slots) 5) db.session 6) render ya redirect

Example GET+POST same route: GET form, POST save.
Data HTML se: form name= → request.form. Data HTML ko: render_template(..., items=query).
Nayi .py file: import karke use karo, warna Flask ko pata nahi. Folder rename: imports/paths/templates check.

SimpleLogin GET form dikhata hai, POST credentials check karke session set karta hai.

@app.route('/login', methods=['GET','POST'])
def login():
    if request.method == 'POST':
        u = User.query.filter_by(email=request.form.get('email')).first()
        if u and check_password_hash(u.password, request.form.get('password')):
            if getattr(u, 'blacklisted', False):
                flash('Blocked'); return redirect(url_for('login'))
            session['user_id'] = u.id
            session['role'] = u.role
            return redirect(url_for('dashboard'))
        flash('Invalid')
    return render_template('login.html')

Logout: session.clear(); redirect login. Incognito alag cookie jar — logged out dikhega.
Single login page: role se redirect alag dashboards.

SimpleCRUD = Create, Read, Update, Delete — kisi bhi resource ke 4 basic operations.

Create: POST, db.session.add(new_user); commit() — register, add trek.
Read: GET, User.query.all() — dashboard list.
Update: POST/PUT, user.name = 'Ram'; commit() — edit profile.

DeletePOST/DELETE, db.session.delete(obj); commit().

REST mapping: POST create, GET read, PUT/PATCH update, DELETE delete.
Admin panel mein yeh 4 dikhana viva demo ka common task hai.

SimpleFlask default port 5000. Change: app.run(port=8000) ya env PORT, ya flask run --port 8000.

if __name__ == '__main__':
    app.run(debug=True, host='0.0.0.0', port=8000)

Do apps ek saath: alag ports. Occupied port: error, doosra number try.

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

Viva mein file khol ke bolo:
1) Kaunsi classes/tables hain (User, Role-specific, Booking...)
2) Har table ka kaam 1 line
3) Relationships: 1-1 / 1-M / M-M, backref, cascade, lazy
4) Constraints: unique email, nullable, default status

Example skeleton

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    email = db.Column(db.String(120), unique=True, nullable=False)
    role = db.Column(db.String(20), default='user')
    bookings = db.relationship('Booking', backref='user', cascade='all, delete-orphan')

ER diagram: rectangles entities, lines relationships, PK/FK mark. Schema = yahi structure.
Tables create: db.create_all() ya migrations. SQLite file SQL viewer se dikha sakte ho.

Examiner code pe ungli rakh ke poochta hai — panic mat karo, 4-line formula bolo.

1) Yeh file/line kya role hai (model / route / template / config)?
2) Input kahan se aata hai (form, URL <id>, session, JSON)?
3) DB pe kya query/write?
4) Output kya (render_template / redirect / jsonify)?

Example

@app.route('/book/<int:id>', methods=['POST']) — logged-in user session se, trek id URL se, Booking add, slots--, redirect history.

Unknown line: imports (request, url_for, flash), decorators, if checks, commit — har keyword ka reason ready rakho.

Simpledono SQLAlchemy relationships ko do taraf se connect karte hain, farq sirf likhne ke style ka hai.

backref: relationship ek side pe likhte ho, doosri side SQLAlchemy khud bana deta hai. Short hai, lekin dono models dekh ke relationship clearly nahi dikhti.

back_populates: dono models pe relationship explicitly likhte ho. Code padhne wale ko turant samajh aa jaata hai ki User.posts aur Post.author linked hain.

Example

class User(db.Model):
    posts = db.relationship('Post', backref='author')

Yahan Post.author automatically mil jaata hai.

Explicit version:

class User(db.Model):
    posts = db.relationship('Post', back_populates='author')
class Post(db.Model):
    author = db.relationship('User', back_populates='posts')

Viva tipexaminer ko bolo — MAD1 project mein back_populates zyada clear hai, isliye preferred.

SimpleCascade parent ke saath child pe automatic action (generally delete).

Company delete → uski drives bhi delete, warna orphan rows / FK error.
SQLAlchemy: db.relationship('Drive', cascade='all, delete-orphan', backref='company')
SQL: ForeignKey(..., ondelete='CASCADE')

Cascade sirf delete nahi: save-update, merge, refresh-expire, expunge, delete-orphan.
Cascade Update: parent PK change to child FK update (rare, PK mat badlo).
Parent delete jab children active hon: constraint error, ya cascade se children gayab, ya pehle children handle karo — design choice examiner poochta hai.
CSS cascading alag topic hai (styles inherit/override).

Definition style question: 1 line simple Hinglish + project example + mini code.

Template'X ka kaam Y hai. Mere project mein Z jagah use hua.'

Example'Session login state rakhta hai. session[user_id]=u.id login pe, logout pe session.clear().'

Agar topic Vue/Celery/Redis ho aur project mein nahi hai to sach bolo, theory example do.

Definition style question: 1 line simple Hinglish + project example + mini code.

Template'X ka kaam Y hai. Mere project mein Z jagah use hua.'

Example'Session login state rakhta hai. session[user_id]=u.id login pe, logout pe session.clear().'

Agar topic Vue/Celery/Redis ho aur project mein nahi hai to sach bolo, theory example do.

SimpleAuthentication poochta hai "tu kaun hai?", Authorization poochta hai "tujhe yeh kaam karne ki permission hai?"

Authentication: login. Username + password check karke prove karte ho ki tum genuine user ho. Success pe session/token milta hai.
Authorization: uske baad role check. Admin hi parking lot delete kar sakta hai, normal user nahi.

Example (Flask):
# Authentication

if user and check_password_hash(user.password, form_password):
    session['user_id'] = user.id

# Authorization
if session.get('role') != 'admin':
    abort(403)  # logged in ho, lekin allowed nahi

Project example: student login = authentication. Student admin dashboard nahi khol sakta = authorization.
Validation alag cheez hai (form sahi bhara hai ya nahi, jaise age 18+).

SimpleFlask session request-across data store karta hai, generally signed cookie mein.

session['user_id'] = user.id
uid = session.get('user_id')
session.clear() # logout

Type: dictionary-like (SecureCookieSession). SECRET_KEY se sign — tamper detect.
Store kahan: default client cookie. Server-side Redis/filesystem bhi laga sakte ho.
Browser storage: cookies, localStorage, sessionStorage. Session cookie tab-close pe jaa sakti hai.
Remember-me: permanent session ya alag token cookie.

Yeh feature demo hai. Account ready rakho, steps bol ke dikhao.

Role ke hisaab login → action (create/approve/book) → DB/UI pe result → edge case (fail when slots=0 / blacklisted).
Do browser windows: admin + user. Search/filter alag se dikhao.
Agar feature nahi hai to sach bolo aur 2 minute mein kaise add karoge (query + template) explain karo.

SimpleValidation galat data rok ti hai — frontend turant, backend must.

Frontend: required, min='18', maxlength='8', pattern='(?=.*[A-Z]).{8,}'
Backend example:

pwd = request.form.get('password','')
if len(pwd) < 8 or not re.search(r'[A-Z]', pwd) or not re.search(r'[0-9]', pwd):
    flash('Weak password')

Haan, regex se password rules ho sakte hain.
Age 18-99, date >= today, slots <= 30 and > 0, confirm password == password, email '@' .
Duplicate username: User.query.filter_by(email=email).first() or unique=True catch IntegrityError.
Past date: if date < date.today(): reject. Negative slots: if slots < 0: reject; book pe available > 0 check.

Simple 4-step: Model → DB → Form → Route → Template. Yeh sabse common live-coding hai.

1) models.py: age = db.Column(db.Integer, nullable=True)
2) DB: SQLite viewer se column, ya DB delete karke create_all, ya ALTER TABLE user ADD COLUMN age INTEGER; production mein Flask-Migrate.
3) register.html: <input type='number' name='age' min='18' required>
4) route: user.age = request.form.get('age', type=int); commit
5) dashboard: {{ user.age }} admin table mein <td>{{ u.age }}</td>

Print terminal: print('AGE', request.form.get('age'))
Phone/city same pattern, String(20). Openings on Drive: integer column + form + create_drive route.

SimpleBootstrap CSS/JS framework — ready classes se responsive UI.

<button class='btn btn-primary'>Save</button>

Red button: btn btn-danger. Navbar, cards, grid (row/col).
CDN: <link href='https://cdn.jsdelivr.net/npm/bootstrap@5...'> — internet na ho to style toot sakti hai. Local copy safer viva ke liye.
CSS vs Bootstrap: Bootstrap faster consistent UI, custom CSS fine-control. Dono saath use ho sakte hain.
aria-current='page' accessibility — current nav item screen readers ko.
CDN fayda: cache, quick setup. Nuksaan: offline, privacy, version lock.

SimpleChecksum file ka hash (jaise SHA256) — file change hui ya nahi verify.

Portal pe submitted ZIP ka checksum diya hota hai. Local file ka hash nikaalo, match hona chahiye.
Linux: sha256sum project.zip
Mismatch = galat file / corrupt download. Examiner integrity check karta hai ki tumhari submitted copy hi run ho rahi hai.

SimpleConstraints rules hain jo galat data rok te hain. Referential integrity FK valid parent ko point kare.

PK, FK, UNIQUE, NOT NULL, CHECK (age >= 18). ORM Column flags yahi map karte hain.
SQL = language tables se baat. Database organized data store.
SQL View: saved query, table jaisi dikhti hai, data copy nahi.
Cluster: kai DB servers together (HA/scale) — MAD1 SQLite single file.
Entity mapping: class User → table user, attributes → columns.

Simple2-3 honest improvements + 1 security + 1 UX.

Example

password hashing/CSRF tighter, Redis cache, tests, pagination, email verify, rate limit login, better mobile CSS.

Challenges: relationships/cascade, concurrent booking, Jinja inheritance.
Rate: 7-8/10 with reason — 10/10 arrogant, 3/10 confidence khatam.
Security extra: HTTPS, hashed passwords, CSRF, SQL injection (ORM), login attempts, file type check.

SimpleConstraints rules hain jo galat data rok te hain. Referential integrity FK valid parent ko point kare.

PK, FK, UNIQUE, NOT NULL, CHECK (age >= 18). ORM Column flags yahi map karte hain.
SQL = language tables se baat. Database organized data store.
SQL View: saved query, table jaisi dikhti hai, data copy nahi.
Cluster: kai DB servers together (HA/scale) — MAD1 SQLite single file.
Entity mapping: class User → table user, attributes → columns.

SimpleVCS history track karta hai, Git ek distributed VCS hai.

VCS: kaun kab kya change kiya, rollback, branches. Example: Git, SVN.
Git distributed: har developer ke paas poori copy (commits) hoti hai. Central GitHub sirf remote hosting hai, lekin Git ka model distributed hai.
SVN centralized: bina server ke history nahi.

Commands: git status (kya dirty hai), git branch / git checkout -b feature (nayi branch), git rm --cached file (track band, file rahe).
Fayda: collaboration, backup, experiment branches, viva GitHub collaborator check.
Git ke bina bhi files rakh sakte ho, lekin history/merge nahi.

SimpleChecksum file ka hash (jaise SHA256) — file change hui ya nahi verify.

Portal pe submitted ZIP ka checksum diya hota hai. Local file ka hash nikaalo, match hona chahiye.
Linux: sha256sum project.zip
Mismatch = galat file / corrupt download. Examiner integrity check karta hai ki tumhari submitted copy hi run ho rahi hai.

SimpleDemo script pehle se practice karo, 5-7 minute, saari roles.

Suggested flow

1) Register/login user 2) Admin login — CRUD 3) Approval/blacklist 4) Booking/apply 5) Search 6) Validation edge (slots 0, duplicate) 7) Logout
Bolte-bolte dikhao: 'Yahan overbooking rokta hoon'. Code tab kholna jab poochhein.
Crash ho to debug calmly: terminal error, typo, DB path.
Mandatory features skip mat karna — examiner list tick karta hai.

SimpleRoutes/controllers URLs handle karte hain. app.py app banata hai, models.py data, templates/ views, static/ CSS-JS.

Typical structure:
app.py / __init__.py → Flask app, db.init, register blueprints
models.py → tables
routes.py / views → @app.route functions
templates/ → Jinja HTML
static/ → css, images
instance/*.db → SQLite

Ek route explain karne ka template:
1) URL + methods 2) Auth/role check 3) Form/query se data 4) Business rule (duplicate, slots) 5) db.session 6) render ya redirect

Example GET+POST same route: GET form, POST save.
Data HTML se: form name= → request.form. Data HTML ko: render_template(..., items=query).
Nayi .py file: import karke use karo, warna Flask ko pata nahi. Folder rename: imports/paths/templates check.

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

Viva mein file khol ke bolo:
1) Kaunsi classes/tables hain (User, Role-specific, Booking...)
2) Har table ka kaam 1 line
3) Relationships: 1-1 / 1-M / M-M, backref, cascade, lazy
4) Constraints: unique email, nullable, default status

Example skeleton

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    email = db.Column(db.String(120), unique=True, nullable=False)
    role = db.Column(db.String(20), default='user')
    bookings = db.relationship('Booking', backref='user', cascade='all, delete-orphan')

ER diagram: rectangles entities, lines relationships, PK/FK mark. Schema = yahi structure.
Tables create: db.create_all() ya migrations. SQLite file SQL viewer se dikha sakte ho.

Simpledono SQLAlchemy relationships ko do taraf se connect karte hain, farq sirf likhne ke style ka hai.

backref: relationship ek side pe likhte ho, doosri side SQLAlchemy khud bana deta hai. Short hai, lekin dono models dekh ke relationship clearly nahi dikhti.

back_populates: dono models pe relationship explicitly likhte ho. Code padhne wale ko turant samajh aa jaata hai ki User.posts aur Post.author linked hain.

Example

class User(db.Model):
    posts = db.relationship('Post', backref='author')

Yahan Post.author automatically mil jaata hai.

Explicit version:

class User(db.Model):
    posts = db.relationship('Post', back_populates='author')
class Post(db.Model):
    author = db.relationship('User', back_populates='posts')

Viva tipexaminer ko bolo — MAD1 project mein back_populates zyada clear hai, isliye preferred.

Simplebackref relationship ki reverse side automatically bana deta hai.

class Post(db.Model):
    user_id = db.Column(db.Integer, db.ForeignKey('user.id'))
    user = db.relationship('User', backref='posts')

Ab post.user milta hai, aur user.posts bhi — Post model pe sirf ek line.
secondary Many-to-Many junction table ke liye: relationship(..., secondary=likes_table, backref='liked_by').
Explicit chahiye to back_populates use karo.

SimpleORM = Object Relational Mapping. Database tables ko Python classes/objects se map karta hai, raw SQL kam likhni padti hai.

Bina ORM: cursor.execute('SELECT * FROM user WHERE id=?', [5])
ORM se: User.query.get(5) ya db.session.get(User, 5)

Example model

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

FaydePython mein soch sakte ho, SQL injection se protection (parameterized), relationships easy, DB switch thoda aasan.

Nuksaancomplex queries slow/abstract, seekhne ki layer extra, kabhi raw SQL phir bhi chahiye.

MAD1: SQLAlchemy (Flask-SQLAlchemy). Tables db.create_all() ya migrations se banti hain.

SimpleBlacklist flag user/company ko block karta hai — login ya features band.

user.is_blacklisted = True; db.session.commit()
Login: if user.is_blacklisted: flash('Blocked'); return
Student dashboard: blacklisted company ke drives hide — query filter join Company.is_blacklisted==False.
Demo: admin blacklist → us user se login fail.

SimpleDuplicate/overbook rokne ke liye DB constraint + route check dono.

Pehle query: Booking.query.filter_by(user_id=uid, trek_id=tid).first()
Agar exists: flash('Already booked'); return
Slots: if trek.available <= 0: reject else trek.available -= 1; commit
Race condition: unique(user_id, trek_id) constraint — do tabs se double click pe bhi ek hi row.
Blacklist: login pe is_blacklisted check.
Active drive limit: if Company ke paas status=open drive hai to naya mat banne do.

SimpleLogin GET form dikhata hai, POST credentials check karke session set karta hai.

@app.route('/login', methods=['GET','POST'])
def login():
    if request.method == 'POST':
        u = User.query.filter_by(email=request.form.get('email')).first()
        if u and check_password_hash(u.password, request.form.get('password')):
            if getattr(u, 'blacklisted', False):
                flash('Blocked'); return redirect(url_for('login'))
            session['user_id'] = u.id
            session['role'] = u.role
            return redirect(url_for('dashboard'))
        flash('Invalid')
    return render_template('login.html')

Logout: session.clear(); redirect login. Incognito alag cookie jar — logged out dikhega.
Single login page: role se redirect alag dashboards.

SimpleLogin GET form dikhata hai, POST credentials check karke session set karta hai.

@app.route('/login', methods=['GET','POST'])
def login():
    if request.method == 'POST':
        u = User.query.filter_by(email=request.form.get('email')).first()
        if u and check_password_hash(u.password, request.form.get('password')):
            if getattr(u, 'blacklisted', False):
                flash('Blocked'); return redirect(url_for('login'))
            session['user_id'] = u.id
            session['role'] = u.role
            return redirect(url_for('dashboard'))
        flash('Invalid')
    return render_template('login.html')

Logout: session.clear(); redirect login. Incognito alag cookie jar — logged out dikhega.
Single login page: role se redirect alag dashboards.

SimpleFrontend user jo dekhta/click karta hai, Backend server logic + database.

Frontend: HTML, CSS, Bootstrap, Jinja templates, thoda JS. Browser pe chalta hai.
Backend: Flask routes, SQLAlchemy, session, validation. Python server pe.
Data flow: form POST → Flask request.form → DB save → render_template/redirect → HTML dikha.
MAD1 typical stack: Flask + Jinja + SQLAlchemy + SQLite + Bootstrap.

SimpleSearch box GET form, backend query filter, results template mein.

q = request.args.get('q', '').strip()
results = Doctor.query.filter(Doctor.name.ilike(f'%{q}%')).all() if q else []
return render_template('search.html', results=results, q=q)

Jinja: {{ results|length }} matches. Empty: 'No results'.
JS-only filter: saara data pehle load, client filter — chhote lists. Bada data: server search.
Search generally GET (shareable URL). Count: len(results) ya db.func.count.

SimpleRoutes/controllers URLs handle karte hain. app.py app banata hai, models.py data, templates/ views, static/ CSS-JS.

Typical structure:
app.py / __init__.py → Flask app, db.init, register blueprints
models.py → tables
routes.py / views → @app.route functions
templates/ → Jinja HTML
static/ → css, images
instance/*.db → SQLite

Ek route explain karne ka template:
1) URL + methods 2) Auth/role check 3) Form/query se data 4) Business rule (duplicate, slots) 5) db.session 6) render ya redirect

Example GET+POST same route: GET form, POST save.
Data HTML se: form name= → request.form. Data HTML ko: render_template(..., items=query).
Nayi .py file: import karke use karo, warna Flask ko pata nahi. Folder rename: imports/paths/templates check.

Simple flow: Browser → Route (controller) → Model/DB → phir template (view) → Browser.

Submit example:
1) HTML form POST /register, name='email'
2) register() request.form.get('email')
3) User(email=...) ; db.session.add; commit
4) redirect dashboard
5) dashboard query + render_template
6) Jinja {{ user.email }} / {% for %}

GET search: /search?q=flask → request.args.get('q') → filter ilike → template list.
JSON API: jsonify, frontend fetch().

SimpleBlacklist flag user/company ko block karta hai — login ya features band.

user.is_blacklisted = True; db.session.commit()
Login: if user.is_blacklisted: flash('Blocked'); return
Student dashboard: blacklisted company ke drives hide — query filter join Company.is_blacklisted==False.
Demo: admin blacklist → us user se login fail.

Simplerender_template HTML page bana ke turant dikhata hai, redirect user ko doosre URL pe bhej deta hai.

render_template('home.html', user=user) → server template fill karke 200 response deta hai. URL same rehta hai.
redirect(url_for('dashboard')) → 302 response, browser naya GET karta hai. URL change ho jaata hai.

Examplelogin POST successful hone ke baad render_template mat use karo, warna refresh pe form dubara submit ho jaayega.

Sahi tarika: redirect(url_for('dashboard')) — yeh Post-Redirect-Get pattern hai.

render_template tab: page dikhana hai with data.
redirect tab: kaam ho gaya, ab doosre page pe le jaana hai (login, delete, update ke baad).

Simpleurl_for sirf URL string banata hai, redirect us URL pe browser ko bhejta hai.

url_for('home') → '/home' (function name se URL nikalta hai)
redirect(url_for('home')) → browser ko /home pe le jaata hai

Example

return redirect(url_for('dashboard'))  # sahi
return redirect('/dashboard')         # hardcode, route change pe toot jaayega

Agar redirect se url_for hata do to khud path string dena padega: redirect('/dashboard').
Agar url_for('home') ko url_for('home_page') kar do aur home_page naam ka function nahi hai to BuildError aayega.

url_for ko function ka naam chahiye, URL path nahi.

SimpleAuthentication poochta hai "tu kaun hai?", Authorization poochta hai "tujhe yeh kaam karne ki permission hai?"

Authentication: login. Username + password check karke prove karte ho ki tum genuine user ho. Success pe session/token milta hai.
Authorization: uske baad role check. Admin hi parking lot delete kar sakta hai, normal user nahi.

Example (Flask):
# Authentication

if user and check_password_hash(user.password, form_password):
    session['user_id'] = user.id

# Authorization
if session.get('role') != 'admin':
    abort(403)  # logged in ho, lekin allowed nahi

Project example: student login = authentication. Student admin dashboard nahi khol sakta = authorization.
Validation alag cheez hai (form sahi bhara hai ya nahi, jaise age 18+).

SimpleCookie browser mein save hoti hai, Session server pe data rakhta hai aur browser ko sirf ID deta hai.

Cookie: key-value browser pe. JS padh sakta hai (agar HttpOnly nahi). Size chhoti (~4KB).
Session: server-side dict. Flask default mein session data signed cookie mein hi store hota hai (client pe, lekin tamper-proof).

Example

session['user_id'] = 12 # login ke baad
# browser ko Set-Cookie milti hai

Tab close: default Flask session cookie browser close pe delete (session cookie). Permanent session alag hota hai.
Incognito: cookies isolated, isliye logged-in nahi dikhega.
SECRET_KEY se session sign hota hai — key nahi to session insecure/kaam nahi karega.

SimpleHTTP stateless hai — har request independent, server previous request yaad nahi rakhta.

Isliye login ke baad bhi har request pe kaun ho yeh prove karna padta hai: cookie/session/JWT.
State = yaad rakhna (user_id, cart). HTTP khud nahi rakhta; Flask session iske upar layer hai.
Fayda: scale aasan, koi bhi server next request handle kar sake (sticky session ke bina, token use karke).

SimpleHTTP methods batate hain request kya karna chahti hai. Common: GET POST PUT PATCH DELETE.

GETread/fetch. Safe, URL se. Page kholna, search.

POSTcreate/submit. Form, login.

PUTpoora replace/update. Idempotent.

PATCHpartial update.

DELETEhataana.

HEAD: sirf headers. OPTIONS: CORS preflight.

Flask: @app.route('/x', methods=['GET','POST'])
Agar methods na likho to default sirf GET.
HTML form native sirf GET/POST. PUT/DELETE JS/fetch ya hidden _method se.
GET se data fetch ho sakta hai, create nahi karna chahiye. POST se theoretically fetch ho sakta hai lekin cache/semantics galat.
DELETE fetch ke liye nahi. GET POST ka kaam officially nahi karta — side effects GET pe mat rakho.

SimpleGET read karta hai, PUT existing resource replace/update karta hai.

GET /users/1 → data lao, side-effect nahi. PUT /users/1 → poora user update, idempotent.
PUT vs FETCH: FETCH HTTP method nahi, JS fetch() function hai jo GET/PUT/POST kuch bhi bhej sakta hai.
Search GET, edit-save PUT/POST. GET se create mat karo.

SimpleGET data mangta hai (read), POST data bhejta hai (create/submit).

GETURL mein dikhta hai, bookmark ho sakta hai, browser back/refresh safe hai, data URL query mein jaata hai. Search, page open, login form dikhana.

POSTbody mein data jaata hai, URL mein password nahi dikhta, refresh pe dubara submit ho sakta hai. Login, register, form save.

Example

# page dikhana

@app.route('/login', methods=['GET', 'POST'])
def login():
    if request.method == 'GET':
        return render_template('login.html')
    # POST: form submit
    email = request.form.get('email')
    ...

GET se theoretically data bhej sakte ho (?q=flask), lekin create/update ke liye nahi use karna — data log/history mein save ho jaata hai, length limit hoti hai.
HTML form default GET hota hai; method='POST' likhna zaroori hai login/register pe.

Simpleextends poora layout inherit karta hai, include chhota piece insert karta hai.

extends: child page base.html ka structure use karti hai, blocks override karti hai. Ek hi parent.
include: navbar.html / footer.html jahan chaho insert. Kai baar use ho sakta hai.

base.html:

{% block content %}{% endblock %}

home.html:
{% extends 'base.html' %}
{% block content %}<h1>Home</h1>{% endblock %}

{% include 'navbar.html' %}  → navbar har page pe

Fayda: header/footer ek jagah, change once — saari pages update. MAD1 mein almost har project use karta hai.

Simplecellpadding cell ke andar gap, cellspacing cells ke beech gap.

cellpadding: text aur cell border ke beech khali jagah (andar).
cellspacing: do cells ke beech khali jagah (bahar).

Old HTML: <table cellpadding='10' cellspacing='5'>
Modern CSS:
td { padding: 10px; } /* padding */
table { border-spacing: 5px; } /* spacing */

border-collapse: collapse spacing hata deta hai, borders mil jaate hain.

SimpleVertical = same machine ko powerful banao. Horizontal = aur machines add karo.

Vertical (scale up): RAM/CPU badhao. Simple, lekin ek limit hai, downtime ho sakta hai, single point of failure.
Horizontal (scale out): 5 servers + load balancer. Sasta long-term, fault tolerant, lekin session/DB sharing sochna padta hai.

Example10k users aaye to Flask app ke 4 copies chalao nginx peeche, DB alag machine pe.

Thousands of requests on one machine: caching (Redis), DB indexes, gunicorn workers, phir horizontal.

Simple 4-step: Model → DB → Form → Route → Template. Yeh sabse common live-coding hai.

1) models.py: age = db.Column(db.Integer, nullable=True)
2) DB: SQLite viewer se column, ya DB delete karke create_all, ya ALTER TABLE user ADD COLUMN age INTEGER; production mein Flask-Migrate.
3) register.html: <input type='number' name='age' min='18' required>
4) route: user.age = request.form.get('age', type=int); commit
5) dashboard: {{ user.age }} admin table mein <td>{{ u.age }}</td>

Print terminal: print('AGE', request.form.get('age'))
Phone/city same pattern, String(20). Openings on Drive: integer column + form + create_drive route.

Yeh project-specific feature add/modify hai. 4 layers touch karo: model, route, template, validation.

1) Data chahiye to models.py mein column/relationship + DB update (ALTER / migrate / create_all).
2) Route: GET pe form/page, POST pe request.form se save, flash + redirect.
3) Template: input name=... Jinja se {{ obj.field }} display.
4) Rule: duplicate, range, role check backend pe.

Example naya field 'city':

user.city = db.Column(db.String(50))
user.city = request.form.get('city')
<input name='city'>  ...  {{ user.city }}

Yeh project-specific feature add/modify hai. 4 layers touch karo: model, route, template, validation.

1) Data chahiye to models.py mein column/relationship + DB update (ALTER / migrate / create_all).
2) Route: GET pe form/page, POST pe request.form se save, flash + redirect.
3) Template: input name=... Jinja se {{ obj.field }} display.
4) Rule: duplicate, range, role check backend pe.

Example naya field 'city':

user.city = db.Column(db.String(50))
user.city = request.form.get('city')
<input name='city'>  ...  {{ user.city }}

Yeh MAD-1 viva question tumhare project ke context se linked hai. Short answer is structure se do:

Pehle 1 line definition/purpose, phir tumhare project ka example, phir chhota code/flow.

Typical Flask flowBrowser request → @app.route controller → SQLAlchemy model/DB → Jinja template response.

Auth: session['user_id'] + role check. CRUD: add/commit, query.all, field update, delete.
Live change maange to: related model → route → template, phir browser refresh karke dikhao.

Example (generic create):
obj = Model(name=request.form.get('name'))

db.session.add(obj); db.session.commit()
return redirect(url_for('list_view'))

SimpleLogin GET form dikhata hai, POST credentials check karke session set karta hai.

@app.route('/login', methods=['GET','POST'])
def login():
    if request.method == 'POST':
        u = User.query.filter_by(email=request.form.get('email')).first()
        if u and check_password_hash(u.password, request.form.get('password')):
            if getattr(u, 'blacklisted', False):
                flash('Blocked'); return redirect(url_for('login'))
            session['user_id'] = u.id
            session['role'] = u.role
            return redirect(url_for('dashboard'))
        flash('Invalid')
    return render_template('login.html')

Logout: session.clear(); redirect login. Incognito alag cookie jar — logged out dikhega.
Single login page: role se redirect alag dashboards.

SimplePOST nayi cheez create karta hai, PUT existing cheez ko replace/update karta hai.

POST /books → naya book add. Har baar naya ID banega. Idempotent nahi — 2 baar POST = 2 records.
PUT /books/5 → id=5 wale book ko poora update. Same PUT dubara bhejo to same result (idempotent).

PUT se create bhi ho sakta hai (agar ID client decide kare), lekin REST convention: create = POST, replace = PUT, partial = PATCH.

Example

@app.route('/user', methods=['POST'])          # register naya user
@app.route('/user/<int:id>', methods=['PUT'])  # poora profile replace

HTML <form> PUT nahi bhejta, isliye Flask apps mein edit pe bhi POST use hota hai. Examiner ko yeh reason clearly bolo.

SimpleHTTP methods batate hain request kya karna chahti hai. Common: GET POST PUT PATCH DELETE.

GETread/fetch. Safe, URL se. Page kholna, search.

POSTcreate/submit. Form, login.

PUTpoora replace/update. Idempotent.

PATCHpartial update.

DELETEhataana.

HEAD: sirf headers. OPTIONS: CORS preflight.

Flask: @app.route('/x', methods=['GET','POST'])
Agar methods na likho to default sirf GET.
HTML form native sirf GET/POST. PUT/DELETE JS/fetch ya hidden _method se.
GET se data fetch ho sakta hai, create nahi karna chahiye. POST se theoretically fetch ho sakta hai lekin cache/semantics galat.
DELETE fetch ke liye nahi. GET POST ka kaam officially nahi karta — side effects GET pe mat rakho.

Simple@app.route URL ko Python function se jodta hai. @ wala cheez decorator hai.

@app.route('/hello/<name>', methods=['GET'])
def hello(name):
    return f'Hello {name}'

Decorator function ko wrap karke extra behaviour deta hai (route register, login_required).
Endpoint generally function name. Path /hello/Ram.
<int:id> type converter — sirf integer. Bina converter string. ID chahiye to int safer.
methods=['POST'] only POST. Default GET.
functools.wraps custom decorator mein original function name/docs preserve karta hai.

Simpleurl_for sirf URL string banata hai, redirect us URL pe browser ko bhejta hai.

url_for('home') → '/home' (function name se URL nikalta hai)
redirect(url_for('home')) → browser ko /home pe le jaata hai

Example

return redirect(url_for('dashboard'))  # sahi
return redirect('/dashboard')         # hardcode, route change pe toot jaayega

Agar redirect se url_for hata do to khud path string dena padega: redirect('/dashboard').
Agar url_for('home') ko url_for('home_page') kar do aur home_page naam ka function nahi hai to BuildError aayega.

url_for ko function ka naam chahiye, URL path nahi.

SimpleUserMixin Flask-Login ko batata hai user object kaise treat karna hai (is_authenticated, get_id).

class User(db.Model, UserMixin):
    id = db.Column(db.Integer, primary_key=True)

current_user proxy logged-in user. Initialize: login_user(user) / user_loader callback.
Flask-WTF: Python classes se forms, CSRF, validators. RegisterForm forms.py mein.
fs_uniquifier Flask-Security mein token/session identity — email change pe sessions invalidate.
enctype='multipart/form-data' file upload pe zaroori. request.files.get('resume').

SimpleAPI = Application Programming Interface — do systems predefined rules se baat karti hain. REST API HTTP + JSON use karti hai.

Controller/route HTML bhi return kar sakta hai. REST API generally JSON return karti hai, frontend alag ho (Vue/Postman).

Example

@app.route('/api/users/<int:id>')
def get_user(id):
    u = User.query.get_or_404(id)
    return jsonify(id=u.id, name=u.name)

MAD1 HTML apps mein 'API' kabhi-kabhi routes ko hi keh dete hain. Agar Vue nahi to bolo: server-rendered Flask, JSON APIs optional.
Boolean return: technically jsonify(True) ho sakta hai, lekin meaningful JSON object better. Flask view None return kare to error.
Test: Postman se GET/POST.
Parsing: request.get_json() body se, request.args query se.

SimpleCascade parent ke saath child pe automatic action (generally delete).

Company delete → uski drives bhi delete, warna orphan rows / FK error.
SQLAlchemy: db.relationship('Drive', cascade='all, delete-orphan', backref='company')
SQL: ForeignKey(..., ondelete='CASCADE')

Cascade sirf delete nahi: save-update, merge, refresh-expire, expunge, delete-orphan.
Cascade Update: parent PK change to child FK update (rare, PK mat badlo).
Parent delete jab children active hon: constraint error, ya cascade se children gayab, ya pehle children handle karo — design choice examiner poochta hai.
CSS cascading alag topic hai (styles inherit/override).

SimpleRelationships tables ko jodti hain taaki related data object se mil jaaye.

One-to-Many: User → kai Posts. posts = relationship('Post', backref='author'). FK post.user_id.
One-to-One: User → Profile. uselist=False + unique FK. Profile.user_id unique.
Many-to-Many: Student ↔ Drive. Junction/secondary table (student_id, drive_id).

Example 1-1:

class Profile(db.Model):
    user_id = db.Column(db.Integer, db.ForeignKey('user.id'), unique=True)
    user = db.relationship('User', back_populates='profile', uselist=False)

1-M ko 1-1: child FK pe unique=True + uselist=False.
Parent-child: parent PK, child FK. Junction table extra columns bhi rakh sakti hai (applied_on).

SimpleOOP = objects + classes. Inheritance child parent ke fields/methods reuse karta hai.

class User(db.Model): ...
class Admin(User): ...  # model inheritance (joiner ya single table)

Models inherit db.Model se taaki query/columns milen.

@staticmethod: self nahi, utility. isinstance(obj, User) type check.

MAD1 models classes hain, routes functions — mix of OOP + procedural.

SimpleJinja2 Flask ka template engine hai. HTML ke andar Python-jaisa data print/loop/if kar sakte ho.

Bina Jinja har user ke liye alag HTML file. Jinja se ek template + data.

{{ user.name }} print, {% for x in items %} loop, {% if %} condition, {% extends %} layout.

Example routereturn render_template('dash.html', treks=treks)

dash.html: {% for t in treks %}<li>{{ t.name }}</li>{% endfor %}

HTML files templates/ folder mein isliye kyunki Flask default wahan dhundhta hai. render_template Jinja ko run karta hai.
Boolean Jinja handle karta hai: {% if user.is_admin %}.

SimpleVertical = same machine ko powerful banao. Horizontal = aur machines add karo.

Vertical (scale up): RAM/CPU badhao. Simple, lekin ek limit hai, downtime ho sakta hai, single point of failure.
Horizontal (scale out): 5 servers + load balancer. Sasta long-term, fault tolerant, lekin session/DB sharing sochna padta hai.

Example10k users aaye to Flask app ke 4 copies chalao nginx peeche, DB alag machine pe.

Thousands of requests on one machine: caching (Redis), DB indexes, gunicorn workers, phir horizontal.

SimpleStatus code number batata hai request ka result.

200 OK — success, page/data mil gaya.
201 Created — POST se naya resource.
302/303 Found/See Other — redirect (login ke baad).
304 Not Modified — cache use karo.
400 Bad Request — galat input.
401 Unauthorized — login nahi (ironically authentication missing).
403 Forbidden — login hai, permission nahi.
404 Not Found — route/record nahi.
500 Internal Server Error — server crash (DB error, NoneType). debug=True pe traceback.
501 Not Implemented — method server nahi sambhalta.

abort(404) Flask mein. get_or_404(id) record na ho to 404.
User ID GET pe exist na kare to 404 return karo, 500 nahi.

SimpleFlask default port 5000. Change: app.run(port=8000) ya env PORT, ya flask run --port 8000.

if __name__ == '__main__':
    app.run(debug=True, host='0.0.0.0', port=8000)

Do apps ek saath: alag ports. Occupied port: error, doosra number try.

SimpleExaminer submitted ZIP chahta hai, local extra changes nahi.

Portal se ZIP download → extract → venv → pip install -r requirements.txt → flask run / python app.py.
Checksum maange to hash match karke dikhao. Camera/OPPE setup unke instructions.
Linux/Mac: paths, gunicorn; Windows paths alag ho to relative paths use karo.
Do browsers: admin + user parallel demo impressive lagta hai.

SimpleDemo script pehle se practice karo, 5-7 minute, saari roles.

Suggested flow

1) Register/login user 2) Admin login — CRUD 3) Approval/blacklist 4) Booking/apply 5) Search 6) Validation edge (slots 0, duplicate) 7) Logout
Bolte-bolte dikhao: 'Yahan overbooking rokta hoon'. Code tab kholna jab poochhein.
Crash ho to debug calmly: terminal error, typo, DB path.
Mandatory features skip mat karna — examiner list tick karta hai.

SimpleORM = Object Relational Mapping. Database tables ko Python classes/objects se map karta hai, raw SQL kam likhni padti hai.

Bina ORM: cursor.execute('SELECT * FROM user WHERE id=?', [5])
ORM se: User.query.get(5) ya db.session.get(User, 5)

Example model

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

FaydePython mein soch sakte ho, SQL injection se protection (parameterized), relationships easy, DB switch thoda aasan.

Nuksaancomplex queries slow/abstract, seekhne ki layer extra, kabhi raw SQL phir bhi chahiye.

MAD1: SQLAlchemy (Flask-SQLAlchemy). Tables db.create_all() ya migrations se banti hain.

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

Viva mein file khol ke bolo:
1) Kaunsi classes/tables hain (User, Role-specific, Booking...)
2) Har table ka kaam 1 line
3) Relationships: 1-1 / 1-M / M-M, backref, cascade, lazy
4) Constraints: unique email, nullable, default status

Example skeleton

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    email = db.Column(db.String(120), unique=True, nullable=False)
    role = db.Column(db.String(20), default='user')
    bookings = db.relationship('Booking', backref='user', cascade='all, delete-orphan')

ER diagram: rectangles entities, lines relationships, PK/FK mark. Schema = yahi structure.
Tables create: db.create_all() ya migrations. SQLite file SQL viewer se dikha sakte ho.

SimpleRBAC = Role-Based Access Control — permission role se (admin/staff/user), har user pe alag nahi.

user.role = 'admin'
if current_user.role != 'admin': abort(403)

Same login page, role ke hisaab dashboard. Multiple roles: roles table Many-to-Many, ya comma field (behtar normalized table).
Unapproved staff: is_approved flag, login pe check.
Flask-Security/UserMixin is_authenticated, is_active, get_id dete hain.

Difference question hai — 3 cheezein bolo: meaning, kab use, 1 example.

Pehle concept A ek line, phir B ek line, phir table-jaisa farq (input/output/side-effect).
Example hamesha MAD1 se: GET search page, POST register, PUT/PATCH API update, session vs cookie login.

Yeh feature demo hai. Account ready rakho, steps bol ke dikhao.

Role ke hisaab login → action (create/approve/book) → DB/UI pe result → edge case (fail when slots=0 / blacklisted).
Do browser windows: admin + user. Search/filter alag se dikhao.
Agar feature nahi hai to sach bolo aur 2 minute mein kaise add karoge (query + template) explain karo.

SimpleCost generally rate × quantity/time, round up rules ke saath.

hours = max(1, math.ceil(total_minutes / 60)) # 10 min bhi 1 hour
cost = hours * lot.price_per_hour
Logic route/model method mein rakho, template mein sirf {{ booking.cost }}.
Viva: numbers ka example 90 min × ₹50 = ₹100 (ceil 2 hours) walkthrough karo.

SimpleRoutes/controllers URLs handle karte hain. app.py app banata hai, models.py data, templates/ views, static/ CSS-JS.

Typical structure:
app.py / __init__.py → Flask app, db.init, register blueprints
models.py → tables
routes.py / views → @app.route functions
templates/ → Jinja HTML
static/ → css, images
instance/*.db → SQLite

Ek route explain karne ka template:
1) URL + methods 2) Auth/role check 3) Form/query se data 4) Business rule (duplicate, slots) 5) db.session 6) render ya redirect

Example GET+POST same route: GET form, POST save.
Data HTML se: form name= → request.form. Data HTML ko: render_template(..., items=query).
Nayi .py file: import karke use karo, warna Flask ko pata nahi. Folder rename: imports/paths/templates check.

Simple2-3 honest improvements + 1 security + 1 UX.

Example

password hashing/CSRF tighter, Redis cache, tests, pagination, email verify, rate limit login, better mobile CSS.

Challenges: relationships/cascade, concurrent booking, Jinja inheritance.
Rate: 7-8/10 with reason — 10/10 arrogant, 3/10 confidence khatam.
Security extra: HTTPS, hashed passwords, CSRF, SQL injection (ORM), login attempts, file type check.

SimpleCost generally rate × quantity/time, round up rules ke saath.

hours = max(1, math.ceil(total_minutes / 60)) # 10 min bhi 1 hour
cost = hours * lot.price_per_hour
Logic route/model method mein rakho, template mein sirf {{ booking.cost }}.
Viva: numbers ka example 90 min × ₹50 = ₹100 (ceil 2 hours) walkthrough karo.

Simpleexaminer UI tweak maangta hai — CSS class ya inline, instantly dikhao.

Button color: <button class='btn btn-success'> ya style='background:#22c55e;color:#fff'
Navbar: navbar-dark bg-success / style='background:yellow' / fixed-bottom se neeche.
Center: .wrap { display:flex; justify-content:center; align-items:center; min-height:100vh; }
text-align:center heading ke liye. Bootstrap: d-flex justify-content-center, mx-auto, text-center.
Hover: .btn:hover { opacity:0.8; transform:scale(1.02); }
Half width: class='col-6' ya width:50%. Row→column: flex-direction:column / col-12 stack.
Login card: card shadow p-4 mx-auto (max-width:400px).
Table header green: th { background:green; color:white; } Bold column: td:nth-child(2){font-weight:bold}
Box shadow: box-shadow: 4px 4px 12px rgba(0,0,0,.3);
Background image: body { background: url('/static/bg.jpg') center/cover; }
Reset button: <button type='reset'>Clear</button>
Move button: ms-auto / position / flex order.
Jinja dashboard heading: <h1>{{ user.name }}'s Dashboard</h1>

SimpleCamera pe clearly IITM/college ID dikhao — naam photo match.

Pehle se ID haath mein rakho. Glare mat aane do. Examiner screenshot/verify karta hai. Iske baad GitHub + project run.

SimpleBlacklist flag user/company ko block karta hai — login ya features band.

user.is_blacklisted = True; db.session.commit()
Login: if user.is_blacklisted: flash('Blocked'); return
Student dashboard: blacklisted company ke drives hide — query filter join Company.is_blacklisted==False.
Demo: admin blacklist → us user se login fail.

SimpleDemo script pehle se practice karo, 5-7 minute, saari roles.

Suggested flow

1) Register/login user 2) Admin login — CRUD 3) Approval/blacklist 4) Booking/apply 5) Search 6) Validation edge (slots 0, duplicate) 7) Logout
Bolte-bolte dikhao: 'Yahan overbooking rokta hoon'. Code tab kholna jab poochhein.
Crash ho to debug calmly: terminal error, typo, DB path.
Mandatory features skip mat karna — examiner list tick karta hai.

SimpleMVC = Model-View-Controller. Code ko 3 hisson mein baant ta hai taaki mix na ho.

Model: data + DB. models.py — User, Trek, Booking classes.
View: jo user dekhta hai. templates/*.html + Jinja.
Controller: beech ka logic. routes / app.py — request lo, model se data, view ko do.

Example flow (register):
Browser form POST → Controller register() → User model save → redirect → View dashboard.html

Draw: Browser → Controller → Model → DB, phir Controller → View → Browser.
ORM na ho to bhi MVC ho sakta hai — Model raw SQL functions ho sakte hain. Structure matter karta hai, library nahi.
MVP/MVVM doosri architectures hain; MAD1 mein MVC expected hai.

SimpleAPI = Application Programming Interface — do systems predefined rules se baat karti hain. REST API HTTP + JSON use karti hai.

Controller/route HTML bhi return kar sakta hai. REST API generally JSON return karti hai, frontend alag ho (Vue/Postman).

Example

@app.route('/api/users/<int:id>')
def get_user(id):
    u = User.query.get_or_404(id)
    return jsonify(id=u.id, name=u.name)

MAD1 HTML apps mein 'API' kabhi-kabhi routes ko hi keh dete hain. Agar Vue nahi to bolo: server-rendered Flask, JSON APIs optional.
Boolean return: technically jsonify(True) ho sakta hai, lekin meaningful JSON object better. Flask view None return kare to error.
Test: Postman se GET/POST.
Parsing: request.get_json() body se, request.args query se.

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

Viva mein file khol ke bolo:
1) Kaunsi classes/tables hain (User, Role-specific, Booking...)
2) Har table ka kaam 1 line
3) Relationships: 1-1 / 1-M / M-M, backref, cascade, lazy
4) Constraints: unique email, nullable, default status

Example skeleton

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    email = db.Column(db.String(120), unique=True, nullable=False)
    role = db.Column(db.String(20), default='user')
    bookings = db.relationship('Booking', backref='user', cascade='all, delete-orphan')

ER diagram: rectangles entities, lines relationships, PK/FK mark. Schema = yahi structure.
Tables create: db.create_all() ya migrations. SQLite file SQL viewer se dikha sakte ho.

Yeh list filter/sort/display task hai. Query badlo, template same rakh sakte ho.

rows = Model.query.filter_by(status='approved').order_by(Model.name.asc()).all()

Jinja: {% for r in rows %}<tr><td>{{ r.name|upper }}</td></tr>{% endfor %}

{{ rows|length }} count dikhane ke liye.

Alphabet sort: order_by(Model.name). Status filter: filter_by(status='pending').
Assigned staff column: relationship se {{ booking.staff.name }}.

SimpleChecksum file ka hash (jaise SHA256) — file change hui ya nahi verify.

Portal pe submitted ZIP ka checksum diya hota hai. Local file ka hash nikaalo, match hona chahiye.
Linux: sha256sum project.zip
Mismatch = galat file / corrupt download. Examiner integrity check karta hai ki tumhari submitted copy hi run ho rahi hai.

SimpleDemo script pehle se practice karo, 5-7 minute, saari roles.

Suggested flow

1) Register/login user 2) Admin login — CRUD 3) Approval/blacklist 4) Booking/apply 5) Search 6) Validation edge (slots 0, duplicate) 7) Logout
Bolte-bolte dikhao: 'Yahan overbooking rokta hoon'. Code tab kholna jab poochhein.
Crash ho to debug calmly: terminal error, typo, DB path.
Mandatory features skip mat karna — examiner list tick karta hai.

Examiner code pe ungli rakh ke poochta hai — panic mat karo, 4-line formula bolo.

1) Yeh file/line kya role hai (model / route / template / config)?
2) Input kahan se aata hai (form, URL <id>, session, JSON)?
3) DB pe kya query/write?
4) Output kya (render_template / redirect / jsonify)?

Example

@app.route('/book/<int:id>', methods=['POST']) — logged-in user session se, trek id URL se, Booking add, slots--, redirect history.

Unknown line: imports (request, url_for, flash), decorators, if checks, commit — har keyword ka reason ready rakho.

SimpleMVC = Model-View-Controller. Code ko 3 hisson mein baant ta hai taaki mix na ho.

Model: data + DB. models.py — User, Trek, Booking classes.
View: jo user dekhta hai. templates/*.html + Jinja.
Controller: beech ka logic. routes / app.py — request lo, model se data, view ko do.

Example flow (register):
Browser form POST → Controller register() → User model save → redirect → View dashboard.html

Draw: Browser → Controller → Model → DB, phir Controller → View → Browser.
ORM na ho to bhi MVC ho sakta hai — Model raw SQL functions ho sakte hain. Structure matter karta hai, library nahi.
MVP/MVVM doosri architectures hain; MAD1 mein MVC expected hai.

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

Viva mein file khol ke bolo:
1) Kaunsi classes/tables hain (User, Role-specific, Booking...)
2) Har table ka kaam 1 line
3) Relationships: 1-1 / 1-M / M-M, backref, cascade, lazy
4) Constraints: unique email, nullable, default status

Example skeleton

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    email = db.Column(db.String(120), unique=True, nullable=False)
    role = db.Column(db.String(20), default='user')
    bookings = db.relationship('Booking', backref='user', cascade='all, delete-orphan')

ER diagram: rectangles entities, lines relationships, PK/FK mark. Schema = yahi structure.
Tables create: db.create_all() ya migrations. SQLite file SQL viewer se dikha sakte ho.