In regards to @BigHomie's edit:

One of the first things you have to ask yourself in regards to "good-subjective" is whether the question is answerable in a Stack Exchange context. The number of possible end results should be relatively small, with the devil being in the details. More than that and the Q&A becomes forum-like discussion with everyone piling on opinons.

A question with many possible solutions is acceptable if the number that apply in a professional context are few. If the professional scope doesn't narrow it down, or we could write a book about it, then the question is too chatty and not good for the format.

Your example about zero padded hostnames strikes me as borderline. On one hand, it's always good to plan ahead for future capacity. On the other, how many digits is a company specific thing, and speaking as a DNS admin who has worked at a few companies, hostname formatting discussions are right up there with religion and politics.

In regards to @BigHomie's edit:

One of the first things you have to ask yourself in regards to "good-subjective" is whether the question is answerable in a Stack Exchange context. The number of possible end results should be relatively small, with the devil being in the details. More than that and the Q&A becomes forum-like discussion with everyone piling on opinons.

A question with many possible solutions is acceptable if the number that apply in a professional context are few. If the professional scope doesn't narrow it down, or we could write a book about it, then the question is too chatty and not good for the format.

Your example about zero padded hostnames strikes me as borderline. On one hand, it's always good to plan ahead for future capacity. On the other, how many digits is a company specific thing, and speaking as a DNS admin who has worked at a few companies, hostname formatting discussions are right up there with religion and politics.

In regards to @BigHomie's edit:

One of the first things you have to ask yourself in regards to "good-subjective" is whether the question is answerable in a Stack Exchange context. The number of possible end results should be relatively small, with the devil being in the details. More than that and the Q&A becomes forum-like discussion with everyone piling on opinons.

A question with many possible solutions is acceptable if the number that apply in a professional context are few. If the professional scope doesn't narrow it down, or we could write a book about it, then the question is too chatty and not good for the format.  Your example about zero padded hostnames in particular does not strike me as a good match for our format. Speaking as a DNS admin who has worked at a few companies, hostname formatting discussions are right up there with religion and politics.

In regards to @BigHomie's edit:

One of the first things you have to ask yourself in regards to "good-subjective" is whether the question is answerable in a Stack Exchange context. The number of possible end results should be relatively small, with the devil being in the details. More than that and the Q&A becomes forum-like discussion with everyone piling on opinons.

A question with many possible solutions is acceptable if the number that apply in a professional context are few. If the professional scope doesn't narrow it down, or we could write a book about it, then the question is too chatty and not good for the format. 

Your example about zero padded hostnames strikes me as borderline. On one hand, it's always good to plan ahead for future capacity. On the other, how many digits is a company specific thing, and speaking as a DNS admin who has worked at a few companies, hostname formatting discussions are right up there with religion and politics.