Build and operate the data processing systems behind analytics and ML on Google Cloud, including BigQuery, Dataflow, and Pub/Sub, and track your readiness for the Professional Data Engineer exam.
Advanced
Prepare and test your skills
Advanced
Prepare and test your skills
Concept
environment variables
Topic in 1 exam domain
- environment variables · Concept
- environment variables · Feature
- Environment variables · Concept
Also called: --env, Deployment-specific environment variables, envVariables, env_variables, https_proxy, http_proxy, OpenTelemetry environment variables, pre-defined environment variables, user-defined environment variables, userEnvVars
Persistent variables set in the Airflow worker container used to provide runtime configuration for DAGs.
Where this appears on the exam
1 subdomain in 1 of 5 domains
Related topics
FoundationsBuilding blocksBuilding blocksBuilding blocksBuilding blocksBuilding blocksBuilding blocksThis topicSecret ManagerServiceservice accountConceptApplication Default CredentialsFeatureIdentity and Access ManagementServiceWorkflowsServicePub/SubServiceManaged Service for Apache AirflowServiceCloud RunServiceCloud FunctionsService
environment variablesConcept
Points to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- environment variables is part of Cloud Functions From the official documentation: “Demonstrates how to use environment variables within a Cloud Function.”
- environment variables is an alternative to Secret Manager From the official documentation: “Don't use environment variables to store and consume secrets, because environment variables are visible to anyone with project Viewer permissions or greater. Instead, use Secret Manager with Cloud Run as described in the [Using secrets](/run/docs/configuring/jobs/secrets) page.”
- environment variables is part of Workflows From the official documentation: “You can define [environment variables](https://wikipedia.org/wiki/Environment_variable) for Workflows at deployment time.”
- Cloud Run depends on Pub/Sub From the official documentation: “Cloud Run function triggered by Pub/Sub to fetch HYPR MFA logs and write to GCS.”
- Application Default Credentials works with Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
- Application Default Credentials secures Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
- Pub/Sub depends on Application Default Credentials From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
- Managed Service for Apache Airflow works with Secret Manager From the official documentation: “You can [configure Secret Manager](/composer/docs/composer-3/configure-secret-manager) as your Airflow secrets backend.”
- Cloud Run depends on service account From the official documentation: “The Cloud Run function needs a service account with permissions to write to GCS bucket and be invoked by Pub/Sub.”
- Pub/Sub works with Secret Manager From the official documentation: “Receive notifications via Pub/Sub when Secret Manager resources change.”
- Application Default Credentials works with Secret Manager From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
- Cloud Functions works with Pub/Sub From the official documentation: “Demonstrates how to interact with Pub/Sub from Cloud Functions.”
- Application Default Credentials configures Cloud Functions From the official documentation: “To authenticate to Cloud Run functions, set up Application Default Credentials.”
- Application Default Credentials secures Cloud Functions From the official documentation: “To authenticate to Cloud Run functions, set up Application Default Credentials.”
- Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- Application Default Credentials works with Workflows From the official documentation: “To authenticate to Workflows, set up Application Default Credentials.”
- Cloud Run works with Identity and Access Management From the official documentation: “For example, a remote backend deployed on Cloud Run can use Identity and Access Management (IAM) to:”
- Cloud Run works with Secret Manager From the official documentation: “The secret is configured to be accessible by Cloud Run and Cloud Build.”
- Cloud Run works with Workflows From the official documentation: “Use Workflows with Cloud Run and Cloud Run functions tutorial”
- Pub/Sub works with Workflows From the official documentation: “Pub/Sub can be integrated into multistep serverless [Workflows](/workflows) declaratively.”
- service account is part of Identity and Access Management From the official documentation: “Service accounts function as both principals and resources within IAM.”
- Application Default Credentials works with Identity and Access Management From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- Application Default Credentials works with service account From the official documentation: “You can authenticate the service account using Application Default Credentials (ADC) or a service account key.”
- Cloud Functions depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run functions, set up Application Default Credentials.”
- Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- Cloud Run works with Pub/Sub From the official documentation: “A Cloud Run app receives the Pub/Sub message.”
- Identity and Access Management secures Secret Manager From the official documentation: “Secret Manager uses Identity and Access Management (IAM) for authorization.”
- Pub/Sub works with service account From the official documentation: “5. Creates a service account to represent the Pub/Sub subscription identity.”
- Secret Manager depends on Application Default Credentials From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
- Secret Manager works with service account From the official documentation: “The service account can access the secret data.”
- Secret Manager works with Workflows From the official documentation: “You can use a Workflows connector to access Secret Manager within a workflow.”
- service account depends on Secret Manager From the official documentation: “Make sure that the service account that AlloyDB Omni uses has the `secretmanager.secretAccessor` permission to read the secret from Secret Manager.”
- Workflows depends on Application Default Credentials From the official documentation: “To authenticate to Workflows, set up Application Default Credentials.”
- Workflows depends on service account From the official documentation: “You need a service account for Workflows (to run the pipeline) and for Managed Service for Apache Spark (to run the connector).”
- Application Default Credentials configures Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- Application Default Credentials secures Secret Manager From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
- Application Default Credentials depends on service account From the official documentation: “If your `BidiProcessOrder` client runs in a secure environment that can be configured with service account credentials (such as Compute Engine, Google Kubernetes Engine, or your on-premise servers), it can use [Application Default Credentials…”
- Application Default Credentials is an alternative to service account From the official documentation: “There are two ways to obtain credentials for the agent to use: - Let the agent use a service account with private-key authentication - Let the agent use application default credentials (ADC).”
- Application Default Credentials secures Workflows From the official documentation: “To authenticate to Workflows, set up Application Default Credentials.”
- Cloud Functions depends on Cloud Run From the official documentation: “Cloud Run functions represent the next evolution of Cloud Functions, offering an event-driven programming model with enhanced control and scalability, leveraging the Cloud Run serverless platform.”
- Cloud Functions depends on service account From the official documentation: “The Cloud Function needs a service account with permissions to write to the GCS bucket.”
- Cloud Functions works with Workflows From the official documentation: “Learn how to use Workflows to link two public HTTP services (using Cloud Functions), an external REST API, and a private Cloud Run service together.”
- Cloud Run works with service account From the official documentation: “Map a custom Service Account to a Cloud Run service”
- Identity and Access Management depends on Application Default Credentials From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- Identity and Access Management secures Cloud Functions From the official documentation: “You use [Identity and Access Management (IAM)](/iam) to authorize identities to perform administrative actions on functions created using the [Cloud Functions v2 API](/functions/docs/apis)—for example, using `gcloud functions`, the REST API, or Terraform.”
- Identity and Access Management secures Cloud Run From the official documentation: “Cloud Run services are secured by IAM.”
- Identity and Access Management secures Managed Service for Apache Airflow From the official documentation: “For access control, use Identity and Access Management and Managed Airflow [roles and permissions](/composer/docs/composer-2/access-control#user-account).”
- Identity and Access Management secures Pub/Sub From the official documentation: “Pub/Sub uses Identity and Access Management (IAM) for authorization.”
- Identity and Access Management works with Workflows From the official documentation: “Workflows manages access and authentication using Identity and Access Management (IAM) roles and permissions.”
- Identity and Access Management secures Workflows From the official documentation: “Workflows uses Identity and Access Management (IAM) to control which authenticated users and service accounts can perform which actions.”
- Managed Service for Apache Airflow depends on service account From the official documentation: “When creating a Managed Airflow environment, you specify a service account that performs most of the environment's operations.”
- Managed Service for Apache Airflow is an alternative to Workflows From the official documentation: “Both [Workflows](/workflows/docs/overview) and [Managed Service for Apache Airflow](/composer/docs/concepts/overview) can be used for service orchestration to combine services to implement application functionality or perform data processing.”
- Secret Manager secures Cloud Run From the official documentation: “Store sensitive credentials in Secret Manager for secure access by the Cloud Run function.”
How learners score on this topic
Last updated