Hands-on guides on AWS, Kubernetes, Docker, Terraform, CI/CD and Salesforce DevOps by Robin Sishodia, AWS DevOps Professional and certified Salesforce Admin.
Get Records is how a Flow reads data. Admin II interviews ask about its filters, sort order and null checks because a badly built one is the most common cause of slow or broken Flows. The 4 Settings
Yesterday I locked down the root account and noted "keep billing alerts up to date". Today is the other half of the front door: making sure a forgotten resource never turns into a surprise bill. AWS B
Decisions send a flow down the right path. Assignments change values along the way. Admin II interviews ask about both because almost every real Flow uses them. The 2 Elements Element What it does
Every AWS account starts with one identity that can do everything: the root user. IAM policies cannot restrict it, so if someone gets in, there is no safety net. Before building anything else, lock it
On Day 2 I wrote a least-privilege policy for one S3 bucket. The next question is who gets to use it. For people, that's a user or group. For servers and apps, it should be a role, so nothing long-liv
Variables, constants, formulas and collections are the building blocks of every Flow. Admin II interviews ask about them to see if you can build, not just click. The 4 Building Blocks Resource Wha
30 days, 30 topics, one cheat sheet to finish. This is the checklist I would run through before any Salesforce admin interview. The 4 Building Blocks Block What it is Key point Security OWD, ro
Store it once, share it safely, keep every version. Files and attachments come up in almost every admin interview. The 4 Building Blocks Block What it is Key point Files Modern and versioned Up
One clean list of values, used everywhere. Picklists, global value sets and dependencies come up in almost every admin interview. The 4 Building Blocks Block What it is Key point Picklist One v