Google IT Automation with Python study plan

Write and run 15 small scripts that use variables, conditionals, loops, and functions to solve IT-flavored problems such as parsing log lines and validating hostnames

Practice string manipulation and formatting well enough to build a report line from raw input without looking up syntax

Use lists, dictionaries, and tuples to model inventory records and iterate over them with both index-based and for-each loops

Debug your own scripts by reading tracebacks and inserting print or logging statements until each error is understood

Define custom functions with default arguments and return values, then refactor three week-1 scripts to use them

Read and write text and CSV files with the open context manager, handling missing files with try/except

Import and use standard library modules (os, sys, datetime, csv) and explain in writing what each import provides

Handle exceptions deliberately by catching specific error types and raising your own ValueError for bad input

Traverse directory trees with os.walk and pathlib to locate files by extension and size

Rename, move, and archive files programmatically while guarding against overwriting existing paths

Inspect file metadata (size, modification time, permissions) and generate a disk-usage summary report

Run external commands with subprocess, capture stdout and stderr, and check return codes

List and filter running processes by name and user, and explain what the PID and parent PID tell you

Send signals to processes safely and describe the difference between a graceful terminate and a hard kill

Collect CPU, memory, and disk metrics and write them to a timestamped log file

Schedule a Python script to run unattended and verify from its output that it actually ran

Initialize a repository, stage selectively, and write commit messages that state what changed and why

Use branching and merging to develop a feature separately, then resolve a deliberately created merge conflict

Inspect history with log, diff, and show to find when a specific line changed

Undo mistakes with restore, reset, and revert, and state in writing which is safe on shared branches

Push a repository to a remote host, clone it elsewhere, and pull changes without losing local work

Open a pull request from a feature branch and respond to review comments with follow-up commits

Write a .gitignore that excludes generated files and secrets, and verify nothing unwanted is tracked

Create and merge a pull request that fixes a bug you found in your own week 3 or 4 code

Write unit tests with unittest for pure functions, covering normal input, boundary values, and expected failures

Replace hard-coded paths and settings with configuration read from a file or environment variables

Add logging at appropriate levels and use it to diagnose a failure you intentionally introduce

Automate a repetitive task end to end, such as rotating backups or generating a weekly report from logs

Troubleshoot a failing script by reproducing the error, isolating the cause, and confirming the fix with a test

Add retry and timeout handling around an unreliable operation such as a network call or file lock

Review your earlier deliverables and refactor the weakest one for readability and error handling

Complete two timed practice sets mixing all four domains and review every missed item