Objective 1.2

PCSE

Managing service accounts

Objective 1.2 sits in Configuring access, which carries 25% of the Cloud Security Engineer exam. The questions below are original, written from the official objective title above, and each explanation cites the Google Cloud page it rests on.

Objective title verbatim from the official objectives. Google Cloud exam page

A worked example

Shown solved, with the whole explanation open: this is what every question here carries.

1-2Configuring access

A security analyst asks why a leaked service account key is treated as more serious than a leaked user password. What makes the key more likely to work?

Service accounts face no additional sign-in verificationsCorrect · your answerCorrect. Nothing stands between the key and an access token.
Keys are valid across every project in the organizationReach follows the grants on the account, not the credential format.
Key material is transmitted without transport encryptionTransport protection is not where the difference between these two credentials lies.
Keys carry broader roles than any user account holdsA key carries only what its service account was granted, nothing wider.

Correct.

Concept

A stolen credential is only as dangerous as the checks standing behind it. A second factor can intercept a human sign-in, while a machine credential is presented and accepted on its own.

Why A

A leaked password often fails against 2-step verification and login challenges, while authenticating with a leaked service account key is likely to succeed, as service accounts are not subject to any additional sign-in verifications.

Source

Attempting to sign in by using a leaked password is unlikely to succeed if the user account has been configured to use 2-step verification and login challenges . In contrast, authenticating by using a leaked service account key is likely to succeed as service accounts are not subject to any additional sign-in verifications.

Google Cloud: Best practices for managing service account keys, checked August 2026
#gcp#service-accounts#keys#credential-leakage

Now you: objective 1.2 questions

No account needed. The explanation opens when you answer.

Sample question 1 of 3

1-2Configuring access

An organization wants service account keys disallowed everywhere, with a handful of legacy projects excepted. How should the constraints be applied?

Sample question 2 of 3

1-2Configuring access

A developer needs a key on a build host but cannot create one, and the administrator who can create it has no access to that host. What should they exchange?

Sample question 3 of 3

1-2Configuring access

Service accounts have no passwords. What do they use instead to authenticate?

Full Cloud Security Engineer question bank coming

We’re writing the complete bank from the official objectives right now. Leave your email and we’ll tell you when it ships, nothing else, ever.

Read the sources

These are the official pages the questions above cite. Reading them is studying the objective from the primary source, which is what the explanations point you toward anyway.

More objectives in Configuring access