Examkin

All practice questions

262 questions

All types1,591Multiple choice816Multiple select491Numeric12Matching10Ordering262
Question 261Question →

An administrator needs to configure granular, least-privilege access for an auditor who requires read access to application logs in a Google Cloud project. Put the following steps in the correct logical order to safely create and assign a custom IAM role.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts with identifying the required granular permissions, followed by creating the custom IAM role at the project level, binding the role to the auditor's identity, and finally verifying that least-privilege access is functioning properly.
Following Google Cloud security best practices for custom IAM management requires establishing the least-privilege permission list first. Once the exact permissions are identified, the custom IAM role is formally created at the project level. Next, the administrator binds this custom role to the user's identity. Finally, access is verified to ensure compliance and proper functionality.

Step-by-Step Solution

1
Determine required granular permissions
A specific list of permissions (such as logging.viewer) is identified.
You must know what specific permissions are needed before bundling them into a role.
2
Create the custom role definition
A project-level custom IAM role containing only the required permissions is provisioned.
Custom roles must exist within the resource hierarchy before they can be assigned.
3
Bind the role to the principal
An IAM policy binding connects the custom role to the auditor's Google account or service account.
Permissions take effect for a user only when an explicit policy binding is established.
4
Verify access
Auditor access is tested to confirm intended permissions are granted without extraneous access.
Verification ensures administrative accuracy and compliance with least-privilege best practices.

Key Concept

Custom IAM Role Creation and Lifecycle Management
Question 262Question →

An engineer needs to deploy a Global External HTTP Load Balancer in Google Cloud using gcloud CLI commands. Arrange the following deployment steps in the correct dependency order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for configuring a Global External HTTP Load Balancer is: 1) Create a health check, 2) Create a backend service and attach backends and health checks, 3) Create a URL map, 4) Create a target HTTP proxy, and 5) Create a global forwarding rule.
Deploying a Global External HTTP Load Balancer in Google Cloud follows a strict bottom-up dependency hierarchy. First, health checks are created to monitor backend instance health. Second, a backend service is created, binding instance groups and the health check. Third, a URL map is defined to route requests to the backend service. Fourth, a target HTTP proxy is created to reference the URL map. Finally, a global forwarding rule is established to map an external IP and port to the target proxy.

Step-by-Step Solution

1
Define the monitoring baseline for backend instances.
A HTTP health check resource is created in Google Cloud.
Backend services depend on existing health checks to evaluate instance health.
2
Construct the backend service container.
A backend service resource is created with backend instance groups and health check associated.
URL maps require a target backend service to route traffic.
3
Configure HTTP routing logic.
A URL map resource is created pointing to the backend service as default routing target.
Target proxies require a URL map to process request path rules.
4
Create the HTTP proxy handler.
A target HTTP proxy resource is created referencing the URL map.
Forwarding rules require a target proxy to receive incoming connections.
5
Expose the load balancer publicly.
A global forwarding rule is created linking the external IP address to the target proxy.
This completes the request path from client frontend to backend instances.

Key Concept

GCP Global External HTTP Load Balancer Deployment Hierarchy
PreviousPage 14 / 14
All practice questions — Google Cloud Associate Cloud Engineer | Examkin