Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Certified Heroku Architect (Plat-Arch-206) Exam - Topic 6 Question 42 Discussion

At Universal Containers (UC), a developer named Yuichiro wrote a PHP application that, in production, uses a MySQL database. Yuichiro is onboarding Mary, a new UC developer, who is setting up her development environment. Yuichiro asks Mary to:1) install the related PHP libraries manually so the application will run;2) use MongoDB, instead of MySQL, in the development environment.According to the Twelve-Factor methodology, which changes should an Architect recommend?
B) Persist code dependencies in the application's production database. Use the same type of database locally to ensure that the dependencies are accessible. and C) Recursively determine code dependencies on application startup and maintain separate Git branches for the MongoDB- and MySQL- compatible versions of the application. and D) Explicitly declare code dependencies in the application's source and use the same type of database in both development and production.
A) Explicitly declare code dependencies in the application's environment variables and use the same type of database in both development and production.

Salesforce Certified Heroku Architect (Plat-Arch-206) Exam - Topic 6 Question 42 Discussion

Actual exam question for Salesforce's Salesforce Certified Heroku Architect (Plat-Arch-206) exam
Question #: 42
Topic #: 6
[All Salesforce Certified Heroku Architect (Plat-Arch-206) Questions]

At Universal Containers (UC), a developer named Yuichiro wrote a PHP application that, in production, uses a MySQL database. Yuichiro is onboarding Mary, a new UC developer, who is setting up her development environment. Yuichiro asks Mary to:

1) install the related PHP libraries manually so the application will run;

2) use MongoDB, instead of MySQL, in the development environment.

According to the Twelve-Factor methodology, which changes should an Architect recommend?

Show Suggested Answer Hide Answer
Suggested Answer: B, C, D

by Maddie at Jul 14, 2024, 09:03 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified Heroku Architect (Plat-Arch-206) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Stephane
9 months ago
Isn't it better to declare dependencies in the environment variables?
upvoted 0 times
...
Theodora
10 months ago
I disagree, keeping dependencies in the source is a bad idea.
upvoted 0 times
...
Malissa
10 months ago
Wait, why would you switch to MongoDB for dev? Seems risky.
upvoted 0 times
...
Vallie
10 months ago
I think option A is spot on!
upvoted 0 times
...
Sarah
10 months ago
Definitely should use the same database type in both environments!
upvoted 0 times
...
Coletta
10 months ago
I think we had a question about keeping dependencies consistent across environments. It feels like option A aligns with that, but I'm not 100% sure.
upvoted 0 times
...
Dominga
11 months ago
I vaguely recall something about environment variables, but I'm confused about whether they should be in the source or not. Could option A be the right choice?
upvoted 0 times
...
Kristal
11 months ago
I'm not entirely sure, but I feel like we practiced something about declaring dependencies in the source code. Maybe option D?
upvoted 0 times
...
Louis
11 months ago
I remember we discussed the importance of having the same database in both environments to avoid issues. I think option A makes sense.
upvoted 0 times
...
Nickole
11 months ago
Option D looks good to me. Explicitly declaring dependencies in the source code and using the same database everywhere is a clean, straightforward solution.
upvoted 0 times
...
Karon
11 months ago
I'm a bit confused by the MongoDB requirement in the development environment. Wouldn't it be better to use the same database in both environments to avoid potential compatibility issues?
upvoted 0 times
...
Reta
11 months ago
I'm leaning towards option A. Explicitly declaring dependencies in environment variables and using the same database in both environments seems like the most reliable approach.
upvoted 0 times
...
Dalene
11 months ago
Okay, let's think this through step-by-step. The key is to identify the best way to manage dependencies and ensure consistency between development and production environments.
upvoted 0 times
...
Cruz
11 months ago
This question seems straightforward, but I want to make sure I understand the Twelve-Factor methodology correctly before answering.
upvoted 0 times
...
Madelyn
11 months ago
Enabling autoscaling on the node pool seems like a good way to handle scaling the cluster as a whole. I'll make sure to set the minimum and maximum node pool size appropriately.
upvoted 0 times
...
Aileen
11 months ago
Hmm, I'm a bit confused by the requirements. I'll need to re-read the question and make sure I understand all the details before deciding on an approach.
upvoted 0 times
...
Rikki
1 year ago
Option E: Install a crystal ball and just hope for the best. That's the developer's way, right?
upvoted 0 times
...
Orville
1 year ago
Option B sounds like a disaster waiting to happen. Storing dependencies in the production database? That's just asking for trouble. I'll have to go with D on this one.
upvoted 0 times
...
Jackie
1 year ago
Haha, Option C is just crazy talk. Maintaining separate Git branches for different database versions? That's way too much work. I'll stick to something more straightforward.
upvoted 0 times
...
Stephane
1 year ago
I actually think Option A is the way to go. Environment variables are the way to go for managing dependencies, and keeping the same database type across environments is a best practice.
upvoted 0 times
Kris
1 year ago
A) Explicitly declare code dependencies in the application's environment variables and use the same type of database in both development and production.
upvoted 0 times
...
Caitlin
1 year ago
D) Explicitly declare code dependencies in the application's source and use the same type of database in both development and production.
upvoted 0 times
...
Deja
1 year ago
A) Explicitly declare code dependencies in the application's environment variables and use the same type of database in both development and production.
upvoted 0 times
...
...
Harrison
1 year ago
Option D makes the most sense to me. Declaring dependencies in the source code and using the same database in both environments aligns with the Twelve-Factor methodology.
upvoted 0 times
Reyes
1 year ago
Declaring dependencies in the source code makes it easier to manage and track.
upvoted 0 times
...
Janessa
1 year ago
D
upvoted 0 times
...
Paris
1 year ago
Using the same database type helps ensure that the application behaves consistently.
upvoted 0 times
...
Ranee
1 year ago
A
upvoted 0 times
...
Fairy
1 year ago
It's important to have consistency between development and production environments.
upvoted 0 times
...
Earnestine
1 year ago
I agree, option D is the best choice for following the Twelve-Factor methodology.
upvoted 0 times
...
...
Joni
1 year ago
Yes, I agree with Kallie. We should explicitly declare code dependencies in the application's source and use the same type of database in both development and production to follow best practices.
upvoted 0 times
...
Kallie
1 year ago
But shouldn't we use the same type of database in both development and production, as per the Twelve-Factor methodology?
upvoted 0 times
...
Matt
1 year ago
Mary, I recommend you to install the related PHP libraries manually so the application will run.
upvoted 0 times
...

Save Cancel