◆ Apache Cassandra

Create new database roles

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All Apache Cassandra tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCreate a new role named 'data_scientist_role' with no initial permissions, to be used for our…+
Create a new role named 'data_scientist_role' with no initial permissions, to be used for our new analytics team by tomorrow morning. Confirm its creation.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I create the 'external_vendor_role' for the new supplier, make it easy to manage. Show…+
Before I create the 'external_vendor_role' for the new supplier, make it easy to manage. Show me how to set up time-limited access for 90 days, and flag any default permissions that might grant too much access by accident.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI created 'temp_dev_role' but it's showing up with more permissions than I explicitly granted,…+
I created 'temp_dev_role' but it's showing up with more permissions than I explicitly granted, specifically on 'staging_data'.
I created 'temp_dev_role' but it's showing up with more permissions than I explicitly granted, specifically on 'staging_data'. I'm afraid there's an implicit grant or a default role inheritance I'm unaware of, and the security audit is next week. What's the most likely diagnosis for this unexpected privilege, and what's the best next move to strip those extra permissions without affecting other roles?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternCreating new roles often results in unintended inherited permissions or insufficient access,…+
Creating new roles often results in unintended inherited permissions or insufficient access.
Creating new roles often results in unintended inherited permissions or insufficient access, leading to rework and security concerns. I suspect I'm not consistently validating the effective permissions after creation. What habit should I change to confidently create roles with precisely the right access from the start, avoiding these frequent adjustments and security risks?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Apache Cassandra's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.