Salesforce Exam Heroku Architect Topic 6 Question 42 Discussion

Actual exam question for Salesforce's Heroku Architect exam

Question #: 42
Topic #: 6

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?

AExplicitly declare code dependencies in the application's environment variables and use the same type of database in both development and production.

BPersist code dependencies in the application's production database. Use the same type of database locally to ensure that the dependencies are accessible.

CRecursively determine code dependencies on application startup and maintain separate Git branches for the MongoDB- and MySQL- compatible versions of the application.

DExplicitly declare code dependencies in the application's source and use the same type of database in both development and production.

Show Suggested Answer

Suggested Answer: B, C, D

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

Limited Time Offer

25%

Off

Get Premium Heroku Architect Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Rikki

26 days ago

Option E: Install a crystal ball and just hope for the best. That's the developer's way, right?

upvoted 0 times

...

Orville

27 days 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

28 days 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

30 days 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

Deja

4 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

29 days ago

Declaring dependencies in the source code makes it easier to manage and track.

upvoted 0 times

...

Janessa

30 days ago

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

upvoted 0 times

...

Fairy

1 months ago

It's important to have consistency between development and production environments.

upvoted 0 times

...

Earnestine

1 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

2 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

...