nerdexam
Google

PROFESSIONAL-CLOUD-DEVOPS-ENGINEER · Question #66

A third-party application needs to have a service account key to work properly. When you try to export the key from your cloud project, you receive an error: "The organization policy constraint…

The correct answer is D. Add a rule to set the iam.disableServiceAccountKeyCreation policy to off in your project, and. To allow service account key creation for a specific third-party application while adhering to security best practices, override the iam.disableServiceAccountKeyCreation policy at the project level.

Submitted by joshua94· Apr 18, 2026Applying site reliability engineering principles to a service

Question

A third-party application needs to have a service account key to work properly. When you try to export the key from your cloud project, you receive an error: "The organization policy constraint iam.disableServiceAccounKeyCreation is enforced." You need to make the third-party application work while following Google-recommended security practices. What should you do?

Options

  • AEnable the default service account key, and download the key.
  • BRemove the iam.disableServiceAccountKeyCreation policy at the organization level, and create a
  • CDisable the service account key creation policy at the project's folder, and download the default
  • DAdd a rule to set the iam.disableServiceAccountKeyCreation policy to off in your project, and

How the community answered

(56 responses)
  • A
    4% (2)
  • B
    9% (5)
  • C
    13% (7)
  • D
    75% (42)

Why each option

To allow service account key creation for a specific third-party application while adhering to security best practices, override the `iam.disableServiceAccountKeyCreation` policy at the project level.

AEnable the default service account key, and download the key.

Enabling the default service account key is generally not a recommended security practice as default service accounts often have overly broad permissions, and the issue is specifically about *creating* a key.

BRemove the iam.disableServiceAccountKeyCreation policy at the organization level, and create a

Removing the policy at the organization level would significantly weaken security across the entire Google Cloud organization, which contradicts Google-recommended security practices.

CDisable the service account key creation policy at the project's folder, and download the default

Disabling the policy at the project's folder level is too broad if only one project requires key creation, potentially compromising security for other projects within that folder.

DAdd a rule to set the iam.disableServiceAccountKeyCreation policy to off in your project, andCorrect

Google-recommended security practices involve applying policies at the most granular level possible. By adding a rule to override the `iam.disableServiceAccountKeyCreation` policy to 'off' specifically at the project level, you enable key creation only where necessary for the third-party application, while maintaining the restrictive policy for the rest of the organization or folder.

Concept tested: IAM organization policies and overrides

Source: https://cloud.google.com/resource-manager/docs/organization-policy/overview

Topics

#Service Account Keys#Organization Policies#IAM#Security Best Practices

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Practice