Welcome to ExamTopics
ExamTopics Logo
- Expert Verified, Online, Free.

Unlimited Access

Get Unlimited Contributor Access to the all ExamTopics Exams!
Take advantage of PDF Files for 1000+ Exams along with community discussions and pass IT Certification Exams Easily.

Exam Associate Cloud Engineer topic 1 question 143 discussion

Actual exam question from Google's Associate Cloud Engineer
Question #: 143
Topic #: 1
[All Associate Cloud Engineer Questions]

Your team maintains the infrastructure for your organization. The current infrastructure requires changes. You need to share your proposed changes with the rest of the team. You want to follow Google's recommended best practices. What should you do?

  • A. Use Deployment Manager templates to describe the proposed changes and store them in a Cloud Storage bucket.
  • B. Use Deployment Manager templates to describe the proposed changes and store them in Cloud Source Repositories.
  • C. Apply the changes in a development environment, run gcloud compute instances list, and then save the output in a shared Storage bucket.
  • D. Apply the changes in a development environment, run gcloud compute instances list, and then save the output in Cloud Source Repositories.
Show Suggested Answer Hide Answer
Suggested Answer: B 🗳️

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
ESP_SAP
Highly Voted 3 years, 7 months ago
Correct Answer is (A): Connecting to Cloud Storage buckets Cloud Storage is a flexible, scalable, and durable storage option for your virtual machine instances. You can read and write files to Cloud Storage buckets from almost anywhere, so you can use buckets as common storage between your instances, App Engine, your on-premises systems, and other cloud services. https://cloud.google.com/compute/docs/disks/gcs-buckets Why not (B)? Caution Cloud Source Repositories are intended to store only the source code for your app and not user or personal data. Don't store any Core App Engine Customer Data (as defined in your License Agreement) in Cloud Source Repositories. https://cloud.google.com/source-repositories/docs/features
upvoted 32 times
gcpengineer
2 years, 8 months ago
B is the ans
upvoted 3 times
...
pYWORLD
2 years, 8 months ago
I agree with what are you saying, but the problem that you know how the deployment manager template looks? Is jinja/yaml file that means that are source code, so better to put them inside of an repository. So, for my perpective I will go with the B.
upvoted 1 times
...
ashrafh
2 years, 7 months ago
maybe below link will help https://cloud.google.com/deployment-manager/docs/configuration/templates/hosting-templates-externally from that we can take a idea on deciding cloud storage or repo :),
upvoted 3 times
...
stepkurniawan
3 years, 7 months ago
you store the sensitive data NOT in the instance template, that is the current best practice. But you need version control like GIT or Google's GIT (Cloud Source Repo) to backup your code somehow and able to roll back if needed.
upvoted 12 times
[Removed]
3 years, 6 months ago
You can do all thing you are mentioning in the cloud store also. Ethically answer is cloud store as you are not dealing with a source file but a template. Again here the argument can go that config is also a part of the source so B answers. To make life easy let's call this template/config file as the proposal file, so the best way to share will be cloud store.
upvoted 2 times
...
magistrum
3 years, 2 months ago
Look at my post above, cloud repo is for code, not templates
upvoted 2 times
...
JohnnieWalker
2 years, 9 months ago
B is the answer. Deployment Manager Template can be written in either Jinja or Python, this is Infrastructure as Code (IaC) we are talking about here, same as AWS Cloudformation, or Terraform. Therefore, they should be stored on a git repository such as Google Cloud Source Repositories.
upvoted 8 times
...
...
...
SSPC
Highly Voted 3 years, 7 months ago
B is correct. https://cloud.google.com/source-repositories/docs/features
upvoted 29 times
AmitKM
3 years, 7 months ago
Using Cloud Storage Repos, you can add comments and describe your changes to the team.Hence this might be a better option.
upvoted 3 times
...
magistrum
3 years, 2 months ago
I don't see how you can do this when I tried creating: Add code to your repository info Your repository is currently empty. Add some code using a selected method and then refresh your browser. Contents added to this repository can take some time to show up in search results. Learn more. Select an option to push code to your repository: Push code from a local Git repository Clone your repository to a local Git repository
upvoted 2 times
...
...
Cynthia2023
Most Recent 2 months, 3 weeks ago
Selected Answer: B
Use of Deployment Manager Templates: Google Cloud Deployment Manager is a tool that allows you to automate the creation and management of Google Cloud resources. It uses templates written in YAML, Python, or Jinja2 to describe your resources and their configurations. By using Deployment Manager templates, you can provide a clear, codified, and repeatable description of the proposed changes to your infrastructure. Version Control and Collaboration: Cloud Source Repositories provide managed and scalable Git repositories hosted on Google Cloud. Storing your Deployment Manager templates in a source repository enables version control, which is a best practice in software and infrastructure development. This approach facilitates collaboration among team members, allowing for review, commenting, and history tracking of changes to the templates.
upvoted 1 times
Cynthia2023
2 months, 3 weeks ago
A. Store in Cloud Storage Bucket: While storing templates in a Cloud Storage bucket makes them accessible, it does not provide the benefits of version control and collaborative features offered by source control systems.
upvoted 1 times
...
...
sara11190
5 months, 2 weeks ago
B is the correct answer
upvoted 2 times
...
Captain1212
6 months, 3 weeks ago
Selected Answer: B
B is the correct answer
upvoted 2 times
...
pritampanda1988
7 months, 3 weeks ago
Selected Answer: A
Option B (storing in Cloud Source Repositories) might be suitable for storing application code, but it's not the best practice for storing infrastructure configuration templates.
upvoted 1 times
...
Praxii
11 months ago
Selected Answer: B
Correct answer is B
upvoted 1 times
...
SK1990
1 year, 3 months ago
Selected Answer: B
B is the best answer.
upvoted 1 times
...
davidsalomon
1 year, 3 months ago
Selected Answer: B
As 2022 best practice, B
upvoted 1 times
...
Kopy
1 year, 4 months ago
Selected Answer: B
Correction. 2 years later. Correct Answer is (B):
upvoted 1 times
...
diasporabro
1 year, 5 months ago
Selected Answer: B
Thought it was A for a sec, the realized Cloud Source is similar to Github/CodeCommit... So, B is a better choice
upvoted 1 times
...
AwesomeGCP
1 year, 5 months ago
B. Use Deployment Manager templates to describe the proposed changes and store them in Cloud Source Repositories
upvoted 1 times
...
KapilDhamija
1 year, 7 months ago
Selected Answer: A
A is the right choice, Use Deployment Manager templates to describe the proposed changes and store them in a Cloud Storage bucket
upvoted 1 times
...
tomis2
1 year, 8 months ago
Selected Answer: B
Don't get confused - it is B. IaC is a matter of version control system like GIT.
upvoted 1 times
...
AzureDP900
1 year, 9 months ago
B is right .. Showing Deployment Manager templates to your team will allow you to define the changes you want to implement in your cloud infrastructure. You can use Cloud Source Repositories to store Deployment Manager templates and collaborate with your team. Cloud Source Repositories are fully-featured, scalable, and private Git repositories you can use to store, manage and track changes to your code. Hence, the correct answer is: Create Deployment Manager templates to define the proposed changes and save them into Cloud Source Repositories.
upvoted 3 times
...
SergijF
1 year, 10 months ago
Selected Answer: B
Its B.
upvoted 1 times
...
Rutu_98
1 year, 10 months ago
Selected Answer: A
A is correct Answer Connecting to Cloud Storage buckets Cloud Storage is a flexible, scalable, and durable storage option for your virtual machine instances. You can read and write files to Cloud Storage buckets from almost anywhere, so you can use buckets as common storage between your instances, App Engine, your on-premises systems, and other cloud services.
upvoted 1 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...