Practical tools for system, network, security, and operations administrators.

CLD-C0167 · Career & Certification

Cloud Career Guide

Map one skill you can show from a lab note, and treat a badge suggestion as a hint, not a certificate.

Updated 25 October 2026 · Pillar guide

This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.

A path is evidence you can repeat

This page does not hire you and it does not certify you. The path finder suggests a study order from answers you type. A suggestion is a hint. A badge is a vendor's exam, not a result this site can grant.

The skill that counts here is a guide you can repeat: a cost note with an owner, an identity that is not an owner key, or a pipeline that stops before apply. A lab note a second person can follow is the evidence. A screenshot with no ticket is not.

Pick one neighbouring guide and finish its proof before you collect another syllabus. Breadth without one finished lab is a list. The cost guide and the identity guide are the two this page points at first because bills and keys cause the loudest mistakes.

An exam date, if you want one, is your decision with the vendor. This page will not tell you that you are ready. Ready, here, means you can explain the lab without the generator open.

One finished note, one next guide

Write the work you already do in a sentence. Use the path finder if you want a hint. Record the hint and whether you agree. Disagreement is allowed. The finder does not know your desk.

Choose the next guide and the proof you will keep: the estimate, the policy sentences, or the plan that was not applied. When that proof exists, you have something to show a teammate. You do not have a certification.

Keep secrets out of the portfolio note. An account id can be a lab name you invented for the write-up. A real key is never the sample. A customer name is never the sample.

Stop after one next guide. A wall of courses is not a plan. The rest of this cloud desk will still be here after that proof is written.

# Career note. This page does not hire and does not certify.
# One finished lab is the evidence.
# A path-finder hint is optional.
# No keys and no customer names in the write-up.
# The next guide is one guide, not a syllabus.

A change you can finish

There is no production change on this page. The change is which guide you will finish next.

Rollback is picking a different next guide. Nothing in an account needs undoing because you did not touch one.

  1. Write the work you do now.
  2. Optional: record a path-finder hint and whether you agree.
  3. Choose one next guide.
  4. Name the proof that guide will leave in a ticket.
  5. Remove secrets from any write-up.
  6. Finish that proof before adding another course.
  7. Do not treat a badge as an outcome of this page.

Mistakes that outlive the command

a cloud career fails in the same few ways. Each one looks finished on the day you type it. The list is here so the ticket can forbid them before the window, not so you can recognise them in an incident review.

Decisions to write down before the window

One decision for a cloud career: The page's limit is written: no hiring, no certification. The current work is one sentence. A hint is optional and can be refused. One next guide is named. The proof is a ticket a teammate can read. No secret is in the write-up. No customer data is in the write-up. No exam is implied by this site. The lab account, when you start, is one you may use. Production is not the practice environment. A second person could follow the note. And one proof is enough before the next syllabus.

The hour you stop

Write the account, the project or subscription, the region, and the clock time before you change anything for a cloud career. If this account is serving people and you do not have a way back, this hour is a plan. A plan you can read tomorrow is a success. A change you cannot undo is not.

Use a lab account, a lab project, or a lab subscription you administer. You do not point a CLI, a pipeline, or a browser tool at an account you do not run. The tools on this site run in the browser. They draft text. They do not log in, and they do not scan.

prompt-for-this is a reminder that a secret is missing. It is not an access key, a token, a password, or a kubeconfig you save. The real secret stays in the password store or the platform's secret store. If a file, a log, a ticket, or a pipeline still contains a live secret, stop and rotate it. Then delete the copy.

One change. A network, a virtual machine, a policy, and a pipeline do not share a window. If two things move and the outcome is wrong, you will not know which one did it. The rollback is the previous file, the previous plan, or the resource you can delete because it was only a lab.

A second person reads the scope aloud: which account, which region, which name. If they cannot find it in the ticket, the ticket is not ready. Silence is not agreement.

Documentation addresses stay in the note. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are not prefixes you type into a production network. example.com is not your zone. A generated file that opens 0.0.0.0/0 is a file you edit before it is applied. A source you can name is the rule you keep.

Do not apply a draft you have not read. A cost estimate, a policy, a manifest, and a Terraform plan are reading material. Apply, a resize of a live machine, and a delete of a bucket are later decisions with their own proof. Read the names. Then decide.

Keep the previous file. A generator draft is not the previous file. The previous file is what you put back if the new one is wrong. You practised the path back, including the serial console or a second admin, before you changed a network or a lockout setting.

If a step fails twice, stop. The failure is the result. Adding a command from a forum beside a half-applied stack produces an account nobody can explain. Rebuild the lab from the copy you kept.

When the checks pass, the next account waits until someone else can repeat the proof from the notes. a cloud career is done for this window when the proof is written, not when a CLI printed a success line.

This page is a planning guide. It is not a vendor manual, not an official standard, not legal advice, and not an audit opinion. If an auditor must see the decision, they see the ticket and the evidence, not this paragraph.

Hand the finished note to the neighbouring guide that owns the next step, and leave this account alone until that guide has its own window.

Career checks before you add another course

Confirm this before you call the change done: The note says this is not a certification. The next guide is one guide. The proof you want is named. No key is in the write-up. No customer name is in the write-up. A hint was not treated as an instruction. Production was not changed. The cost or identity guide is on the path, or you wrote why not. A teammate is the audience, not a badge. The lab, if any, has an owner. You can explain the last proof without a generator. The next course waits until that proof exists. The hostname in the prompt matches the hostname in the ticket for a cloud career. The result line includes the time and the person, not only the command. You can point at the rollback value without searching a chat history. And done is a sentence a second person can repeat: the proof for a cloud career happened, and the next host is not started early. If one of those fails, stop.

Tools for this guide

These tools run in the browser on this site. They do not log into your machines.

Guides in this cluster

These supporting pages belong to this pillar.