MENU
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?
Suggested Answer: B, C, D
Get Premium Salesforce Certified Heroku Architect (Plat-Arch-206) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
33 comments · newest first
ST
Stephane
11 months ago
Isn't it better to declare dependencies in the environment variables?
TH
Theodora
11 months ago
I disagree, keeping dependencies in the source is a bad idea.
MA
Malissa
12 months ago
Wait, why would you switch to MongoDB for dev? Seems risky.
VA
Vallie
12 months ago
I think option A is spot on!
SA
Sarah
1 year ago
Definitely should use the same database type in both environments!
CO
Coletta
1 year 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.
DO
Dominga
1 year 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?
KR
Kristal
1 year ago
I'm not entirely sure, but I feel like we practiced something about declaring dependencies in the source code. Maybe option D?
LO
Louis
1 year ago
I remember we discussed the importance of having the same database in both environments to avoid issues. I think option A makes sense.
NI
Nickole
1 year 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.
KA
Karon
1 year 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?
RE
Reta
1 year 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.
DA
Dalene
1 year 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.
CR
Cruz
1 year ago
This question seems straightforward, but I want to make sure I understand the Twelve-Factor methodology correctly before answering.
MA
Madelyn
1 year 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.
AI
Aileen
1 year 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.
RI
Rikki
1 year ago
Option E: Install a crystal ball and just hope for the best. That's the developer's way, right?
OR
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.
JA
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.
ST
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.
KR
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.
CA
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.
DE
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.
HA
Harrison
2 years 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.
RE
Reyes
1 year ago
Declaring dependencies in the source code makes it easier to manage and track.
JA
Janessa
1 year ago
D
PA
Paris
1 year ago
Using the same database type helps ensure that the application behaves consistently.
RA
Ranee
1 year ago
A
FA
Fairy
2 years ago
It's important to have consistency between development and production environments.
EA
Earnestine
2 years ago
I agree, option D is the best choice for following the Twelve-Factor methodology.
JO
Joni
2 years 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.
KA
Kallie
2 years ago
But shouldn't we use the same type of database in both development and production, as per the Twelve-Factor methodology?
MA
Matt
2 years ago
Mary, I recommend you to install the related PHP libraries manually so the application will run.