Exam CRT-450 topic 1 question 109 discussion

C is correct I`v tested it. The order of execution: {!StringMethod} invokes getStringMethod() that calls myString getter in which we have assignment myString = a, and than getter returns first 'a'. Both next {!myString} invokes myString variable getter, so we have 'a' and 'a' again. And getMyString() metod is never called.

The question seems to be wrong since there is no getStringMethod defined - but assuming that it's what "StringMethod" was supposed to reference - the answer is a, a, a Even though getStringMethod is called before the getter, the method then attempts to retrieve the value to check if it's null. This retrieval calls the getter - and causes the value to be set to 'a' before being returned. Basically, the property is null only as long as you don't check what it is - the first attempt to check its value changes its state.

myString is an APEX property. The get accessor executes when the property is read. Hence, the answer is a,a,a

I tested the full code in Dev console and the answer is: a, a, a I've struggled to understand the reason, but it seems that getStringMethod uses the getter to access myString, so it receives the value 'a' and doesn't enter the If statement at all

Just test this code in dev console : String myString { get { if (myString == null) { myString = 'a'; } return myString; } private set; } system.debug(myString == null); You get a 'false' printed. Because as soon as you try to evaluate if myString == null in the debug, you enter in the getter of myString, who evaluate myString to null, and set it to 'a'. So myString is no longer null and the system.debug(myString == null) = false :)

it should be b,a,a