A receipt consumer’s role
A fictional workload must receive and acknowledge messages. A publisher role names the right service but authorizes a different operation. A role on the operator’s identity also doesn’t grant that workload access. In the IAM binding lesson, inspect the principal, approved role and project. Then change the scenario: if only one subscription is needed, ask whether the project grant is broader than the requirement. Check inherited policy as well as the new binding.
Identity and enablement
A service account identifies a workload. Enabling an API makes that service available to the project. Neither step alone grants the workload every required permission.
The local console saves selected bindings without issuing tokens or evaluating a complete IAM policy. The Google Cloud course connects these decisions with applications and data. Validate effective access, including an excluded resource, before relying on a real grant.