MENU
You write an expression that checks the validity of an email address.
Which three scenarios should you configure as test cases? (Choose three.)
Suggested Answer: A, B, C
Get Premium ACD101 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
When testing the validity of an email address in Appian, you should consider various scenarios to ensure robust validation. This includes checking for the presence of the @-character, which is essential for a valid email format (A), testing how the expression handles null values (B), and verifying that a correctly formatted email address is validated as such (C). The availability of the mail server (D) is not relevant to the format validation of an email address within an expression. Reference: Appian Documentation - Expression Language Syntax
25 comments · newest first
SH
Shawna
10 months ago
Not sure if null is a good test case, seems too basic.
EL
Elbert
11 months ago
Wait, can an email be valid if the server is down?
FA
Fanny
11 months ago
A valid email like 'jane.doe@example.com' is a must!
CH
Charlette
11 months ago
I think null should be included too, makes sense.
GA
Galen
11 months ago
Definitely need to test for missing the @-character!
BL
Blair
12 months ago
I think option D about the mail server might be relevant too, but I’m not sure if it fits the criteria for checking email validity directly.
NO
Noe
12 months ago
I definitely recall that we need to include a valid email address in our tests, so option C is definitely one to pick.
WA
Walker
12 months ago
I'm not entirely sure about option B being null; I think we might have covered that in class, but it feels a bit tricky.
AP
Apolonia
1 year ago
I remember we discussed testing for missing components in email addresses, so option A seems like a good choice.
OL
Ollie
1 year ago
I've got this! I'll set up test cases for an invalid email without the '@', a null email, and a valid email address. Covering those bases should do the trick.
LO
Lorean
1 year ago
Okay, let's see. I'll definitely want to test an email missing the '@' symbol. Null values and unavailable mail servers are also good edge cases to consider.
QU
Quentin
1 year ago
Hmm, I'm a bit unsure about this one. I'll need to think carefully about the different scenarios that could invalidate an email address.
DE
Deandrea
1 year ago
This seems like a straightforward question. I'll focus on testing common invalid email formats and a valid email address.
LU
Luke
1 year ago
Okay, this seems straightforward. The error message clearly states the memory is growing beyond parameters, so the answer must be that the QlikView Server memory is above the High limit for the Working Set.
CL
Claudio
1 year ago
Based on my understanding of CloudWatch, the correct answer is B, FreeStorageSpace. That's the metric I would check to ensure the DB Instance has enough free storage.
GA
Garry
1 year ago
Okay, I think I know the answer here. The key is to configure the profiler to use "No CoA" instead of the default behavior.
CA
Carey
1 year ago
I feel like I studied something about CoA settings impacting reauthentication. Is it possible that's the reason for the limited access?
SH
Sherell
2 years ago
I think we should not test for scenario D, as it is not related to email address validation.
TI
Timothy
2 years ago
We should also test for scenario C, a valid email address to make sure our expression works correctly.
EL
Elenore
2 years ago
I agree with testing for scenario A. That's a common mistake people make.
LI
Lisbeth
2 years ago
I think we should test for scenario A, an invalid email address without the @-character.
DO
Dorinda
2 years ago
I think we should exclude testing for scenarios like the mail server being unavailable.
SH
Shayne
2 years ago
We should also test for valid email addresses, like 'jane.doe@example.com'.
LA
Lai
2 years ago
I agree with that. That's definitely an important test case to include.
JA
Jamey
2 years ago
I think we should test for invalid email addresses without the @-character.