Exam Professional Cloud Architect topic 1 question 3 discussion

This is talking about the APPLICATION not the infrastructure, therefore I believe we should focus on the APP-side of things: 1. port the app to app engine for content delivery 2. add monitoring for troubleshooting 3. use a CI/CD workflow for continuous delivery w/testing for a stable application so, for me: A, C and E should be the answers

Let's go with option elimination A. Port the application code to run on Google App Engine >> PaaS serverless managed service, so all my infra provisioning is taken care by GCP. B. Integrate Cloud Dataflow into the application to capture real-time metrics >> Good to have C. Instrument the application with a monitoring tool like Stackdriver Debugger >> Is a must for debugging issues and monitoring application logs this is now GCP Cloud monitoring and logging. D. Select an automation framework to reliably provision the cloud infrastructure >> App Engine is a PaaS so the infrastructure is taken care of by App Engine, I would select this if I have not selected A, hence will eliminate this option for now E. Deploy a continuous integration tool with automated testing in a staging environment >> Good to have F. Migrate from MySQL to a managed NoSQL database like Google Cloud Datastore or Bigtable >> There is no requirement for DB enhancement hence will elimination this option A and C are must-have B and E are Good to have, but E has more importance than Big Hence will go with ACE

A : GCP managed infrastructure to make JEE application work, easier than on a VM with server appli to configure C : Mandatory in order to operate the application (maybe not the debugger, but the monitoring) E : CI/CD for better application quality / security; so the operator would appreciate

I chose these answers based on what would make the application easier to get deployed to gcp.

I will go for CDE.

I would say A C D . E has no relevance to the question , creating a CI CD automation testing pipeline that too in staging , yes is a good thing but it is not relavant I feel. Similary doing Data analysis is also irrelevant . hence B & E go out for the same reason .

I think C is wrong now because it was already deprecated. https://cloud.google.com/stackdriver/docs/deprecations/debugger-deprecation

Would recommending Cloud debugger be the right option? As it is no longer available

Answer is : C, D, E. C. Instrument the application with a monitoring tool like Stackdriver Debugger: Visibility is key in the cloud. Tools like Stackdriver Debugger (now called Cloud Debugger) allow you to inspect the state of your application in real-time without stopping or slowing it down. D. Select an automation framework to reliably provision the cloud infrastructure: Manual configuration is error-prone and doesn't scale. Infrastructure-as-code tools like Terraform or Deployment Manager let you define your infrastructure in code, making it repeatable, version-controlled, and easier to manage. E. Deploy a continuous integration tool with automated testing in a staging environment: A robust CI/CD pipeline is essential for rapid and reliable deployments. Automated testing in a staging environment that mirrors production helps catch issues early, ensuring a smoother transition and reducing the risk of production outages.

agree CDE

I chose ACE, but ADE make sense. A. Port the application code to run on Google App Engine. Ok. It's a good practice use managed services when possible, we shouldn't worry about infrastructure. B. Integrate Cloud Dataflow into the application to capture real-time metrics. No Ok. It's just a J2EE application, the question says nothin about a batch or stream pipeline or real-time in insight. C. Instrument the application with a monitoring tool like Stackdriver Debugger. No Ok. App Engine already have natively logging and monitoring, we only have to enable debugger to fix some problem. D. Select an automation framework to reliably provision the cloud infrastructure. Ok. It's a good practice use IaC (infrastructure as code). E. Deploy a continuous integration tool with automated testing in a staging environment. Ok. It's a good practice use CI/CD and tests. F. Migrate from MySQL to a managed NoSQL database like Google Cloud Datastore or Bigtable. No Ok. The question says nothin about Database.

Absolutely different： B No need to use DataFlow F No need to use NOSQL.We should use CloudSQL. Absolutely Correct:A、E A First Step. I'm at a loss:C,D,E C It is microservices app best practice.App Engine is microservices app. AndIt is also written on this page.(Configuring your App with app.yaml) D This is Correct, but App Engine does it automatically. E Automatically test is a Java best practice.

I voted ADE. A - App Engine could be used for J2EE application B - Dataflow is not used for real-time metrics C - Debugger is not used for monitoring D - Good practice E - Good practice F - Depends on the situation but I don't think Datastore or BigTable is a good choice for MySQL migration

I voted ADE. A - App Engine could be used for J2EE application B - Dataflow is not used for real-time metrics C - Debugger is not used for monitoring D - Good practice E - Good practice F - Depends on the situation but I don't think Datastore or BigTable is a good choice for MySQL migration

I think it is ACE A. Port the application code to run on Google App Engine - Correct - Best Practice to migrate J2EE app to APP engine. B. Integrate Cloud Dataflow into the application to capture real-time metrics - Incorrect - Cloud Data flow in not relevant in migrating existing J2EE app to cloud C. Instrument the application with a monitoring tool like Stackdriver Debugger - Correct - Only because it is relevant in this use case of migrating J2EE app to GAE have to 3 best answers. otherwise App engine is already enabled with Debugger by default, Nothing to do extra. D. Select an automation framework to reliably provision the cloud infrastructure - Incorrect - As APP enigne is managed service no requirement to automate provision of infrastructure. E. Deploy a continuous integration tool with automated testing in a staging environment - Correct - This is a best practice for using a cloud native CI/CD

D: Automation frameworks can help you reliably provision the necessary cloud infrastructure for your application, ensuring that the migration process is smooth and consistent. E: Continuous integration tools can help you automate the testing process, ensuring that your application is properly tested before it is deployed to the cloud. A staging environment can provide a separate testing environment that is isolated from the production environment, allowing you to test your application before it goes live. C: Monitoring tools like Stackdriver Debugger can help you identify and troubleshoot issues with your application after it is migrated to the cloud. This can help ensure that your application is running smoothly and efficiently in the cloud.

CDE The three recommended practices you should recommend to the operations manager are: C. Instrument the application with a monitoring tool like Stackdriver Debugger: Monitoring the application's performance and health is crucial for identifying and resolving issues quickly. Stackdriver Debugger provides detailed insights into the application's behavior, helping diagnose performance bottlenecks and debug errors. D. Select an automation framework to reliably provision the cloud infrastructure: Automating infrastructure provisioning reduces manual effort and ensures consistent configuration across environments. This can be achieved using tools like Terraform or Ansible. E. Deploy a continuous integration tool with automated testing in a staging environment: Continuous integration and continuous delivery (CI/CD) pipelines automate the build, test, and deployment process, ensuring code changes are delivered reliably and with minimal downtime. Automated testing in a staging environment helps identify and fix regressions before they impact production.