Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) Exam - Topic 5 Question 21 Discussion

Actual exam question for Salesforce's Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) exam

Question #: 21
Topic #: 5

[All Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) Questions]

Universal Containers has discovered a Sev0 defect in production. Tens of thousands of records will be created with incorrect data in minutes, producing significant brand damage as a consequence. The Salesforce administrator has suggested that the defective text field be replaced with a new picklist field directly in production. The page layout will be modified so that the text-field is removed and the new picklist field added.

What should the Salesforce architect advise?

ADeny the suggestion and explain to everyone that the risk is too high and the next release window is on the weekend.

BPair with the administrator, and review each change as it happens

CExplain that only developers are certified to make changes directly in production.

DCall the security team and begin organizing d penetration test.

Show Suggested Answer

Suggested Answer: A, B, C

by Thaddeus at Jul 25, 2023, 05:04 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Raymon

5 months ago

Pairing with the admin could work, but still risky!

upvoted 0 times

...

Tambra

5 months ago

Wait, can we really just swap fields like that? Seems off.

upvoted 0 times

...

Herminia

5 months ago

Only developers should touch production, for sure.

upvoted 0 times

...

Weldon

6 months ago

I agree, better to wait for the next release window.

upvoted 0 times

...

Annett

6 months ago

Sounds risky to change fields in production!

upvoted 0 times

...

Ciara

6 months ago

I recall that only developers should make changes in production, but I wonder if there are exceptions for urgent fixes like this one.

upvoted 0 times

...

An

6 months ago

I feel like the answer might be to deny the suggestion, but I’m not confident. What if there’s a way to implement the change safely?

upvoted 0 times

...

Geraldo

6 months ago

I’m not entirely sure, but I think pairing with the admin could help mitigate some risks. We practiced a similar scenario in class.

upvoted 0 times

...

Evan

7 months ago

I remember we discussed the risks of making changes directly in production during our last study session. It seems like a bad idea to me.

upvoted 0 times

...

Ceola

7 months ago

Hmm, I'm a bit unsure about this one. I know Twitter has its own analytics, but I'm not sure if that's the specific tool they're asking about. Let me think this through.

upvoted 0 times

...

Shay

7 months ago

I'm pretty sure this is asking about the IT Rules 2011 in India, so I'll focus on that. The options seem to be about different types of officers, so I'll try to recall what I know about the requirements for Indian companies.

upvoted 0 times

...

Alberta

7 months ago

I'm pretty confident about this one. The Message Screening pattern is designed to protect against SQL injection attacks, so the statement must be true.

upvoted 0 times

...

Tresa

7 months ago

Hmm, I'm a bit unsure about this one. I'll need to double-check the instructions to make sure I understand exactly what they're asking for.

upvoted 0 times

...

Robt

7 months ago

Okay, let me think this through. Quo changed its accounting method for the investment in Worth, Inc. from cost to equity. Based on the options given, I think the retroactive or retrospective restatement approach is the right choice here.

upvoted 0 times

...

Dyan

7 months ago

This question seems straightforward, but I want to make sure I understand the key points about monitoring a Blue Prism environment.

upvoted 0 times

...

Francine

12 months ago

D seems like the way to go. Better call in the security team and get a full penetration test before touching anything in production. Can't be too careful these days.

upvoted 0 times

Douglass

11 months ago

It's better to be safe than sorry, especially when dealing with sensitive data in production environments.

upvoted 0 times

...

Douglass

12 months ago

Definitely, a penetration test will help ensure that the changes won't introduce any vulnerabilities.

upvoted 0 times

...

Douglass

12 months ago

Agreed, security should always be a top priority when making changes in production.

upvoted 0 times

...

Vilma

12 months ago

I'm with C on this one. Developers are the ones who should be making changes to production, not the admin. Gotta keep those strict protocols in place, you know?

upvoted 0 times

...

Shawn

1 year ago

Whoa, hold up! Modifying production data directly? That's a recipe for disaster, even if the intention is good. Let's listen to the architect's advice.

upvoted 0 times