Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Heroku Architect Topic 6 Question 42 Discussion

Actual exam question for Salesforce's Heroku Architect exam
Question #: 42
Topic #: 6
[All Heroku Architect 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

Contribute your Thoughts:

Rikki
1 months 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 months 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 months 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 months 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
Caitlin
3 days 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
8 days 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
2 months 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 months ago
Declaring dependencies in the source code makes it easier to manage and track.
upvoted 0 times
...
Janessa
1 months ago
D
upvoted 0 times
...
Paris
1 months ago
Using the same database type helps ensure that the application behaves consistently.
upvoted 0 times
...
Ranee
1 months ago
A
upvoted 0 times
...
Fairy
2 months ago
It's important to have consistency between development and production environments.
upvoted 0 times
...
Earnestine
2 months ago
I agree, option D is the best choice for following the Twelve-Factor methodology.
upvoted 0 times
...
...
Joni
2 months 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
3 months 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
3 months ago
Mary, I recommend you to install the related PHP libraries manually so the application will run.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77