Let's start with how to set up Cymbal Superstore's cloud environment. Cymbal Superstore is ready to start implementing the basic Cloud Infrastructure for their organization. As an Associate Cloud engineer, you have been assigned to the team to help with this phase of the project, the team begins with a planning meeting to decide how Cymbal Superstore's cloud structure will be organized. Outcomes of this phase of the migration journey include establishing a resource hierarchy, implementing organizational policies, managing projects and quotas, managing users and groups, and applying Access Management, setting up billing and monitoring the use of your cloud resources are also things to consider. Finally, choosing how you interact with Google Cloud is an important decision as well. Different options include the graphical Cloud console, command-line tools, and software development tools. Let's take a closer look. How to set up a resource hierarchy on Google Cloud depends on the needs and structure of the organization. Cymbal Superstore plans to migrate three applications to the Cloud. Its supply chain application, which will run on virtual machines, it's containerized e-commerce application, which will use GKE. It's transportation management application, which will use Cloud Functions to attract truck location. These applications correspond to three different departments. Operations manages the B2B supply chain, logistics overseas transportation, and the sales and marketing department manages the e-commerce application. The graphic shows a possible organizational hierarchy for Cymbal Superstore. The Cymbal Superstore organization is at the top, followed by optional folders underneath, one for each division and one for each application. There are multiple projects under the B2B supply chain app folder. One for each environment related to continuous integration, continuous delivery, CICD, a developing, staging, and production environment. Other apps in the chart would have a similar project structure. As you set up the hierarchy, you will also need to grant organizational policies. For example, marketing might need access to the data in the supply chain system to see if inventory levels affected recent marketing campaigns. Giving marketing the viewer permissions on the supply chain production environment might be a good choice to give them the access they need. An Associate Cloud engineer could also be tasked with enabling application programming interfaces or APIs within projects during setup. Cymbal Superstore's e-commerce project requires access to Google Kubernetes Engine and Cloud SQL as a database backend. You need to enable the APIs for these services. Setting up the Cloud environment also involves granting members IAM roles to ensure they have the right access to projects depending on the needs of their job and their role at Cymbal Superstore. For example, data analysts in the marketing department will need access to historic sales data in the e-commerce system. This is a great use case for BigQuery, Google's cloud-based data warehouse solution. How would we go about giving the proper access? New data analysts would be added to a group named Data Analyst. Managing permission enrolls at a group level is easier than keeping track of permissions for individual users. Data analysts need access to the data in a dataset or table. They would require BigQuery.Data Viewer role at the proper level. Queries and BigQuery are executed as an executable job. To submit a query, a data analyst would also need the BigQuery.jobs.create permission. This permission is included in the predefined role named BigQuery.user. You would give the Data Analyst group access to this role in the production project. As a Cloud Engineer, you'll need to know how to manage symbol superstores users and groups in Cloud Identity, a service for managing users and groups if you're not doing so via Google workspace. Google Cloud's operations Suite, which used to be called StackDriver, provides metrics and logging services for all your services, resources, and projects in your Cloud environment. To monitor metrics from multiple projects. You set up project scoping. If symbol superstores' operations department decides to monitor metrics across all three supply chain projects in the staging environment project. You will set staging as a scoping project and then add Dev and production as monitored projects. While migrating to Google Cloud, Cymbol superstore will be moving some of its IT expenditure to operational expenses. The different departments associated with each application will be responsible for compute and storage costs. You'll need to create a different billing account for each group and link each project to the appropriate account. The department lead in sales and marketing expresses particular concern about the cost of housing its data warehouse and BigQuery, and how to optimize queries and Storage. You'll need to set up custom billing Projects and alerts for this department. Each department will also need you to set up billing exports that can be used to track charges. As an IT administrator for Cymbal Superstore, you can always set up resources in the graphical console. If you have a combination of task you need to do often, you can automate resource management task on the command line. The Cloud SDK has a GCloud command set. The last configuration of google Cloud resources as an executable script. You can use the command G Cloud config set to configure default options such as the project and Compute region. Then if you don't give specific command line arguments, the SDK will use these defaults which simplifies your code even more.
