Google Professional Cloud Security Engineer Question 94
Select 3Google Cloud PlatformYour organization uses Google Cloud and wants to implement a secure password and session management policy for user accounts. The organization has the following requirements: 1) Enforce strong passwords that meet compliance standards. 2) Automatically log out inactive users after a certain period. 3) Prevent the reuse of recent passwords. Which of the following measures should you implement to meet these requirements?
- A
Enable Google Workspace password policies to enforce minimum password strength and complexity rules.
- B
Use Cloud Identity to configure session timeout policies for inactive user sessions.
- C
Implement a custom password management solution hosted on Google Cloud to enforce password reuse restrictions.
- D
Enable the 'Enforce password history' setting in Google Workspace to prevent password reuse.
- E
Configure Google Workspace to allow users to reset their passwords without any restrictions.
Show answer and explanation
Correct answers: A, B, D
Explanation
To create a secure password and session management policy, you should use Google Workspace and Cloud Identity's built-in capabilities. Enforcing strong passwords, setting session timeouts for inactive users, and preventing password reuse are critical measures that directly address the organization's requirements. Custom or overly lenient approaches are unnecessary and may introduce security concerns.
- A. Correct.
This is correct because Google Workspace password policies allow you to enforce strong password strength and complexity rules, which aligns with the requirement for strong passwords.
- B. Correct.
This is correct because Cloud Identity allows you to configure session timeout policies to automatically log out inactive users, addressing the session management requirement.
- C. Incorrect.
This is incorrect because Google Workspace and Cloud Identity already provide built-in features to enforce password reuse restrictions, so a custom solution is not necessary.
- D. Correct.
This is correct because the 'Enforce password history' setting in Google Workspace explicitly prevents recent password reuse, satisfying the requirement to prevent password reuse.
- E. Incorrect.
This is incorrect because allowing unrestricted password resets undermines password security and does not align with the organization's compliance requirements.