Google Associate Cloud Engineer Practice Test 69
Question 680
An IAM Condition references resource.name but fails with invalid attribute semantics for a target permission. What must be checked?
- Verify that the selected IAM condition attribute is supported for the target service, resource and permission type.
- Add a supported IAM Condition on the role binding that evaluates the exact resource.name prefix for eligible requests.
- Move the project between billing accounts to bypass an IAM authorization decision.
- Grant the role at the organization root despite the request for a narrow resource scope.
Explanation
Correct Answer
A:Conditional expressions aren't universally applicable across all Google Cloud permissions and resource types.
Incorrect Answers
B:That action does not resolve the effective IAM permission and binding in this request. The necessary distinction is the effective access decision. The appropriate action here is: Verify that the selected IAM condition attribute is supported for the target service, resource and permission type.
C:Billing changes payment responsibility, not the technical behavior of this workload. The case instead depends on the effective access decision. The appropriate action here is: Verify that the selected IAM condition attribute is supported for the target service, resource and permission type.
D:That action does not resolve the effective IAM permission and binding in this request. It leaves the effective access decision unaddressed. The appropriate action here is: Verify that the selected IAM condition attribute is supported for the target service, resource and permission type.
Question 681
A time-limited IAM Condition uses UTC timestamps, but a team writes an expiration string without timezone and access expires unexpectedly. What should be corrected?
- Replace the time-limited IAM condition with a permanent binding to avoid UTC conversion.
- Move the project between billing accounts to bypass an IAM authorization decision.
- Change only a user or project display name and expect IAM authorization to change.
- Use an unambiguous RFC3339/UTC time value in the condition and test expiration boundaries for the intended principal.
Explanation
Correct Answer
D:Time-based IAM conditions compare exact temporal values; ambiguous local timestamps cause incorrect access windows.
Incorrect Answers
A:Removing the expiration condition grants enduring access rather than correcting the timestamp representation.
B:Billing changes payment responsibility, not the technical behavior of this workload. It leaves the effective access decision unaddressed. The appropriate action here is: Use an unambiguous RFC3339/UTC time value in the condition and test expiration boundaries for the intended principal.
C:Display names and labels identify resources; they do not enforce their runtime behavior. The specific requirement concerns the effective access decision. The appropriate action here is: Use an unambiguous RFC3339/UTC time value in the condition and test expiration boundaries for the intended principal.
Question 682
A denied request is traced to a conditional IAM binding requiring a resource tag, but the resource is missing that tag. What is the proper fix?
- Use real Google Cloud Resource Manager tags and tag bindings where IAM Conditions require tags, not generic labels.
- Attach the approved tag or adjust the policy only after verifying the resource meets the intended classification.
- Move the project between billing accounts to bypass an IAM authorization decision.
- Recreate the principal without updating its actual role binding or identity mapping.
Explanation
Correct Answer
B:Tag-conditional access depends on actual effective tags; broadening the condition to bypass classification breaks governance.
Incorrect Answers
A:That action does not resolve the effective IAM permission and binding in this request. It leaves the effective access decision unaddressed. The appropriate action here is: Attach the approved tag or adjust the policy only after verifying the resource meets the intended classification.
C:Billing changes payment responsibility, not the technical behavior of this workload. The specific requirement concerns the effective access decision. The appropriate action here is: Attach the approved tag or adjust the policy only after verifying the resource meets the intended classification.
D:That action does not resolve the effective IAM permission and binding in this request. The necessary distinction is the effective access decision. The appropriate action here is: Attach the approved tag or adjust the policy only after verifying the resource meets the intended classification.
Question 683
A team assigns a resource tag for classification but assumes every label with the same text satisfies IAM tag conditions. What must they distinguish?
- Use real Google Cloud Resource Manager tags and tag bindings where IAM Conditions require tags, not generic labels.
- Attach the approved tag or adjust the policy only after verifying the resource meets the intended classification.
- Grant the role at the organization root despite the request for a narrow resource scope.
- Remove audit logging and assume a missing permission will stop causing failures.
Explanation
Correct Answer
A:Resource tags and free-form labels have different policy semantics; sharing a name does not make them interchangeable.
Incorrect Answers
B:That action does not resolve the effective IAM permission and binding in this request. The specific requirement concerns the effective access decision. The appropriate action here is: Use real Google Cloud Resource Manager tags and tag bindings where IAM Conditions require tags, not generic labels.
C:That action does not resolve the effective IAM permission and binding in this request. The necessary distinction is the effective access decision. The appropriate action here is: Use real Google Cloud Resource Manager tags and tag bindings where IAM Conditions require tags, not generic labels.
D:Changing audit collection cannot grant a denied permission or fix service behavior. The case instead depends on the effective access decision. The appropriate action here is: Use real Google Cloud Resource Manager tags and tag bindings where IAM Conditions require tags, not generic labels.
Question 684
A project owner tries to remove an inherited organization tag from a child project only by editing project labels. What should they review?
- Review and validate the new hierarchy's inherited roles and organization policies for each sensitive child project.
- Inspect effective tag inheritance and modify the authorized parent tag binding or permitted child override process.
- Add another broad allow-role binding without checking inherited denies or restrictions.
- Grant the role at the organization root despite the request for a narrow resource scope.
Explanation
Correct Answer
B:Hierarchical tag bindings can affect child resources independent of labels stored on the project.
Incorrect Answers
A:That action does not resolve the effective IAM permission and binding in this request. The necessary distinction is the effective access decision. The appropriate action here is: Inspect effective tag inheritance and modify the authorized parent tag binding or permitted child override process.
C:That action does not resolve the effective IAM permission and binding in this request. The case instead depends on the effective access decision. The appropriate action here is: Inspect effective tag inheritance and modify the authorized parent tag binding or permitted child override process.
D:That action does not resolve the effective IAM permission and binding in this request. It leaves the effective access decision unaddressed. The appropriate action here is: Inspect effective tag inheritance and modify the authorized parent tag binding or permitted child override process.
Question 685
A developer's conditional IAM grant works until an exact UTC cutoff; requests immediately after midnight fail even though the network path is unchanged. Which permission condition should be checked?
- Evaluate the binding's request.time expression and time-zone/cutoff interpretation for the failing request timestamp.
- Increase the Cloud NAT gateway size; NAT always resets IAM Conditions at midnight when ports are exhausted.
- Grant the role permanently at organization scope; time-bound access cannot be investigated without removing every condition.
- Rename the user's Cloud Identity account so its login no longer matches the conditional IAM binding.
Explanation
Correct Answer
A:Evaluate the binding's request.time expression and time-zone/cutoff interpretation for the failing request timestamp. IAM Conditions can compare request.time to a timestamp. A correctly enforced expiry may cause the observed change without any networking failure.
Incorrect Answers
B:Increase the Cloud NAT gateway size; NAT always resets IAM Conditions at midnight when ports are exhausted. NAT port allocation problems and IAM conditional authorization are independent. A cutoff-specific permission denial points to the condition.
C:Grant the role permanently at organization scope; time-bound access cannot be investigated without removing every condition. An unconditional organization grant is unnecessarily broad and obscures the root cause. Inspecting the condition can explain legitimate expiration.
D:Rename the user's Cloud Identity account so its login no longer matches the conditional IAM binding. Renaming an identity does not extend the timestamp encoded in a conditional binding and may create account-management problems.
Question 686
An external auditor needs two-hour read access to one project's compliance evidence, but the team adds them to a permanent organization-wide group. What should change?
- Keep deployment permissions scoped to the Cloud Run resource and reserve organization IAM administration for separate principals.
- Use a scoped temporary group or conditional role binding with clear expiry and validated read-only permissions.
- Grant the role at the organization root despite the request for a narrow resource scope.
- Remove audit logging and assume a missing permission will stop causing failures.
Explanation
Correct Answer
B:A temporary review should not create unbounded organization-level access after the engagement ends.
Incorrect Answers
A:Deploying a separate workload does not automatically configure the existing feature. It leaves the effective access decision unaddressed.
C:That action does not resolve the effective IAM permission and binding in this request. The specific requirement concerns the effective access decision. The appropriate action here is: Use a scoped temporary group or conditional role binding with clear expiry and validated read-only permissions.
D:Changing audit collection cannot grant a denied permission or fix service behavior. The necessary distinction is the effective access decision. The appropriate action here is: Use a scoped temporary group or conditional role binding with clear expiry and validated read-only permissions.
Question 687
An administrator plans to transfer project ownership to a new team, but its current service accounts are not documented. What should be inventoried?
- Enumerate human/group bindings and managed workload identities with usage before changing project access policy.
- Disable or remove the person's user/group access and verify effective bindings while preserving distinct application service identities.
- Recreate the principal without updating its actual role binding or identity mapping.
- Grant project Owner to the principal without checking the specific permission or effective policy.
Explanation
Correct Answer
A:Ownership transitions can unintentionally break workload service identities if IAM dependencies are assumed to belong to departing administrators.
Incorrect Answers
B:That action does not resolve the effective IAM permission and binding in this request. The specific requirement concerns the correct runtime principal and its bindings.
C:That action does not resolve the effective IAM permission and binding in this request. The necessary distinction is the correct runtime principal and its bindings. The appropriate action here is: Enumerate human/group bindings and managed workload identities with usage before changing project access policy.
D:Project Owner broadens authorization and is not an appropriate substitute for the named control. The case instead depends on the correct runtime principal and its bindings. The appropriate action here is: Enumerate human/group bindings and managed workload identities with usage before changing project access policy.
Question 688
A folder inherits a custom organization role but the child project's Security Reviewer role adds additional audit permissions. How should effective access be calculated?
- Evaluate the union of applicable inherited and direct allows, together with denials and conditions for the target principal.
- Analyze effective IAM policy bindings and their inheritance for that principal and target resource.
- Grant project Owner to the principal without checking the specific permission or effective policy.
- Move the project between billing accounts to bypass an IAM authorization decision.
Explanation
Correct Answer
A:Effective IAM access can include multiple independent grants; checking only the nearest binding misses some permissions.
Incorrect Answers
B:That action does not resolve the effective IAM permission and binding in this request. The necessary distinction is the effective access decision. The appropriate action here is: Evaluate the union of applicable inherited and direct allows, together with denials and conditions for the target principal.
C:Project Owner broadens authorization and is not an appropriate substitute for the named control. The case instead depends on the effective access decision. The appropriate action here is: Evaluate the union of applicable inherited and direct allows, together with denials and conditions for the target principal.
D:Billing changes payment responsibility, not the technical behavior of this workload. It leaves the effective access decision unaddressed. The appropriate action here is: Evaluate the union of applicable inherited and direct allows, together with denials and conditions for the target principal.
Question 689
An API error reports permission denied on a dependent service outside the requested resource even though the caller has rights on the main resource. What should be checked?
- Identify the exact denied underlying API and its separate IAM resource scope rather than expanding the main resource role.
- Retry the exact denied operation with the actual workload identity after allowing for IAM policy propagation.
- Move the project between billing accounts to bypass an IAM authorization decision.
- Grant the role at the organization root despite the request for a narrow resource scope.
Explanation
Correct Answer
A:Cross-service operations may require permissions on dependencies such as storage or KMS, not only on the primary product.
Incorrect Answers
B:Retries repeat operations; they do not correct missing permissions or invalid configuration. The case instead depends on the effective access decision.
C:Billing changes payment responsibility, not the technical behavior of this workload. It leaves the effective access decision unaddressed. The appropriate action here is: Identify the exact denied underlying API and its separate IAM resource scope rather than expanding the main resource role.
D:That action does not resolve the effective IAM permission and binding in this request. The specific requirement concerns the effective access decision. The appropriate action here is: Identify the exact denied underlying API and its separate IAM resource scope rather than expanding the main resource role.
Question 690
A team wants IAM access for a service limited by network location but attempts to use a condition attribute unsupported by that product. What secure alternative should be considered?
- Verify that the selected IAM condition attribute is supported for the target service, resource and permission type.
- Add another broad allow-role binding without checking inherited denies or restrictions.
- Move the project between billing accounts to bypass an IAM authorization decision.
- Use an approved supported access-context or network/service perimeter control together with IAM instead of assuming an invalid condition will enforce location.
Explanation
Correct Answer
D:IAM Conditions have service/attribute limits; network provenance may require a distinct supported policy layer.
Incorrect Answers
A:That action does not resolve the effective IAM permission and binding in this request. It leaves the effective access decision unaddressed. The appropriate action here is: Use an approved supported access-context or network/service perimeter control together with IAM instead of assuming an invalid condition will enforce location.
B:That action does not resolve the effective IAM permission and binding in this request. The specific requirement concerns the effective access decision. The appropriate action here is: Use an approved supported access-context or network/service perimeter control together with IAM instead of assuming an invalid condition will enforce location.
C:Billing changes payment responsibility, not the technical behavior of this workload. The necessary distinction is the effective access decision.