<a target="_blank" href="https://www.cloudskillsboost.google/focuses/2794?parent=catalog">1. A Tour of Google Cloud Hands-on Labs</a> introduces the Google Cloud console. There's also a walkthrough on how to enable an API (e.g. Dialogflow).
<ul>
<li>Google Cloud Project refers to the entity that contains the cloud resources and services (e.g. pool of virtual machines, databases, network, settings and permissions)
</li>
<li><a target="_blank" href="https://cloud.google.com/iam/docs/understanding-roles/#primitive%5C_roles">Basic Roles/Primitive Roles</a> (Viewer, Editor, Owner) are highly permissive and are not recommended in production environments. Instead, use predefined roles or custom roles.
</li>
<li>The core principle of <a target="_blank" href="https://cloud.google.com/apis/design/resources">REST architecture style</a> is to "define named resources that can be manipulated using a small number of methods."
</li>
</ul>

[1\. A Tour of Google Cloud Hands-on Labs](https://www.cloudskillsboost.google/focuses/2794?parent=catalog) introduces the Google Cloud console. There's also a walkthrough on how to enable an API (e.g. Dialogflow).

* Google Cloud Project refers to the entity that contains the cloud resources and services (e.g. pool of virtual machines, databases, network, settings and permissions)
    
* [Basic Roles/Primitive Roles](https://cloud.google.com/iam/docs/understanding-roles/#primitive%5C_roles) (Viewer, Editor, Owner) are highly permissive and are not recommended in production environments. Instead, use predefined roles or custom roles.
    
* The core principle of [REST architecture style](https://cloud.google.com/apis/design/resources) is to "define named resources that can be manipulated using a small number of methods."

Google Cloud Project

I'm following the Google Cloud Architect learning path