1. A startup is growing and needs to migrate from a flat project structure to a multi-level resource hierarchy with an organization node, folders, and projects. Which statement best describes the migration considerations and constraints? (Select TWO.)
- A. Existing projects can be moved into the organization and organized into folders without downtime✓ Correct
- B. All billing accounts must be reassigned to the organization node
- C. IAM policies from the flat structure are preserved and automatically inherited by the new hierarchy
- D. Once a project is placed in an organization, it cannot be removed to standalone status✓ Correct
- E. Quota allocations at the project level are reset when moving projects into an organization
Explanation
Existing projects can be moved into an organization and organized into folders without service downtime (option A is true). Once a project belongs to an organization, it cannot be removed to standalone status (option D is true). Option B is false; billing accounts are separate from the organizational hierarchy and don't need reassignment based on org structure. Option C is false; IAM policies don't automatically migrate—you must reapply them as needed in the new structure. Option E is false; project-level quotas are not reset during organizational moves.