Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise is designing a secure identity and access architecture across its hybrid environment and Google Cloud Platform (GCP). The security team has defined two core integration requirements:
Which protocol design aligns with Google Cloud security best practices to satisfy both requirements?
This option suggests using the OAuth 2.0 Client Credentials Grant to log workforce users into the Google Cloud Console and using OpenID Connect (OIDC) ID tokens as authorization tokens for API calls.
The scenario required backend service-to-service communication with no human user context and proof-of-identity validation within the client application.
This option suggests using the OAuth 2.0 framework for workforce portal login and embedding SAML 2.0 XML assertion payloads directly into API authorization headers for RESTful microservice calls.
Google Cloud REST API endpoints natively accepted raw SAML assertions directly in Authorization: Bearer headers for standard data-plane API invocations, which is not supported.
This approach attempts to standardize entirely on SAML 2.0 across both browser-based workforce Single Sign-On and programmatic backend API requests.
Authorization headers.Google Cloud services natively ingested and verified raw SAML XML assertions as authorization tokens on every individual service API request.
Security Assertion Markup Language (SAML) 2.0 is an XML-based open standard designed primarily for federated identity and browser-based web Single Sign-On (SSO). OAuth 2.0 is an industry-standard authorization framework designed to issue short-lived, scoped access tokens that grant delegated authority to client applications accessing protected HTTP/REST APIs without exposing user credentials.
NameID), allowing Google Cloud to establish an authenticated session for the employee.https://www.googleapis.com/auth/bigquery.readonly), ensuring the application only performs actions explicitly delegated by the user.This architecture leverages each protocol for its intended engineering purpose: SAML 2.0 handles federated enterprise workforce authentication across trust domains, while OAuth 2.0 handles modern, scoped API authorization headers.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated